testing: fix bug in TestParticipationAccountsExpirationFuture/TestParticipationAccountsExpirationNonFuture#3616
Merged
tsachiherman merged 1 commit intoalgorand:masterfrom Feb 13, 2022
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3616 +/- ##
==========================================
+ Coverage 48.05% 48.09% +0.04%
==========================================
Files 381 381
Lines 62074 62074
==========================================
+ Hits 29829 29854 +25
+ Misses 28822 28794 -28
- Partials 3423 3426 +3
Continue to review full report at Codecov.
|
winder
approved these changes
Feb 13, 2022
Merged
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.
Summary
This test had a bug, where it was sending a transaction to one node2, waiting for the transaction to be included in a block on node1, and then pulling the account data from node2.
Since the test failed to wait for node2 to be at the same round as node1, there is no guarantee that the account data fetched from node2 is the same as the account data that was just updated in the block.
Separately from that, the
fixture.WaitForTxnConfirmationcall was not tested for its return value.Test Plan
Use Circle-CI.