Expose SHOULD("XXX") sub-targets explicitly callable from the shell

[qknight]

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.

[MattYoung50]

I would also appreciate this feature

[krzysztof-jusiak]

Are there issues with the following?

Note Running specific should test case requires ':' in the test filter (--gtest_filter="test case pattern:should pattern")

--gtest_filter="FooTest*:Do A" # calls FooTest with should("Do A")
--gtest_filter="FooTest*:-Do A" # calls FooTest with not should("Do A")
--gtest_filter="FooTest*:Do*" # calls FooTest with should("Do...")
--gtest_filter="FooTest.:Do*" # calls FooTest with should("Do...")
--gtest_filter="-FooTest?:-Do*" # calls not FooTest with not should("Do...")

• https://github.com/cpp-testing/GUnit/blob/master/docs/GTest.md

[MattYoung50]

That works for me! Who wants to read good documentation when opening a ticket is so much simpler right?