test(flaky): Sorting headers for deterministic order #5754
Merged
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.
The order of HTTP methods in the
ALLOW
header (OPTIONS,PUT vs PUT,OPTIONS) is not guaranteed to be consistent ingetHeaderString()
, so the following test case fails if the order changes:jersey/tests/e2e/src/test/java/org/glassfish/jersey/tests/e2e/server/wadl/NoJAXBNoWadlTest.java
Line 69 in 89de7de
This PR proposes to sort the headers so that the order assumptions (in this PR, alphabetical order) in the test cases are correct.
This change was confirmed by running the NonDex tool, which explores and reports errors in different behaviors of under-determined Java APIs.
To reproduce this problem, you can run the test with NonDex using these commands:
Here are screenshots of the output produced by NonDex before and after the fix:
Please let me know if you want to discuss these changes.