Mechanism for catching link-time test stripping
Open
- Dominant language
- C++
- Stars
- 21.5k
- Forks
- 3.5k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 2
Description
So, I have an issue where a linker strips out all the test cases in separate files (but not the custom runner main).
I've tried to catch this at run time by adding [hidden] failing tests an asserting that a certain number fail, HOWEVER, this is both fragile and incompatible with *actually* running the main suite, as you can't have 2 session objects.
Any ideas?
Contributor guide
Assessment
This issue has not been assessed yet.