Bug: 9 pre-existing test failures from removed opt_out jersey option #300
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/basketball-api#300
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Bug
Lineage
Standalone — discovered during email architecture validation (2026-04-03). Pre-existing regression, not caused by email work. Traced to removal of
opt_outjersey option (likely #263).Repo
forgejo_admin/basketball-apiWhat Broke
9 tests fail on main because they send
{"option": "opt_out"}which is no longer a validJerseyOptionenum value. The API returns 422 (validation error) instead of the expected 200 or 403. This blocks the CI pipeline — theupdate-kustomize-tagstep skips when tests fail, requiring manual image tag updates to deploy.Failing tests:
test_checkout.py::TestPlayerIdCheckoutCreateSession— 3 failurestest_dual_auth.py::TestJerseyCheckoutDualAuth— 2 failurestest_dual_auth.py::TestCheckoutCreateSessionDualAuth— 1 failuretest_jersey.py::TestPlayerIdJerseyCheckout— 3 failuresRepro Steps
git checkout main && git pullpytest tests/test_checkout.py tests/test_dual_auth.py tests/test_jersey.py -vassert 422 == 200orassert 422 == 403Expected Behavior
All tests pass. CI pipeline goes green.
update-kustomize-tagstep runs automatically on merge.Environment
fb24245(latest main)Acceptance Criteria
pytestruns green on main (748+ pass, 0 fail)update-kustomize-tagstepRelated
project-westside-basketball— parent project