SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsspec-test-execute

spec-test-execute

Testing & quality

View repository

Updated 10-16 01:58

About this skill

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

This skill produces a "conclusive test report": answering whether the ACs are satisfied, whether it is deliverable, what the blockers are, and what the next actions are。

Inputs and Gates (must be followed)

REQUIRED SUB-SKILL: currently executing spec-context to obtain context, and echo in the conversation FEATURE_DIR=...(allowed (reuse)）。

  • locate first, then read/write: must first obtain via spec-context Get FEATURE_DIR; stop on failure, guessing paths is prohibited.
  • Must-read project-level memory：project/memory/product.md、project/memory/tech.md、project/memory/glossary.md; if unreadable, must write CONTEXT GAP。
  • Input dependencies：verification/test-plan.md and verification/usecase.md must exist;verification/suites.md if present, include in coverage statistics.
  • Defects are not persisted in the Spec Pack: creating new verification/bugs/**is prohibited; the report only provides a reference list of "defect number/link/status/severity".
  • Defect write-back (mandatory): after a defect is created/updated in an external system, it must be written back to this round's report-*.md "defect list", and linked to the corresponding TC-*。

Output (persisted)

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

Naming rule:

  • date：YYYY-MM-DD
  • version: build/release traceable identifier (version number, build id, git sha); if unknown, use unknown and write in the report CONTEXT GAP: version/build unknown

Mandatory template (must be followed)

  • report-*.md must be generated according to the template (structure/field names must not be invented):
    • assets/report_template.md

Content requirements (minimum structure)

report-*.md must at least include:

  • Test summary
    • Conclusion: Pass / Fail / Conditional Pass
    • Version/build/environment (if unknown, must write CONTEXT GAP）
  • Coverage statistics
    • By suite/priority: total, executed, passed, failed, blocked, not executed
  • AC↔TC coverage mapping
    • At minimum, must answer "which ACs are covered by which TCs; which ACs still have gaps (Gap)"
  • Key failures and blockers
    • Must be traceable to test case numbers (TC-...)
  • Defect list (reference only)
    • Defect system/Issue number + link + status + severity
    • Must be linked to the corresponding TC-*; if a defect has not yet been filed, must state the blocking reason and next actions (must not be left dangling)
  • Residual risks and recommendations
    • Next actions must be executable (rework/retest/canary/monitoring/rollback recommendations)
  • Traceability links
    • requirements/*、verification/test-plan.md、verification/usecase.md, (optional)verification/suites.md
  • CONTEXT GAP (if any)

DoD self-check (V4-DoD)

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