test-case-analysis

Execute TMS test cases end-to-end and emit Automation-Friendly Specs.

18|9|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/arozumenko/sdlc-skills --skill test-case-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-case-analysis
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/test-case-analysis
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill test-case-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates the gap between an authored TMS test case and what the live application actually does by executing the case end-to-end and producing an Automation-Friendly Spec (AFS) that downstream engineers can implement without re-exploring.

Core Features & Use Cases

  • End-to-end manual execution: Runs a single TMS test case against the live app, observing real behavior step by step.
  • Selector discovery and defect/blocked classification: Captures stable, accessible-friendly selectors and classifies outcomes (ready, already-covered, extend-existing, blocked, defect-found, un-automatable).
  • AFS emission for automation handoff: Outputs a spec in the required test-specs structure and includes evidence paths and routing details for defects.

Quick Start

Use the test-case-analysis skill to execute TMS case SCRUM-T101 and emit an Automation-Friendly Spec (AFS) with stable selectors and any defect evidence.

Frequently Asked Questions about test-case-analysis

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

FAQPage Schema
How do I turn manual test execution into an automation-friendly spec?

To turn manual test execution into an automation-friendly spec, execute a TMS test case end-to-end against the live application and capture observed behavior, stable selectors, and routing details into a structured spec file for downstream automation.

What is automation-friendly spec emission for pre-automation case exploration?

Automation-friendly spec emission outputs a structured specification containing stable selectors, evidence paths, and outcome classifications after running a TMS test case, enabling engineers to implement automation without re-exploring the live application.

How do I capture stable selectors during test case analysis?

Stable selectors are captured during step-by-step browser execution by favoring test IDs and ARIA roles from the live application, ensuring the resulting specification is accessible and resilient for downstream automation implementation.

Does test case analysis write Playwright automation code automatically?

No, test case analysis does not write automation code. It executes the TMS case against the live app, captures selectors, and emits an automation-friendly specification file, leaving the actual code implementation to downstream engineers.

How do I classify defects and blocked cases during TMS test execution?

During TMS test execution, observed behavior is classified into specific outcomes such as ready, already-covered, extend-existing, blocked, defect-found, or un-automatable, with defect evidence paths included in the emitted specification.

What is a case-gate preflight in test case analysis?

A case-gate preflight is a required validation step executed before step-by-step browser exploration, ensuring the TMS test case meets necessary conditions for end-to-end execution against the live application prior to selector discovery and spec emission.