Possible bug in twister gtest harness #71635
Unanswered
GeekOffTheStreet
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Hi @GeekOffTheStreet, |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I tried using Twister with the gtest harness and ran into issues with it detecting unit test execution. The behavior for how it parses sample.yaml/testcase.yaml doesn't match what I would expect. I should not that I'm not using pigweed. Consider this simple test case:
I build that for qemu using:
If I use the console harness with a sample.yaml resembling:
The test works as expected (sample output):
If I try to use the gtest harness:
The runner tries to match
HelloWorld.foo.HelloWorld.foo
instead of justHelloWorld.foo
and fails:I didn't see an obvious way to alter the matching behavior.
@yperess
Beta Was this translation helpful? Give feedback.
All reactions