QA nits from #490: silent test skip + import formatting #492
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#492
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
QA nits from PR #490 review (2026-04-17). Per
feedback_nits_to_epilogue.md, nits must be tracked — filed here instead of dismissed.Repo
forgejo_admin/basketball-apiUser Story
As an engineer, I trust every regression test is actually asserting behavior (not silently skipping), and imports follow a single consistent convention across the module.
What Broke
Two minor quality issues in the #490 diff:
tests/test_checkout_session_ttl.py::test_register_promo_discount_path_sets_expires_atusespytest.skip(...)on a branch that, if refactored, could silently no-op forever without flagging. A future change could make this test a permanent pass-by-default.routes/checkout.py,routes/jersey.py,services/tournament_checkout.pyhave splitfrom basketball_api.config import ...imports that could be collapsed to match the combined-form convention already used inadmin.pyandregister.py.Repro Steps
tests/test_checkout_session_ttl.py, locatetest_register_promo_discount_path_sets_expires_at, observepytest.skip(...)without a branch-taken assertionfrom basketball_api.config import X, Ypatterns where the single-line form fits cleaneradmin.py/register.pycombined importsExpected Behavior
pytest.fail(...)or a stricter assertion guaranteeing the tested branch was exercisedEnvironment
tests/test_checkout_session_ttl.py,routes/checkout.py,routes/jersey.py,services/tournament_checkout.pyAcceptance Criteria
Related
project-pal-e-platformforgejo_admin/basketball-api #488, #490— parent fix PR