Repository navigation
test: verify owned URL visibility with isolated API clients - #46
Merged
Merged
Conversation
|
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.
The own-URL API test now creates an owned URL and an administrator-owned URL, verifies the owned URL is returned and the foreign URL is hidden, then removes its test records. Authenticated fixtures use separate clients so requesting user and admin actions together cannot overwrite the user's token.
Validation: all 19 HTTP API tests passed against a disposable SQLite-backed local app; Django system checks and Python compilation passed. Returning an empty list or all URLs each failed the strengthened test. Existing Pydantic deprecation warning remains. Hosted CI currently collects HTTP tests without starting an API.