| name | cypress-reporter-zephyr |
| description | Test-management reporting skill for Zephyr Scale. Use when Codex needs to publish Cypress execution results into Zephyr using the project's mappings, environment configuration, and chosen reporting flow. |
| metadata | {"author":"jovd83","version":"1.1","dispatcher-category":"testing","dispatcher-capabilities":"test-management-reporting, cypress-test-management-reporting","dispatcher-accepted-intents":"report_cypress_test_results","dispatcher-input-artifacts":"execution_results, test_management_config, mappings","dispatcher-output-artifacts":"published_results, reporting_summary","dispatcher-stack-tags":"cypress, reporting, test-management","dispatcher-risk":"medium","dispatcher-writes-files":true} |
Telemetry & Logging
[!IMPORTANT]
All usage of this skill must be logged via the Skill Dispatcher to ensure audit logs and wallboard analytics are accurate:
./log-dispatch.cmd --skill <skill_name> --intent <intent> --model <model_name> --reason <reason> (or ./log-dispatch.sh on Linux)
Zephyr Scale API Reporter
Use this skill when the goal is to push execution outcomes into Zephyr.
Action
Inputs:
- Zephyr connection details and credentials,
- the local result source,
- the mapping from automated tests to Zephyr case IDs,
- any target run, build, or environment context required by the project.
Workflow:
- Confirm the mapping and target run 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.
