Fix nondeterminism in WriteOptionsTest #427
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.
This PR fixes nondeterministic behavior in the following flaky tests:
com.cedarsoftware.io.WriteOptionsTest.getAccessorsForClass_bindsBooleanNonStaticFieldAccessorscom.cedarsoftware.io.WriteOptionsTest.getAccessorsForClass_findEnumWithCustomFields_whenNotPublicFieldsOnlycom.cedarsoftware.io.WriteOptionsTest.getAccessorsForClass_findsAllNonStaticFieldAccessorscom.cedarsoftware.io.WriteOptionsTest.getAccessorsForClass_whenMethodDoesNotExists_doesNotThrowExceptioncom.cedarsoftware.io.WriteOptionsTest.getAccessorsForClass_withMixedAccessorsDescription
All five tests flaked due to the nondeterministic ordering of fields and methods returned by Java reflection.
WriteOptions.getAccessorsForClass()constructs its accessor list using reflection, which does not guarantee deterministic ordering, yet the original tests assumed fixed positional order (e.g., index 0 must be"x").Failure messages:
Proposed Changes
list.get(0),list.get(1), etc.).Map<String, Accessor> map = accessors.stream().collect(...)