Fixed flaky test case in EmailTest.java #561
Open
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.
Fixed flaky test case in the following class:
org.simplejavamail.api.email.EmailTest
Assertion called in:
EmailTest#testToStringFull
POINT OF FAILURE
In
EmailPopulatingBuilderImpl
class, headers was of typeHashMap
. HashMap being unordered, can give non-deterministic results fortoString()
method when run on different jvms.Observed failure was:
FIX
Changed the type of
headers
toLinkedHashMap
as it retrieves the order of insertion in the Map, guaranteeing consistenttoString()
output.Fixed using NonDex
Suggested command to check flaky tests :
For the particular test class:
For more information: https://github.com/TestingResearchIllinois/NonDex