spec-test-execute

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Spec 测试执行与报告（V4：Execute + Report）

Spec Test Execution and Report (V4: Execute + Report)

本技能产出“结论性测试报告”：回答 是否满足 AC、是否可交付、阻断点是什么、下一步动作是什么。

权威口径：

design/aisdlc_spec_verification.md

This skill produces a "conclusive test report" that answers whether AC is met, whether it is deliverable, what the blocking points are, and what the next actions are.

Official Specification:

design/aisdlc_spec_verification.md

硬门禁（必须遵守）

Hard Access Control (Mandatory Compliance)

先定位再读写：必须先运行
```
spec-context
```
得到并回显
```
FEATURE_DIR=...
```
；失败即停止，禁止猜路径。

必读项目级 memory：

project/memory/product.md

、

project/memory/tech.md

、

project/memory/glossary.md

；读不到必须写

CONTEXT GAP

。

输入依赖：

verification/test-plan.md

与

verification/usecase.md

必须存在；

verification/suites.md

若存在则纳入覆盖统计。

缺陷不在 Spec Pack 落盘：禁止新建
```
verification/bugs/**
```
；报告只做“缺陷编号/链接/状态/严重程度”的引用清单。
禁止越权路由：完成后只输出
```
ROUTER_SUMMARY
```
，下一步由
```
using-aisdlc
```
决策。

Locate path before read/write: You must run
```
spec-context
```
first to get and echo
```
FEATURE_DIR=...
```
; stop immediately if it fails, do not guess the path.
Mandatory reading of project-level memory:
```
project/memory/product.md
```
,
```
project/memory/tech.md
```
,
```
project/memory/glossary.md
```
; if you cannot read them, you must write
```
CONTEXT GAP
```
.
Input dependencies:
```
verification/test-plan.md
```
and
```
verification/usecase.md
```
must exist; if
```
verification/suites.md
```
exists, include it in coverage statistics.
Defects are not stored in Spec Pack: Do not create new
```
verification/bugs/**
```
; the report only includes a reference list of "defect ID/link/status/severity".
No unauthorized routing: Only output
```
ROUTER_SUMMARY
```
after completion, the next step is decided by
```
using-aisdlc
```
.

红旗清单（出现任一条就停止）

Red Flag Checklist (Stop if any item occurs)

想在缺少
```
test-plan.md
```
/
```
usecase.md
```
的情况下写“结论性报告”
想把缺陷细节落盘到
```
verification/bugs/**
```
（本阶段只允许引用外部缺陷系统）
想在版本未知时写固定版本号或用
```
TBD
```
代替（必须用
```
unknown
```
并显式
```
CONTEXT GAP
```
）

Attempting to write a "conclusive report" without
```
test-plan.md
```
/
```
usecase.md
```
Attempting to store defect details in
```
verification/bugs/**
```
(only references to external defect systems are allowed in this phase)
Attempting to write a fixed version number or use
```
TBD
```
when the version is unknown (you must use
```
unknown
```
and explicitly mark
```
CONTEXT GAP
```
)

唯一做法（PowerShell）

Only Valid Procedure (PowerShell)

1) 获取

FEATURE_DIR

1) Get

FEATURE_DIR

powershell

. ".\skills\spec-context\scripts\spec-common.ps1"
$context = Get-SpecContext
$FEATURE_DIR = $context.FEATURE_DIR
Write-Host "FEATURE_DIR=$FEATURE_DIR"

powershell

. ".\skills\spec-context\scripts\spec-common.ps1"
$context = Get-SpecContext
$FEATURE_DIR = $context.FEATURE_DIR
Write-Host "FEATURE_DIR=$FEATURE_DIR"

2) 命名规则（强制）

2) Naming Rules (Mandatory)

```
date
```
：
```
YYYY-MM-DD
```
```
version
```
：构建/发布可追溯标识（版本号、build id、git sha）

若版本未知：使用

report-{date}-unknown.md

，并在报告中写明

CONTEXT GAP: version/build unknown

```
date
```
:
```
YYYY-MM-DD
```
```
version
```
: Traceable identifier for build/release (version number, build id, git sha)

If the version is unknown: use

report-{date}-unknown.md

, and write

CONTEXT GAP: version/build unknown

in the report.

3) 目标输出路径（示例）

3) Target Output Path (Example)

powershell

$date = "2026-03-02"
$version = "unknown"
$out = Join-Path $FEATURE_DIR ("verification/report-{0}-{1}.md" -f $date, $version)
Write-Host "OUTPUT=$out"

powershell

$date = "2026-03-02"
$version = "unknown"
$out = Join-Path $FEATURE_DIR ("verification/report-{0}-{1}.md" -f $date, $version)
Write-Host "OUTPUT=$out"

报告最小结构（建议）

Minimum Report Structure (Recommendation)

写入

{FEATURE_DIR}/verification/report-{date}-{version}.md

，至少包含：

测试摘要
- 结论：通过 / 不通过 / 有条件通过
- 版本/构建/环境（未知必须写
```
CONTEXT GAP
```
  ）
覆盖统计
- 按套件/优先级：总数、执行数、通过、失败、阻塞、未执行
关键失败与阻断项
- 必须可追溯到用例编号（TC-...）
缺陷清单（仅引用）
- 缺陷系统/Issue 编号 + 链接 + 状态 + 严重程度
遗留风险与建议
- 下一步动作必须可执行（返工/补测/灰度/加监控/回滚建议）

追溯链接

requirements/*

、

verification/test-plan.md

、

verification/usecase.md

、（可选）

verification/suites.md

Write to

{FEATURE_DIR}/verification/report-{date}-{version}.md

, including at least:

Test Summary
- Conclusion: Pass / Fail / Conditional Pass
- Version/Build/Environment (must write
```
CONTEXT GAP
```
  if unknown)
Coverage Statistics
- By suite/priority: Total, Executed, Passed, Failed, Blocked, Not Run
Key Failures and Blockers
- Must be traceable to test case ID (TC-...)
Defect List (References only)
- Defect system/Issue ID + link + status + severity
Remaining Risks and Recommendations
- Next actions must be executable (rework/retest/gray release/add monitoring/rollback suggestions)

Traceability Links

requirements/*

verification/test-plan.md

verification/usecase.md

, (optional)

verification/suites.md

DoD 自检（V4-DoD）

DoD Self-Check (V4-DoD)

报告有明确结论（不是“已测完”）
所有失败/阻断项都能定位到
```
TC-*
```
与外部缺陷编号（如有）
风险与建议可执行（下一步动作明确）

The report has a clear conclusion (not "test completed")
All failures/blockers can be linked to
```
TC-*
```
and external defect IDs (if any)
Risks and recommendations are executable (next actions are clear)

输出约定（交还 Router）

Output Convention (Return to Router)

text

ROUTER_SUMMARY
- feature_dir: <FEATURE_DIR>
- outputs:
  - verification/report-<date>-<version>.md
- context_gaps:
  - <CONTEXT GAP...> (if any)
- dod:
  - pass: <yes/no> (and why)
  - next_risks: <short list>

name: spec-test-execute description: Use when 需要在 sdlc-dev 的 Spec Pack 中执行 verification 阶段验证（V4），记录执行结果并产出报告输出物 report-{date}-{version}.md（作为执行的证据与结论载体）。

text

ROUTER_SUMMARY
- feature_dir: <FEATURE_DIR>
- outputs:
  - verification/report-<date>-<version>.md
- context_gaps:
  - <CONTEXT GAP...> (if any)
- dod:
  - pass: <yes/no> (and why)
  - next_risks: <short list>

name: spec-test-execute description: Use when you need to perform verification phase validation (V4) in the Spec Pack of sdlc-dev, record execution results and produce the report output

report-{date}-{version}.md

(as the carrier of execution evidence and conclusions).

Spec 测试执行（V4：执行验证并产出报告）

Spec Test Execution (V4: Perform Validation and Generate Report)

概览

Overview

本技能是 verification 阶段 worker skill，只负责：

门禁校验（先定位
```
{FEATURE_DIR}
```
，再读必要输入）
执行验证（可为手工执行/自动化执行的记录；不绑定框架）

产出执行输出物：

{FEATURE_DIR}/verification/report-{date}-{version}.md

按 V4-DoD 自检（结论性 + 可追溯）
输出
```
ROUTER_SUMMARY
```
后回到
```
using-aisdlc
```

本技能不决定下一步做什么（由

using-aisdlc

路由）。

This skill is a worker skill for verification phase, only responsible for:

Access control verification (first locate
```
{FEATURE_DIR}
```
, then read necessary inputs)
Execution validation (can be records of manual execution/automated execution; no framework binding)

Produce execution output:

{FEATURE_DIR}/verification/report-{date}-{version}.md

Self-check according to V4-DoD (conclusive + traceable)
Output
```
ROUTER_SUMMARY
```
and return to
```
using-aisdlc
```

This skill does not decide what to do next (routed by

using-aisdlc

报告命名规则（强制）

Report Naming Rules (Mandatory)

文件名：
```
report-{date}-{version}.md
```
```
date
```
：
```
YYYY-MM-DD
```
```
version
```
：构建/发布版本号或可追溯标识（例如
```
v1.7.3
```
、
```
build-20260302.1
```
、
```
sha-abc1234
```
）

若

version

无法获得：仍可生成报告，但必须：

文件名使用
```
report-{date}-unknown.md
```
在报告内写
```
CONTEXT GAP: version/build unknown
```
，并在结论中降低置信度（通常为有条件通过/不通过，取决于准出标准与阻断项）

File name:
```
report-{date}-{version}.md
```
```
date
```
:
```
YYYY-MM-DD
```
```
version
```
: Build/release version number or traceable identifier (e.g.
```
v1.7.3
```
,
```
build-20260302.1
```
,
```
sha-abc1234
```
)

version

is not available: you can still generate the report, but you must:

Use
```
report-{date}-unknown.md
```
as the file name
Write
```
CONTEXT GAP: version/build unknown
```
in the report, and reduce the confidence level in the conclusion (usually conditional pass/fail, depending on the release criteria and blockers)

硬门禁（不得绕过）

Hard Access Control (Cannot Be Bypassed)

1) 先定位 FEATURE_DIR（禁止猜路径）

1) Locate FEATURE_DIR first (do not guess the path)

powershell

. ".\skills\spec-context\scripts\spec-common.ps1"
$context = Get-SpecContext
$FEATURE_DIR = $context.FEATURE_DIR
Write-Host "FEATURE_DIR=$FEATURE_DIR"

失败即停止。

powershell

. ".\skills\spec-context\scripts\spec-common.ps1"
$context = Get-SpecContext
$FEATURE_DIR = $context.FEATURE_DIR
Write-Host "FEATURE_DIR=$FEATURE_DIR"

Stop immediately if failed.

2) 必读项目级 Memory（缺失写 CONTEXT GAP）

2) Mandatory reading of project-level Memory (write CONTEXT GAP if missing)

```
.aisdlc/project/memory/product.md
```
```
.aisdlc/project/memory/tech.md
```
```
.aisdlc/project/memory/glossary.md
```

任一缺失：在报告中显式写

CONTEXT GAP

，并说明它如何影响结论可信度。

```
.aisdlc/project/memory/product.md
```
```
.aisdlc/project/memory/tech.md
```
```
.aisdlc/project/memory/glossary.md
```

If any is missing: explicitly write

CONTEXT GAP

in the report, and explain how it affects the credibility of the conclusion.

3) 必须读取 verification 输入

3) Must read verification inputs

执行前必须读取：

```
{FEATURE_DIR}/verification/test-plan.md
```
```
{FEATURE_DIR}/verification/usecase.md
```
```
{FEATURE_DIR}/verification/suites.md
```
（如存在）

若缺失：停止并回到

using-aisdlc

（因为无法证明范围/口径/覆盖）。

Must read before execution:

```
{FEATURE_DIR}/verification/test-plan.md
```
```
{FEATURE_DIR}/verification/usecase.md
```
```
{FEATURE_DIR}/verification/suites.md
```
(if exists)

If missing: stop and return to

using-aisdlc

(since scope/specification/coverage cannot be proven).

执行记录要求（最小）

Execution Record Requirements (Minimum)

以
```
usecase.md
```
的用例编号（
```
TC-...
```
）为最小统计单位
每条用例必须给出结果：Pass / Fail / Blocked / Not Run
Fail/Blocked 必须给出：
- 对应
```
TC-...
```
- 外部缺陷编号/链接（或明确写“尚未提缺陷”的阻断原因与下一步动作）
禁止在 Spec Pack 内新增
```
verification/bugs/**
```

Use the test case ID (
```
TC-...
```
) in
```
usecase.md
```
as the minimum statistical unit
Each test case must have a result: Pass / Fail / Blocked / Not Run
Fail/Blocked must provide:
- Corresponding
```
TC-...
```
- External defect ID/link (or clearly state the blocking reason and next action for "defect not yet submitted")
Do not add
```
verification/bugs/**
```
in the Spec Pack

输出（落盘）

Output (Write to Disk)

{FEATURE_DIR}/verification/report-{date}-{version}.md

{FEATURE_DIR}/verification/report-{date}-{version}.md

报告最小结构（必须包含）

Minimum Report Structure (Must Include)

测试摘要
- 结论：通过 / 不通过 / 有条件通过（三选一）
- 版本/构建/环境
- 执行日期（与文件名 date 一致）
覆盖统计
- 按优先级与（如存在）套件：总数、执行数、通过、失败、阻塞、未执行
用例结果清单
- ```
TC-...
```
  → Pass/Fail/Blocked/Not Run
关键失败与阻断项
- 每条必须可追溯到 TC 编号
缺陷清单（仅引用外部系统）
- 缺陷编号/链接/状态/严重度
- 必须关联到对应 TC 编号
遗留风险与建议（可执行下一步动作）
追溯链接（requirements/design/implementation 的关键入口）
CONTEXT GAP（如有）

Test Summary
- Conclusion: Pass / Fail / Conditional Pass (choose one of three)
- Version/Build/Environment
- Execution date (consistent with the date in the file name)
Coverage Statistics
- By priority and (if exists) suite: Total, Executed, Passed, Failed, Blocked, Not Run
Test Case Result List
- ```
TC-...
```
  → Pass/Fail/Blocked/Not Run
Key Failures and Blockers
- Each item must be traceable to TC ID
Defect List (only reference external systems)
- Defect ID/link/status/severity
- Must be associated with the corresponding TC ID
Remaining Risks and Recommendations (executable next actions)
Traceability Links (key entries for requirements/design/implementation)
CONTEXT GAP (if any)

V4-DoD 自检

V4-DoD Self-Check

报告给出明确结论（不是“已测完”）
所有失败/阻断项均可定位到 TC 编号与外部缺陷编号/链接
统计口径可解释（为何未执行/为何阻断）
风险与建议可执行（下一步动作明确）

The report gives a clear conclusion (not "test completed")
All failures/blockers can be linked to TC ID and external defect ID/link
Statistical caliber is explainable (why not executed/why blocked)
Risks and recommendations are executable (next actions are clear)

红旗 STOP

Red Flag STOP

未回显
```
FEATURE_DIR=...
```
就开始执行/落盘报告
结论写“通过”，但存在未执行/阻断项且未解释
Fail/Blocked 没有关联 TC 编号或外部缺陷引用

Start execution/write report to disk without echoing
```
FEATURE_DIR=...
```
Conclusion is "Pass" but there are unexecuted/blocked items without explanation
Fail/Blocked is not associated with TC ID or external defect reference

输出约定（给 Router）

Output Convention (For Router)

text

ROUTER_SUMMARY
- FEATURE_DIR=...
- report_written: verification/report-{date}-{version}.md
- execution_summary:
  - totals: { planned: ?, executed: ?, pass: ?, fail: ?, blocked: ?, not_run: ? }
  - blockers: [ ... ]
- context_gaps: [...]
- open_risks: [...]
- blocked_by: [...]
- router_hints: ["回到 using-aisdlc 继续路由"]

text

ROUTER_SUMMARY
- FEATURE_DIR=...
- report_written: verification/report-{date}-{version}.md
- execution_summary:
  - totals: { planned: ?, executed: ?, pass: ?, fail: ?, blocked: ?, not_run: ? }
  - blockers: [ ... ]
- context_gaps: [...]
- open_risks: [...]
- blocked_by: [...]
- router_hints: ["回到 using-aisdlc 继续路由"]