agf-writing-qa-report

Solid

Use when qa-engineer (or miniapp-qa-engineer) is about to publish an E2E or UAT report. Provides the report skeleton, evidence-quality bar, verdict criteria, and hand-off rules. SIT is now dev-owned and lives in progress/<role>.md (see agf-running-sit-tests skill) — this skill does NOT cover SIT reports.

Testing & QA 480 stars 14 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%

Recency 20%

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Writing a QA Report (E2E / UAT) Use this skill when: - E2E execution is complete and a report needs publishing - UAT business sign-off needs to be captured - A bug-fix E2E re-verification needs recording (always **appended** as `## Re-run [N] — [date]` to the existing `[feature]-e2e-[YYYY-MM-DD].md`; never a new file — see "File path & naming" below) **Pair with**: - `agf-running-sit-tests` skill — SIT 由 dev 自跑，本 skill 不覆盖 SIT 报告（SIT 证据已在 `progress/<role>.md` 的 `**SIT 证据**` 段，归档随 `docs/qa/<feature>-process-log.md` 走） - **UAT 用例文档** `docs/qa/[feature]-uat-cases-[date].md`（模板 `docs/qa/uat-cases-_TEMPLATE.md`，gate SSOT 见 `testing.md`「UAT 用例文档」节）— UAT 执行前生成 + 用户审核 `status: Approved`；执行证据回填用例文档（证据 SSOT），**UAT 报告引用用例 ID，不重复粘贴证据** - This skill — covers the **E2E / UAT artifact** (report file) format ## File path & naming `docs/qa/[feature-kebab-case]-[stage]-[YYYY-MM-DD].md` — Stage ∈ `{e2e, uat}`. Examples: - `docs/qa/oauth-login-e2e-2026-05-13.md` - `docs/qa/oauth-login-uat-2026-05-15.md` **One report per stage per feature.** Re-runs after defect fix → append a new `## Re-run [N] — [date]` section to the same file, do not create a new file. ## Required sections (in order) ```markdown --- # frontmatter 是 verdict 数据的唯一 SSOT（agf-verdict.py 解析；validate-verdict hook 校客观底线、agf-matrix.sh fan-in 都读这里） feature: [feature-slug] date: YYYY-MM-DD tester: qa-engineer stage: E2E # E2E | UAT report_verdict: Promote # Promote | Conditional promote | Block criti...

Details

Author: pcliangx
Repository: pcliangx/AppGenesisForge
Created: 3 months ago
Last Updated: 1 weeks ago
Language: Python
License: MIT

Integrates with

FastAPI · Backend

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Solid

qa-only

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes.

11 Updated 3 days ago

HyperAITeam

Testing & QA Solid

agf-running-sit-tests

Use when an execution-layer dev (frontend-dev / backend-dev / ai-agent-dev / ml-engineer / miniapp-dev) has finished feature code + Unit tests and is about to enter code-review. Provides the SIT scope, environment, AC-driven integration walk, and evidence sink (progress/<role>.md). SIT is now a dev-owned step, not a separate QA stage.

480 Updated 1 weeks ago

pcliangx

Code & Development Listed

report-format

Test report format with QA-XXX issue IDs compatible with code-review plugin. Defines report structure, severity levels, issue format, and detailed results.

3 Updated 4 days ago

AppVerk