-
Notifications
You must be signed in to change notification settings - Fork 339
Description
Description of the bug:
It looks like default run/debug configurations created by CLIon for gtests doesn't pass the correct filter for parameterized tests.
For example,
TEST_F(TestName, MethodName)
creates run configuration with --test-filter=TestName.MethodName
And it seems like that's exactly what's happening for TEST_P as well. Taking an example from googletest docs,
TEST_P(FooTest, DoesBlah) {
...
}
INSTANTIATE_TEST_SUITE_P(MeenyMinyMoe,
FooTest,
testing::Values("meeny", "miny", "moe"));
For this actual generated test names are of this format, MeenyMinyMoe/FooTest.DoesBlah/0. But since the test filter generated from IDE is still FooTest.DoesBlah, it doesn't match any tests and runs nothing. Although a correct fix would be to somehow surface parameters as part of test run configurations and construct the full test name properly, a simple fix would be to put * by default (such as *FooTest.DoesBlah*)
Which category does this issue belong to?
CLion
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Create a small test file using parametrized tests following official guide, https://google.github.io/googletest/advanced.html#value-parameterized-tests
Which Intellij IDE are you using? Please provide the specific version.
No response
What programming languages and tools are you using? Please provide specific versions.
C++
What Bazel plugin version are you using?
2025.10.27.0-api-version-253
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status