In short: SHOULD("") tests should also be exposed as single targets on the shell and they 'could' eventually also show up as individual tests in the tests run. At least they should be callable individually!
Given this example:
GTEST(MYFooTest, "MyBarTest") {
... some setup stuff ...
SHOULD("foo") {
}
SHOULD("bar") {
}
I'd like to call SHOULD tests explicitly!
Using GUnit one can run all tests:
./mytest --gunit_filter="*"
Or just a subset:
./mytest --gunit_filter="MYFooTest.*"
Or one explicit test:
./mytest --gunit_filter="MYFooTest.MyBarTest"
But one cannot call a SHOULD:
./mytest --gunit_filter="MYFooTest.MyBarTest.foo"
why?
In our code-base we have like 10 SHOULD calls and if one fails it is often hard to see which one does as the output can be quite huge. So I basically comment all n-1 SHOULD tests and uncomment them one by one to work them down. Which is of course total overkill.
In short: SHOULD("") tests should also be exposed as single targets on the shell and they 'could' eventually also show up as individual tests in the tests run. At least they should be callable individually!
Given this example:
I'd like to call SHOULD tests explicitly!
Using GUnit one can run all tests:
Or just a subset:
Or one explicit test:
But one cannot call a SHOULD:
why?
In our code-base we have like 10 SHOULD calls and if one fails it is often hard to see which one does as the output can be quite huge. So I basically comment all n-1 SHOULD tests and uncomment them one by one to work them down. Which is of course total overkill.