chore: add a systematic test for concurrent transactions #3449
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
chebbyChefNEQ
force-pushed
the
rmeng/tx-test
branch
from
e1b14bb to
55c26e9
Compare
chebbyChefNEQ
force-pushed
the
rmeng/tx-test
branch
from
55c26e9 to
219f411
Compare
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.
This PR adds a way to easily write test for concurrent transactions.
we define a new class called
ParallelOperationswhere we can define:The tests will automatically test applying the transactions in random order and make sure the transactions are applied correctly
I will add more tests in subsequent PRs
I will also add a failure test where we expect certain transactions to fail in subsequent PRs