sparq:publish-results

Publish E2E test results from CI workflows to TestRail, Qase, or Zephyr Scale TMS.

27|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-publish-results
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparq:publish-results
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-publish-results
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-publish-results

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing E2E test execution results from Playwright/Cypress back to TestRail, Qase, or Zephyr Scale TMS after CI runs. Use when: (1) posting pass/fail results from a completed CI run to a TMS, (2) creating a test run record in TestRail or Qase from Playwright JSON or JUnit XML output, (3) syncing CI results back to the test management system.

Core Features & Use Cases

  • Reads Playwright JSON reporter output from playwright-report/results.json or test-results/**/*.xml, maps test titles to TC IDs embedded as TC-XYZ-ABC-123 (regex: TC-[A-Z0-9]+-[A-Z0-9]+-\d+), creates a test run in the configured TMS, and posts pass/fail/skip per matched test case. Tests with no TC ID are grouped into an "Untracked Tests" run. Falls back to a local CSV file when MCP is unavailable.

Quick Start

Run the publish workflow after CI completes to synchronize test results with the configured TMS.

Frequently Asked Questions about sparq:publish-results

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish Playwright test results to TestRail after a CI run?

The Skill automatically posts pass/fail statuses to TestRail by reading Playwright JSON output, mapping test titles to TC IDs via regex, and creating a test run through an MCP connection.

Can I sync JUnit XML results to Qase or Zephyr Scale from my CI workflow?

Yes, the Skill supports syncing JUnit XML output to Qase or Zephyr Scale by parsing test-results XML files, mapping matched test cases, and posting per-test execution results to the configured TMS.

What happens to E2E tests without a mapped TC ID when publishing to a TMS?

Tests lacking a TC ID are grouped into an "Untracked Tests" run within the TMS, isolating unmapped results while still recording their pass/fail execution outcomes.

How do I configure which test management system receives my CI test results?

You configure the target TMS provider in the sparq.config.json file, allowing the Skill to route CI test results and generate run URLs for TestRail, Qase, or Zephyr Scale.

What happens if MCP is unavailable when publishing E2E test results to a TMS?

When MCP is unavailable, the Skill falls back to generating a local CSV file containing per-test results, providing a CSV path as feedback for manual TMS import.