chore: Prevent race condition in DynamoDB Tests #179
Conversation
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
DynamoDB tests share a database / table and reset it for each test. XUnit tests can run in parallel causing one test to reset the table in the middle of another test executing and triggering a failure. This can be observed by adding a delay after a write and before a read. Collections will ensure the specific tests are not run in parallel. I tested using a unique prefix for each test but still observed the error. Ideally these should be able to run in parallel but this is a compromise of invested time to fix it vs more stable tests now.
tanderson-ld
approved these changes
Oct 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
DynamoDB tests share a database / table and reset it for each test. XUnit tests can run in parallel causing one test to reset the table in the middle of another test executing and triggering a failure. This can be observed by adding a delay after a write and before a read.
Collections will ensure the specific tests are not run in parallel. I tested using a unique prefix for each test but still observed the error. Ideally these should be able to run in parallel but this is a compromise of invested time to fix it vs more stable tests now.
Note
Annotates DynamoDB test classes with a shared xUnit collection to prevent parallel execution.
pkgs/dotnet-server-sdk-dynamodb/test/DynamoDBBigSegmentStoreTest.csandpkgs/dotnet-server-sdk-dynamodb/test/DynamoDBDataStoreTest.cswith[Collection("DynamoDB Tests")]to run these tests in a shared, non-parallel collection.Written by Cursor Bugbot for commit f11700b. This will update automatically on new commits. Configure here.