tc-runner

Execute TC.csv test cases via browser agent and generate an Allure report.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jina-litmers/qa-agent-skills --skill tc-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tc-runner
Source: https://github.com/jina-litmers/qa-agent-skills/tree/main/.claude/skills/tc-runner
Command: npx skills add https://github.com/jina-litmers/qa-agent-skills --skill tc-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read TC.csv and execute tests with agent-browser, then generate an Allure HTML report. Includes network error logs, screenshots, and video recording.

Core Features & Use Cases

  • Start Collector and authenticate to load saved sessions before test execution.
  • Parse TC.csv and determine the list of test cases to run, filtering by status and scope.
  • Execute each TC with deterministic browser actions and capture logs, HAR files, and artifacts.
  • Generate Allure report after all TCs finish with a summary and failed-test details.

Quick Start

Start the collector, authenticate if needed, parse and run TC.csv, and view the Allure report when complete.

Frequently Asked Questions about tc-runner

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

FAQPage Schema
How do I automate end-to-end QA tests from CSV to Allure reports?

Automating end-to-end QA tests from CSV to Allure reports requires driving a browser agent to execute test cases defined in TC.csv, capturing HAR logs and screenshots, and generating an HTML summary. This workflow applies deterministic execution steps for verification.

Can I capture HAR files and video recordings during browser test automation?

Yes, browser test automation can capture HAR files and video recordings during execution. The workflow drives a browser agent through each test case to collect network error logs, screenshots, and video artifacts for comprehensive verification.

How do I filter test cases by status and scope when parsing TC.csv?

Filtering test cases by status and scope when parsing TC.csv occurs during the test execution setup phase. The workflow determines the list of test cases to run by applying these filters before driving the browser agent through the selected cases.

Do I need to authenticate and start a collector before executing test cases?

Yes, you must start a collector and authenticate to load saved sessions before executing test cases. This prerequisite ensures the browser agent has the necessary session context to run deterministic actions across the filtered TC.csv entries.

What's the best way to generate Allure reports with failed-test details for QA workflows?

Generating Allure reports with failed-test details for QA workflows is best handled by executing each test case with deterministic browser actions and capturing artifacts. After all cases finish, the workflow produces an Allure HTML report summarizing results and failures.

Why does browser-automation testing require network error logs and screenshots?

Browser-automation testing requires network error logs and screenshots to provide per-TC verification artifacts. Capturing HAR files and visual evidence alongside video recordings ensures comprehensive debugging context within the final Allure report.