RANGER-5565:Resolve Unit Test Failures Caused by RANGER-5538#927
Merged
Conversation
d305654 to
9fc9661
Compare
dineshkumar-yadav
approved these changes
Apr 27, 2026
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.
What changes were proposed in this pull request?
Fixed unit test failure in TestRangerKRBAuthenticationFilter due to updated authentication flow.
Removed outdated unit test testProtectedDoFilter_usesSessionUserNameKeyadminPath which relied on unused suser parameter and path-based logic. Updated tests to align with current cookie-based authentication flow in RangerKRBAuthenticationFilter.
How was this patch tested?
Executed unit tests using: mvn clean compile package install
Confirmed no regressions or failures in other test cases.