Hi, I am here to understand why you made fixtures doomed to be tests. I would also like to be pointed on a solution that avoid drawbacks I get now.
I need to make my tests to touch a file automatically when they are successful. Since add_test dont support several COMMAND, I use fixtures to do so (with COMMAND cmake -E touch…).
Maybe I should use something else (if so what?), but for me, that’s exactly the purpose of a fixture.
- The amount of report doubled because of the junk of the fixtures.
- The time to do a memory check almost doubled as well, since the startup time of -T memcheck of each test is so big, and the cmake -E… is being memchecked all the time after the real test.
- Probably other things that I did not spot yet
In my opinion, it’s conceptually wrong to force a fixture to be a separated test. Sure it can be useful sometimes, but forcing just loose flexibility. I would like to hear why this had been imposed, and if I have alternatives for my use-case.