--run_test arbitrary depth matching

[Maxim Yanchenko <Maxim.Yanchenko@…>]

Hi Gennady,

That's awesome that you have added the ability to run individual tests and suites by name. However, while using this feature, I found myself keeping adding "*/" before the test name and rerunning the test program until it finally matches the nesting level and run the test I need (because usually I just see the test I want to run in the source code and I don't really care how deep is it in the hierarchy).

Could you please add a possibility to match "any" nesting level?
I would suggest double-star syntax:

--run_test=/my_test

will match "my_test", "s1/my_test", "s1/s2/s3/s4/my_test" etc.

--run_test=s1//my_test

will match "s1/my_test", "s1/s2/s3/s4/my_test" etc, but will not match "my_test" and "s2/my_test".

Thanks,
Maxim

[Gennadiy Rozental]

do you want /a/b to filter out test case b in all sub-testsuites a on any level either?

[Maxim Yanchenko <Maxim.Yanchenko@…>]

yes, please, as well as /a*//b and similar, for a case when there are many tests with name "b" (say "conversion_test"), and I need one which is "somewhere" inside suite with name starting with "a" ("market_data"), no matter how many sub-suites are between them (including zero).

To me, it would be enough just to have a regexp to match versus the whole test path, but I understand it may add an unnecessary dependency on Boost.Regex which is probably undesirable.

[Gennadiy Rozental]

I've introduced a notion of a label and an ability to run by label. I think this will be more natural in comparison to what you suggested.