Add way to generate main->test code mapping via coverage & show affected #740
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
Allows to generate a coverage mapping from main code to test code by running each test suite one after another, each time processing the generated coverage data. After that the coverage data can be combined with a git diff to see which tests are most likely to be affected. Not bullet proof, but can in many cases safe the time to run the full test suite, reducing the feedback loop.
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.
Allows to generate a coverage mapping from main code to test code by
running each test suite one after another, each time processing the
generated coverage data.
After that the coverage data can be combined with a git diff to see
which tests are most likely to be affected.
Not bullet proof, but can in many cases safe the time to run the full
test suite, reducing the feedback loop.