From 7368586f0dfc25a97d982636e1eda9e5ebb5d41b Mon Sep 17 00:00:00 2001 From: Massimiliano Culpo Date: Mon, 29 Jan 2018 15:19:50 +0100 Subject: Mark slow unit tests (#6994) * Marking database tests as slow * Marking url command tests as slow * Marking every test that uses database as slow * Marking tests that import files as slow * Marking gpg tests as slow * Marking all versions and one list tests as slow * Added more markers to unit tests + cli option to skip slow tests Following a discussion with Axel, the generic 'slowtest' marker has been split into 'db', 'network' and 'maybeslow'. A brief description of the meaning of each marker has been added to pytest.ini. A command line option to run only fast tests has been added to 'spack test' * Don't use classes to group tests together Reverted grouping tests under a class, as required in the review * Minor style changes --- pytest.ini | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'pytest.ini') diff --git a/pytest.ini b/pytest.ini index 0d8d2b271f..e8f5e33c71 100644 --- a/pytest.ini +++ b/pytest.ini @@ -2,4 +2,8 @@ [pytest] addopts = --durations=20 -ra testpaths = lib/spack/spack/test -python_files = *.py \ No newline at end of file +python_files = *.py +markers = + db: tests that require creating a DB + network: tests that require access to the network + maybeslow: tests that may be slow (e.g. access a lot the filesystem, etc.) -- cgit v1.2.3-60-g2f50