Ordering or depending tests
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 296
- Forks
- 66
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 1
Description
Just using the calc_pi example...
```
[scratlantis:~/ideas-ecp/TrainingCi4Ecp/build] miller86% make test
Running tests...
Test project /Users/miller86/ideas-ecp/TrainingCi4Ecp/build
Start 1: test_1
1/2 Test #1: test_1 ........................... Passed 0.00 sec
Start 2: blt_gtest_smoke
2/2 Test #2: blt_gtest_smoke .................. Passed 0.00 sec
100% tests passed, 0 tests failed out of 2
```
It appears to run the ``blg_gtest_smoke`` *after* my google test. But, isn't a passing ``blt_gtest_smoke`` a *requirement* in order for any of my gtest tests to run? So, am curious about a) why the order is what it is and b) is it possible to *depend* any gtest on a passing ``blt_gtest_smoke`` so that if that doesn't pass, it doesn't even attempt to run gtest tests?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the calc_pi example's `make test` output and the CMake test registration that produces `test_1` and `blt_gtest_smoke`. Determine how the tests are ordered and whether a gtest dependency can be expressed; done means dependent tests wait for, and are skipped when, `blt_gtest_smoke` fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100