Project

General

Profile

Support #12984

Counting tests, i.e. files in the test directories

Added by Katherine Lato over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
06/22/2016
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

Can we create and run a script that records the number of tests in larsoft... i.e. files in the test directories?

History

#1 Updated by Lynn Garren over 4 years ago

Why?

Note that the number of files does not equate to the number of tests. Plus there are unit tests and CI tests. Some tests may be marked for specific circumstances (e.g., those that take a long time to run).

#2 Updated by Marc Mengel over 4 years ago

For the Integration tests, the test_runner has a --list-tests option that
will list all the available tests, and a --expand-tests that shows the expanded
tests in a given suite rather than run them.

Is there a say-it-but-don't-do-it option for the mrb test phase?

#3 Updated by Lynn Garren over 4 years ago

Interesting idea. However "mrb test" really means "run cmake, build, and then test". Finding a simple solution will need some thought and some work.

#4 Updated by Gianluca Petrillo over 4 years ago

For the unit tests, running ctest -N gives the list of the tests.
This means:

mrb build -C
cd "$MRB_BUILDDIR" 
ctest -N

Requires:

  • all relevant repositories checked out
  • running cmake (as above)

Compilation is not required.

#5 Updated by Ruth Pordes about 4 years ago

  • Status changed from New to Closed


Also available in: Atom PDF