| name | playwright-reporter-zephyr |
| description | Test-management reporting skill for Zephyr Scale. Use when Codex needs to publish Playwright execution results into Zephyr using the project's mappings, run configuration, and chosen reporting flow. |
| metadata | {"author":"jovd83","version":"2.0.0","dispatcher-category":"testing","dispatcher-capabilities":"test-management-reporting, playwright-test-management-reporting","dispatcher-accepted-intents":"report_playwright_test_results","dispatcher-input-artifacts":"execution_results, test_management_config, mappings","dispatcher-output-artifacts":"published_results, reporting_summary","dispatcher-stack-tags":"playwright, reporting, test-management","dispatcher-risk":"medium","dispatcher-writes-files":true} |
Zephyr Reporter
Use this skill when the goal is to push execution outcomes into Zephyr Scale.
Inputs
- Zephyr connection details and credentials,
- the local result source,
- the mapping from automated tests to Zephyr keys,
- any target cycle, execution, or environment context required by the project.
Workflow
- Confirm the mapping and target execution context.
- Configure the reporting path or client the project uses.
- Publish results securely.
- Return a concise report of what was sent and what could not be reported.
Guardrails
- Never echo secrets back in plain text.
- Do not report results for tests that cannot be mapped confidently.
- Call out partial publication explicitly.