René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Expose SHOULD(\"XXX\") sub-targets explicitly callable from the shell","articleBody":"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!\r\n\r\nGiven this example:\r\n\r\n```\r\nGTEST(MYFooTest, \"MyBarTest\") {\r\n\r\n... some setup stuff ...\r\n\r\nSHOULD(\"foo\") {\r\n\r\n}\r\nSHOULD(\"bar\") {\r\n\r\n}\r\n```\r\n\r\nI'd like to call SHOULD tests explicitly!\r\n\r\nUsing GUnit one can run all tests:\r\n\r\n    ./mytest --gunit_filter=\"*\"\r\n\r\nOr just a subset:\r\n\r\n    ./mytest --gunit_filter=\"MYFooTest.*\"\r\n\r\nOr one explicit test:\r\n\r\n    ./mytest --gunit_filter=\"MYFooTest.MyBarTest\"\r\n\r\nBut one cannot call a SHOULD:\r\n\r\n    ./mytest --gunit_filter=\"MYFooTest.MyBarTest.foo\"\r\n\r\n# why?\r\n\r\nIn 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.","author":{"url":"https://github.com/qknight","@type":"Person","name":"qknight"},"datePublished":"2022-03-18T10:18:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/73/GUnit/issues/73"}