Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMultiple coverage tracking according to the result of a transaction #369
Conversation
…a into dev-coverage-adding-binary
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.
This PR fixes issue #363 . It introduces a boolean type in the coverage maps to keep track of transactions when they revert (or not). This will allow a richer notion of coverage.
It is worth mentioning that this PR will not improve the test cases generation by itself, until the code to mutate lists of transactions is merged (this will happen in upcoming PR, after #357 is merged).
This PR also includes a simple test to check that the amount of lists of transactions in the corpus collected is correct (for a small contract). This tests the code that collect the corpus as well.