New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to filter test by name (-t, --run_test) if template type contains multiple parameters #223
Comments
Thanks for the report. Right now, two possible solutions that come to my mind:
As a user, I find What do you think? |
Hi, I would just expect the framework to take the exact same name, that it prints. My expectation would be, that when the framework says test |
We both agree to qualify the current behaviour that you described as buggy, and that was not my question. Thanks for the report, I'll go for 1. |
Hi, Thank you for looking into this! |
I implemented a fix on the branch |
…xt-internal * topic/GH-223-cannot-filter-template-test-cases: Change log Documentation updates Normalizing test names accross several compilers Sanitizing template test cases that contain ',' in their name
Works like a charm. Thank you very much! |
Thanks for the quick feedback! (I'll close the issue when this gets merged to master) |
Hello,
I'm used to using the
-t
option to separate a failing test during TDD and to inspect the cause be using printf() debugging. Usually, I just copy the test name just from the error message. So, if I have an error message like this:I'm used to filter the test with:
-t "filter_me<test_parameters<100, 100>>"
. That works fine as long as there is no comma in the test name, as above.Following example:
Will generate the error message above and will not allow you to filter the test by the name printed. However, the test can be filter with a wildcard behind the first comma:
-t "filter_me<test_parameters<100,*"
.I would expect that I can use the reported name of a failing test to filter for exactly that failing test.
Edit: Observed in Boost 1.68 with Apple LLVM version 10.0.0
The text was updated successfully, but these errors were encountered: