Murisi/execute tests rebased3 abrev with generalized generation#343
Draft
Murisi/execute tests rebased3 abrev with generalized generation#343
Conversation
…th generalized transaction generation.
This file contains hidden or 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.
Based on the same code as #341 . This PR is an attempt to integrate generalized transaction generation with the property tests that induce transaction failure. The end goal being to generate a larger range of failing transactions and discover potential issues. Specifically, the following approach is taken:
mutationTestExecuteNonExistingRootFails(vm.transaction(_mockVerifier, txParams), mutParams);Currently in
mainwe only mutate a more limited set of transactions where actions all have the same number of compliance units (amongst other minor restrictions). This draft is only for checking/demonstrating whether this idea is workable and for testing the latest proposed changes to the protocol adapter. This PR would have to be rebased for actual use.