Add Jenkins workflow and optimise testing mechanism
Add Jenkins workflow and optimise testing mechanism
Thanks for your contribution. But this is not we change we would accept as this is clearly for a specific downstream implementation which is is not used in our repo. Also we are doing Coverage is a different way (but it is currently temporally disabled because of an upstream issue).
I do like the approach of collecting coverage for each separate test. This is something I wanted to do myself in the past in a different project.
The title does not describe the actual changes.
Also this is not portable and more of a hack.
Also you can achieve this without changing a single line of code. The compiler flags are supposed to be passed to make via CXXFLAGS. And you can simply execute testrunner for each test from a script which prepares and specifies the environment. Some recently introduced parameter allow that. Please take a look at test/scripts/testrunner-single.sh. Extending the loop body at line 16 should be sufficient. There is a downsize though because all tests (and related data) are loaded at each start-up so you might still require the flush. Instantiating the tests only when they are actually executed is being in tracked in https://trac.cppcheck.net/ticket/12080 and will hopefully be addressed within the year.
Still some additional comments in case we will keep using this locally.
No reply in over two weeks - closing.
Please re-open if comments are being addressed and there is still something to apply.