tc-generator

Generate CSV QA test case documents from UI exploration workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines QA documentation by translating UI exploration into structured test-case CSVs, saving manual effort and ensuring consistent test coverage.

Core Features & Use Cases

  • Generates TC.csv from a UI map based on the top navigation and user flows
  • Documents happy-path, edge cases, and auth-branch scenarios for both logged-in and logged-out states
  • Produces a ready-to-use, human-readable QA doc that managers can execute manually

Quick Start

Ask the agent to start a UI exploration and generate a TC.csv file for the target application.

Frequently Asked Questions about tc-generator

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

FAQPage Schema
How do I generate QA test cases from UI exploration?

You can generate QA test cases by automating a UI exploration workflow that captures observable UI elements and writes steps with expected results into a structured TC.csv file. This translates top-navigation-based exploration into ready-to-use manual testing documentation.

What is a TC.csv file and when do I need it for manual testing?

A TC.csv file is a structured QA test case document containing entries for each page and authentication state. You need it when translating UI exploration into consistent, human-readable test coverage that QA managers can execute manually.

Does the test case generator cover both logged-in and logged-out auth states?

Yes, the test case generator documents happy-path, edge cases, and auth-branch scenarios for both logged-in and logged-out states. It captures entries for each page based on the top navigation and respective user flows.

Do I need agent-browser to perform UI exploration for test case documentation?

Yes, you need agent-browser to perform the UI exploration required to generate the test case CSV. The skill relies on it to navigate the target application and capture observable UI elements across different pages.

Can I document edge cases and happy-path scenarios in the same CSV export?

Yes, the generated TC.csv includes documentation for happy-path, edge cases, and auth-branch scenarios together. It outputs a single human-readable QA doc that managers can execute manually across all captured UI states.