Spec test coverage report hack #13718
Merged
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
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 type of PR is this?
Test Coverage
What does this PR do? Why is it needed?
This PR adds a hack script to generating a spec test coverage report.
We basically run the bazel tests and save the test paths to bazels undeclared outputs folder. From there we cross reference the test paths with those of the official consensus spec tests repo and write to a file whether they have been found or are missing.
This is needed so that we can quickly determine whether there are any new spectests that we aren't supporting or if there are some spectests that we do support but are being skipped/not running.
Fail conditions are:
Which issues(s) does this PR fix?
N/A
Other notes for review