Generate a coverage report for End to end tests #5667
Merged
+36
−10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thebentern
approved these changes
Dec 26, 2024
|
I've used Coveralls in some other projects, so I'll add it to my list to get that added for the firmware |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For coverage to be saved, the application under test needs to exit cleanly, calling all exit handling logic. This happens when the application calls
exit(). I've modified the simulator and the crypto unit test so they exit and save the coverage details.Demo: see the
code-coverage-reportartifact on https://github.com/esev/meshtastic-firmware/actions/runs/12497423501The
code-coverage-report/coverage_src.infofile should be compatible with most coverage tools like CodeCov/Coveralls.