/ and , bind at the wrong precedence for --run_test argument

[Richard <legalize@…>]

When specifying an argument to --run_test you can use * to specify wildcards in the naming hierarchy and / to specify different levels of the naming hierarchy. Comma (,) can be used to specify different sets of tests but only at the same level.

Unfortunately this is backwards from what you'd expect because you really want comma to separate entire specifications, not different names at the same level.

If you have the following test case organization:

MASTER
suite1

case1
case2

suite2

testcase1
testcase2

suite3

subsuite

testcase1

There isn't any way to specify that only case1, testcase2 and subsuite be run. This is because you can't specify alternative paths, only alternative elements within a path level.

[awl03@…]

I agree this is a bug. Very suprising behaviour. I tried posting some code here with examples of other --run_test weirdness but Trac thought it was spam and won't let me post it.

[Gennadiy Rozental]

This is addressed in 1.59. You can now use --run_test repeatedly and achieve desired filtering. In addition many more filtering options exist now (including labels).