Change data structure HashMap to LinkedHashMap to fix flaky test#1
Open
219sansim wants to merge 1 commit into
Open
Change data structure HashMap to LinkedHashMap to fix flaky test#1219sansim wants to merge 1 commit into
219sansim wants to merge 1 commit into
Conversation
Owner
Author
|
When I run
All the tests pass with the same fix |
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.
Summary:
This the fix for the flaky test case
This test is detected as flaky by the NonDex tool developed by researchers at UIUC. (https://github.com/TestingResearchIllinois/NonDex)
Flaky tests are tests in software development that produce inconsistent or unreliable results, which can lead to false non-deterministic outcomes of the test case, fixing them is important to both reliable testing and fixing vulnerabilities in the code.
The outcomes of the
TokenAuthenticationValidatingPushNotificationHandlerare sometimesINVALID_PROVIDER_TOKENinstead ofEXPIRED_PROVIDER_TOKENwhich is why theassertfailsThis is because the
verifySignaturemethod fails before reaching the line of code which detects anEXPIRED_PROVIDER_TOKENThe
verifySignaturemethod inAuthenticationTokenclass convertsheaderJsonandclainsJsontohashmapand then to string in order for token authentication. The elements in thehashmapare not guaranteed to be in the same order always which introduces a vulnerability in the code, however elements in aLinkedHashmapare guaranteed to be stored in a particular order. The authentication may fail and result inINVALID_PROVIDER_TOKENeven if it is correct.Fix: Use
LinkedHashMapinsteadHashMapTests Plan: