Fix stale SAML backend tests#620
Merged
Merged
Conversation
JackWilb
marked this pull request as ready for review
July 13, 2026 20:53
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
1 participant
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
SanguineSaml2Backend/apiproduction defaultRoot cause
Commit
f0d26cf7removed the broken custom SAML backend and switched production todjangosaml2.backends.Saml2Backend, but its tests continued importing and exercising the deleted class. Once that collection error was removed, the suite exposed a second stale expectation for the old/redirect default.Validation
poetry check --lockpython manage.py check --settings=api.test_settingspython manage.py makemigrations --check --dry-run --settings=api.test_settingspython manage.py test --settings=api.test_settings(16 tests)git diff --check