Test updateInstanceWithTransaction in CandidateDeciderDao #611
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
|
[diff-counting] Significant lines: 92. |
andrew032011
approved these changes
May 2, 2024
| const results = await Promise.all(promises); | ||
|
|
||
| // Verify proper number of candidates are rated | ||
| expect(results[4].candidates.length === 5); |
There was a problem hiding this comment.
maybe also verify that for two updates to the same ID, that the latest rating and comment will persist?
andrew032011
approved these changes
May 6, 2024
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.
Test
updateInstanceWithTransactionby simulating concurrent updates, then checking that the total candidates rated is correct after all promises have been resolved.