Update testing guide structure and add coverage testing #1182
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
|
Preview is available here: |
sisuresh
approved these changes
Jan 17, 2025
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.
What
Add a testing page on code coverage. Also reorganised the testing pages.
Why
Code coverage was somethign I was wanting to add to this section previously but I ran into issues figuring it out. But thankfully @graydon gracefully showed me how to do it, and it was pretty simple!
Limitations
This new doc does not provide instructions for how to get code coverage information from fuzz tests. That's a different process which I'll hopefully figure out and open a different PR for.
Close #921
This is part 1 of 2 in a stack made with GitButler: