feat: Add Test Case Generation for Weak Isolation Levels in Different Databases #61
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.
issue #42
Generate different test cases for weak isolation levels of different databases.
The isolation level of the database has different capabilities to break the cycles in POP. If the isolation level can break the cycles in POP, then the test case corresponding to POP should not have data anomalies under the isolation level. I corresponded the isolation level with the ability to break the cycles and summarized 6 mechanisms.
By specifying the database and isolation level, the code can generate test cases for the isolation level.