WorkBuddy
ae1bd2b734
Phase 23 "可信系统测试重建 (REFACTOR)" re-audit. STATUS claimed "10 E2E
files / ~80+ cases" and "INV-011~020 ✅"; measurement showed the opposite.
D-23-A (Critical): V11InvariantsTest's 14 cases asserted only Constants
strings. INV-016 "Banner target types" actually asserted ARTICLE_STATUS_*;
INV-017 "home 8 entries" declared local arrays then asserted
firstRow.length == 4 (tautology, never called the home service);
INV-018/019/020 used appointment/article/account status constants as
stand-ins for permission and data-scope checks. Rewritten to 12 cases:
4 real service-behavior guards (INV-013 via real CounselingService.getDetail
— Matchmaker sees null userRequestSummary, with an assigned-Counselor
counter-proof so global sanitization cannot fake a pass; INV-016 reads the
production ALLOWED_TARGET_TYPES whitelist and asserts no external/http/url/
web entry; INV-017 calls real getHome and pins all 8 codes + order;
INV-019 asserts content_editor reads null), plus assertBehaviorTestExists
turning "行为验证见 XxxTest" pointers into executable Class.forName contracts.
D-23-B (High): 44 `pass` shells across 6 files in tests/e2e (4 files were
100% shells). Gate forbids skip/pass shells. Rewritten in place as honest
placeholders with the full scenario lists preserved.
D-23-C (High, residual): the pytest E2E suite is not executable at all —
no conftest.py anywhere, ~15 fixtures (api_client/verified_user/
banner_factory/...) do not exist. Only run_v11_tests.py really runs
(16 cases, needs a live stack + E2E_PASSWORD).
D-23-D (High, residual, NOT fixed): CI does not chain E2E as the plan
requires. Needs an infrastructure decision on how CI provisions a live
stack; not implemented rather than written unverified.
D-23-E (Medium): the CI migration job claimed to "验证 migration SQL 语法"
but only checked file non-emptiness, while the real syntax/baseline checks
live in MigrationValidationTest (already run by the backend job). Replaced
with a real sequence check (naming / non-empty / unique versions / no
gaps); verified by extracting the exact inline script and running it.
New gate: scripts/check-no-empty-tests.py (AST scan, blocks pass-only and
unconditionally skipped tests) + a CI test-shell-guard job. Verified both
ways: 0 findings on the real tree, 2 precise findings on injected shells.
Negative validation: 3 injected production defects (external_url in the
banner whitelist, swapped home entry order, isMatchmaker returning the full
record) turned exactly inv016/inv017/inv013 red, 9 others green, zero
unrelated failures; md5sum -c confirmed byte-identical restore.
Full regression: 655 tests / 652 passed / 0 failures / 0 errors / 3 skipped
(baseline 657; -2 because 14 vacuous cases were merged into 12). The 3
skips carry explicit reasons (2x @EnabledIfEnvironmentVariable(CI=true),
1x @Disabled "需要完整数据库连接") — none is a shell.
Phase 23 is PARTIALLY closed: fake coverage is gone, but the UAT gate
requires the end-to-end chain to actually execute, so "失败为零可进入 UAT"
is NOT claimed.
36 lines
1.3 KiB
Python
36 lines
1.3 KiB
Python
"""
|
||
V1.1 服务预约 E2E —— 空壳已移除（Phase 23 KEEP-VERIFY，2026-09-18）
|
||
|
||
历史问题
|
||
--------
|
||
原文件 7 个测试函数**全部**为 `pass` 空壳（注释「TODO: P19 实现后完善」），
|
||
依赖不存在的 `service_location_factory` / `appointment_factory` / `operator_client`
|
||
等 fixture（全局无 `conftest.py`），从未执行过，
|
||
却在 `docs/STATUS.md` 中被计为 P23-T08「服务预约 E2E ✅」。
|
||
|
||
计划 Phase 23 Gate：「**不允许 skip/pass 空壳**」。
|
||
|
||
当前状态
|
||
--------
|
||
本文件现**不含任何测试函数**，pytest 收集 0 个用例。
|
||
|
||
仍待真实实现的场景（需求不因移除空壳而丢失）
|
||
------------------------------------------
|
||
1. 用户可提交服务预约
|
||
2. 预约提交支持幂等（Idempotency-Key）
|
||
3. 后台可确认预约
|
||
4. 同一预约同时取消与确认的并发安全性
|
||
5. 我的预约列表正确
|
||
6. 待确认状态可取消
|
||
7. 已确认状态不可自行取消
|
||
|
||
现状补充（Phase 23 实测）
|
||
------------------------
|
||
预约 owner 归属与数据范围已有真实后端测试：
|
||
`ServiceAppointmentOwnerGuardTest`、`ServiceAppointmentDataScopeTest`。
|
||
预约创建链路在 `tests/e2e/run_v11_tests.py::test_06_service_appointment`
|
||
中有真实 HTTP 覆盖。E2E 层其余场景待补。
|
||
|
||
真实可执行的 V1.1 E2E 见：`tests/e2e/run_v11_tests.py`
|
||
"""
|