Fix flaky test in DeliveryDetailsTest#709
Merged
Merged
Conversation
Owner
|
Thanks for the PR @Md-Arif-Hasan. Once this CI build goes Green, we should be able to merge it. |
authorjapps
approved these changes
Apr 22, 2025
Contributor
Author
|
@authorjapps Thank you so much! |
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.
Fix Flaky Test in
DeliveryDetailsTest.testSerDeserWhat is the purpose of this PR?
This pull request addresses a flaky test,
DeliveryDetailsTest.testSerDeser, in thezerocodeproject. The test was failing intermittently due to assumptions about the ordering of JSON fields during serialization and deserialization.Why the test fails
The
DeliveryDetailsTest.testSerDesertest relied on strict JSON field ordering during serialization. Gson, the JSON library used in the project, does not guarantee field order by default. This caused the test to fail when the field order changed, especially under NonDex shuffling, which explores non-deterministic behaviors.How to reproduce the test failure
Run the test with NonDex to simulate shuffling of field order:
Before the fix, the test failed intermittently with errors similar to:
Expected results
The test should pass consistently, regardless of the order of fields in the serialized JSON.
Actual results
Before the fix, the test failed intermittently due to changes in the order of JSON fields.
Description of fix
JSONAssertassertions using theLENIENTmode. This ensures that field order does not affect the test results.GsonBuilder:Validation
Test Results
mvn -pl core test -Dtest=org.jsmart.zerocode.core.kafka.DeliveryDetailsTest#testSerDeserAdditional Notes
Let me know if further improvements or clarifications are needed!