post-test-report

name	post-test-report
description	Phase 3 of web-app-tester. Computes the overall verdict (PASSED / FAILED / BLOCKED) from the inline step results, composes a report that conforms exactly to the report template, and posts it via the correct provider (GitHub or Azure DevOps). For wi entry points on Azure DevOps, also posts a notification comment on the work item. The report is strictly bounded — no recommendations, no root-cause analysis, no commentary outside the defined sections.
disable-model-invocation	true

Phase 3 — Post Test Execution Report

This skill is invoked by the orchestrator agent. It is not a standalone slash command.

Inputs

Variable	Source	Description
Inline result list	run-playwright-session	One entry per step: { n, desc, status, reason, screenshot }
TEST_URL	gather-test-context	URL that was tested
PRODUCTION_WARNING	gather-test-context	Whether read-only mode was applied
ENTRY_TYPE	orchestrator	pr, issue, or wi
ENTRY_ID	orchestrator	PR number, issue number, or work item ID
PLATFORM	orchestrator	GitHub or AzureDevOps
LINKED_PR_ID	gather-test-context	Azure DevOps wi entry only: the PR linked to the work item

Outputs

A single report comment posted on the PR or issue, plus (for wi entry) a notification on the work item, plus a one-line confirmation written to stdout.

---

Step 1: Compute Overall Verdict

Determine the overall result from the per-step statuses:

Condition	Overall Result
All steps passed	PASSED
One or more steps failed (all steps were attempted)	FAILED
One or more steps could not execute (element not found, page error, timeout, auth gate, production-mode skip)	BLOCKED

A run with both FAILED and BLOCKED steps uses BLOCKED as the overall result.

Store as OVERALL_RESULT, PASSED (count), FAILED (count), BLOCKED (count), TOTAL (count).

---

Step 2: Compose the Report Body

Build the comment body using the exact structure defined in styles/report-template.md. The report comment must contain only the sections defined in that template. Do not add suggested fixes, recommendations, next steps, root cause analysis, explanations, or any content not defined in the template. If you have observations beyond the test results, discard them — they do not belong in this comment.

The skeleton is:

🤖 web-app-tester — Test Execution Report
URL tested: {TEST_URL}
{PRODUCTION_WARNING ? "⚠️ URL appears to be production. Executed read-only steps only." : ""}
Total: N | ✅ Passed: X | ❌ Failed: Y | 🔴 Blocked: Z
Overall: PASSED / FAILED / BLOCKED

| # | Step | Status |
|---|------|--------|
| 1 | {step description} | ✅ PASSED |
| 2 | {step description} | ❌ FAILED |

[For each FAILED or BLOCKED step:]
**Step N — {description}**
Reason: {what went wrong after 3 retries}
[Screenshot attached if available]

Step descriptions in the report must be in business language — describe the user action and observed outcome, not the Playwright command. See the Step Description Format section in styles/report-template.md for examples.

For FAILED and BLOCKED steps, screenshots are described inline as "captured at point of failure" — neither GitHub nor Azure DevOps PR comments support direct file attachments, so the PNG files are not uploaded.

Store as REPORT_BODY.

---

Step 3: Post the Report

Read the correct provider file and post using the appropriate command:

GitHub

Read and follow providers/github.md.

• ENTRY_TYPE == pr → gh pr comment ${ENTRY_ID} with REPORT_BODY
• ENTRY_TYPE == issue → gh issue comment ${ENTRY_ID} with REPORT_BODY

Post a single comment. Never split the report across multiple comments.

Azure DevOps

Read and follow providers/azure-devops.md.

• ENTRY_TYPE == pr → post the full report as a PR thread comment on PR ${ENTRY_ID}
• ENTRY_TYPE == wi and LINKED_PR_ID is set → two posts:
  1. Post the full report as a PR thread comment on LINKED_PR_ID
  2. Post a notification comment on the work item ${ENTRY_ID} (brief summary only — OVERALL_RESULT, step counts, TEST_URL, reference to the PR)
• ENTRY_TYPE == wi and LINKED_PR_ID is empty → post the full report directly on the work item ${ENTRY_ID}

See providers/azure-devops.md for the exact curl commands for each case.

---

Step 4: Final Output

After posting, write a single confirmation line to stdout:

web-app-tester complete for {ENTRY_TYPE} #{ENTRY_ID}: {OVERALL_RESULT} — {PASSED}/{TOTAL} steps passed

If posting fails, output a single error line describing what failed and stop.