WorkBuddy
730dddde30
Phase 23 closed as PARTIAL: fake coverage was gone, but the E2E layer itself
was still empty — no conftest.py anywhere, ~15 fixtures that never existed,
6 files crashing at import on os.environ["E2E_PASSWORD"], and CI never ran E2E.
STATUS's "10 E2E files / ~80+ cases ✅" described files that had never executed.
Infrastructure delivered:
- tests/e2e/conftest.py: ApiClient (trust_env=False — a host http_proxy turns
localhost calls into 502), operator_token(username) / new_user / admin_token
fixtures, and a session probe that calls pytest.exit(4) when the stack is
unreachable. NOT skip: skip would launder "did not run" into "passed".
- pytest.ini, tests/e2e/requirements.txt, and tests/e2e/sql/
seed_e2e_operators.sql — migrations contain NO operator seed at all, so a
fresh database has zero logins; the seed creates 6 e2e accounts with role
bindings, idempotent, password injected via `psql -v pwd`.
- CI job `e2e`: compose up -> poll /health/live (timeout = fail) -> seed ->
pytest -> always teardown. Gate D-23-D is now closed.
- 8 E2E files migrated off import-time env reads; tautological assertions
(`x == t or not x`), a counselor token standing in for content_editor, and a
bare `status_code == 200` claiming to prove INV-020 were replaced with real
permission/behavior assertions.
Six real production defects found only by running against real PostgreSQL
(H2 has zero coverage for all of them):
- D-23B-A (Critical): stale V042__add_appointment_operator_register_permission.sql
left in target/classes; src had replaced it with V042__add_service_location_
announcements.sql. Packing without clean put two V042 in the jar -> Flyway
"Found more than one migration with version 042" -> app would not start.
Guard added: testBuildOutputHasNoDuplicateMigrationVersions scans build output
(src is clean, so only this catches it).
- D-23B-B (High): non-UUID path variable reached the DB -> 500 + leaked
`invalid input syntax for type uuid`. Now rejected at the controller.
- D-23B-C (High): 6 E2E files raised KeyError at import -> never collected.
- D-23B-E (Critical): permissions = 48, role_permissions for super_admin = 18,
matchmaker = 0. V015's "grant all to super_admin" was a point-in-time snapshot;
the 30 permissions added later were never granted. On a fresh stack an admin
cannot create a service station and matchmakers can do nothing. V044 restores
super_admin to its documented definition (not an expansion); the matchmaker
permission set needs a product decision and is left as a residual.
- D-23B-I (Medium): IllegalArgumentException (e.g. invalid activity type) was
unmapped -> 500. Now BAD_REQUEST.
- D-23B-J (High): `operator does not exist: uuid = character varying` — Java
ids are String, columns are uuid, PostgreSQL does not implicitly cast in
comparisons. Fixed at the source with JDBC `stringtype=unspecified` (docker
profile); production datasource comes from deploy env and needs the same.
One judgement retracted: an initial read suggested service_appointment.register
was missing. It is not — the endpoint uses service.assisted_registration, seeded
in V029, and the code deliberately avoids a duplicate permission. Nothing was
changed on that basis.
Verification: 33 E2E passed against a live stack; unreachable stack and a
missing operator password both exit 4 (never skip/pass); backend regression
656 / 0 failures / 0 errors / 3 skipped (baseline 655, +1 guard, negatively
validated by injecting a duplicate V042 -> exactly one test turned red).
38 lines
1.5 KiB
Python
38 lines
1.5 KiB
Python
"""
|
||
V1.1 新增 Operator 角色权限边界 E2E（INV-012 / INV-018 / INV-019）。
|
||
|
||
迁移说明：原文件用 counselor 的 token 去"模拟" content_editor 的权限边界
|
||
（名不副实——测的根本不是 content_editor），且 import 期读环境变量导致收集失败。
|
||
现改为真实的角色账号。
|
||
"""
|
||
import pytest
|
||
|
||
pytestmark = pytest.mark.e2e
|
||
|
||
|
||
def test_station_operator_cannot_view_counseling_queue(api, operator_token):
|
||
"""INV-012：服务站运营人员不得进入咨询队列。"""
|
||
token = operator_token("e2e_station")
|
||
resp = api.call("GET", "/counseling/services/operator/queue", token=token)
|
||
assert resp.status_code == 403, (
|
||
f"服务站运营竟能查看咨询队列：HTTP {resp.status_code} {resp.text[:200]}"
|
||
)
|
||
|
||
|
||
def test_counselor_cannot_view_all_service_appointments(api, operator_token):
|
||
"""INV-012：咨询师不得浏览全量服务预约。"""
|
||
token = operator_token("e2e_counselor")
|
||
resp = api.call("GET", "/service-appointments/operator/list", token=token)
|
||
assert resp.status_code == 403, (
|
||
f"咨询师竟能浏览全量预约：HTTP {resp.status_code} {resp.text[:200]}"
|
||
)
|
||
|
||
|
||
def test_content_editor_cannot_access_appeals(api, operator_token):
|
||
"""INV-019：内容编辑员不得访问申诉等用户数据处理职能。"""
|
||
token = operator_token("e2e_content")
|
||
resp = api.call("GET", "/operator/appeals/pending", token=token)
|
||
assert resp.status_code == 403, (
|
||
f"内容编辑员竟能访问申诉队列：HTTP {resp.status_code} {resp.text[:200]}"
|
||
)
|