Fixed flaky tests due to class.getMethods
#1525
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.
I found some flaky tests in
feign.TypesResolveReturnTypeTest
that are caused by using theclass.getMethods
method.According to Java docs:
This means that future changes in Java may change the order of the returned list, and cause tests failures in this file. I created a
getMethods
method to sort the result fromclass.getMethods
using alphabetical order with combos of the method name and return type name.Then I just replaced the
class.getMethods
with the newgetMethods
method, and updated some of the indexs in related tests to ensure deterministic order and behavior in the future.