report

Solid

Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".

AI & Automation 61 stars 15 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
60
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Smart Test Reporting Generate test reports that plug into the user's existing workflow. Zero new tools. ## Steps ### 1. Run Tests (If Not Already Run) Check if recent test results exist: ```bash ls -la test-results/ playwright-report/ 2>/dev/null ``` If no recent results, run tests: ```bash npx playwright test --reporter=json,html,list 2>&1 | tee test-output.log ``` ### 2. Parse Results Read the JSON report: ```bash npx playwright test --reporter=json 2> /dev/null ``` Extract: - Total tests, passed, failed, skipped, flaky - Duration per test and total - Failed test names with error messages - Flaky tests (passed on retry) ### 3. Detect Report Destination Check what's configured and route automatically: | Check | If found | Action | |---|---|---| | `TESTRAIL_URL` env var | TestRail configured | Push results via `/pw:testrail push` | | `SLACK_WEBHOOK_URL` env var | Slack configured | Post summary to Slack | | `.github/workflows/` | GitHub Actions | Results go to PR comment via artifacts | | `playwright-report/` | HTML reporter | Open or serve the report | | None of the above | Default | Generate markdown report | ### 4. Generate Report #### Markdown Report (Always Generated) ```markdown # Test Results — {{date}} ## Summary - ✅ Passed: {{passed}} - ❌ Failed: {{failed}} - ⏭️ Skipped: {{skipped}} - 🔄 Flaky: {{flaky}} - ⏱️ Duration: {{duration}} ## Failed Tests | Test | Error | File | |---|---|---| | {{name}} | {{error}} | {{file}}:{{line}} | ## Flaky Tests |...

Details

Author
adriannoes
Repository
adriannoes/awesome-agentic-ai
Created
11 months ago
Last Updated
1 weeks ago
Language
Jupyter Notebook
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

run-report

Produce an execution report from a Playwright run in the formats the QA profession consumes - JUnit XML, Cucumber JSON, and a self-contained HTML summary - with requirement traceability. Use after running an automated suite, when a CI dashboard or an ALM needs the results, or when someone asks what the last run actually produced.

0 Updated 3 weeks ago
QAIA-Project
Data & Documents Listed

test-reporting

When the user wants to design, integrate, or improve test reporting — JUnit XML aggregation, HTML dashboards, Allure, Cucumber Reports, screenshots / videos / traces, failure triage, and historical analytics. Use when the user mentions "test reports," "JUnit XML," "Allure," "mochawesome," "Cucumber Reports," "Datadog CI Visibility," "Buildkite Test Analytics," "test result aggregation," "trace / artifacts on failure," "test dashboard," or "trend analysis." For CI orchestration see ci-test-orchestration. For flake analytics see flaky-test-management.

4 Updated 1 weeks ago
aks-builds
Testing & QA Listed

pw-test-step-reporter

Structures a Playwright test so it explains itself in the HTML report — test.step for logical phases, testInfo.attach for evidence (screenshots, JSON, diffs), expect.soft with a hard gate for grouped checks, and annotations for issue/bug-ID traceability. Use when an SDET says "make this test's report readable", "group this into steps", "attach a screenshot to the report", "how do I do soft assertions", or "why can't I tell which step failed in CI". Produces a report a human can debug from without re-running the test — a draft the engineer reviews and runs.

1 Updated 1 weeks ago
Shivani26Singh