test-automation-workflow

Convert manual TMS test cases into executable end-to-end automation workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It reduces the slow, error-prone work of converting manual TMS test cases into reliable end-to-end automation, while keeping the work honest and consistent across teams.

Core Features & Use Cases

  • End-to-end automation pipeline: guides analyst → implementer → reviewer through discovery, execution, spec writing, implementation, and review.
  • AFS-first execution contract: produces an Automation-Friendly Spec (AFS) that implementers can execute without guessing, including selector evidence and known-defect handling rules.
  • Pluggable TMS integration: supports Zephyr Scale, TestRail, Xray, Azure Test Plans, or markdown-based cases via adapters.
  • No defect masking guardrails: enforces strict rules (e.g., no test.fail()/skip-style hiding of real product defects); supports expect.soft with ticket references for isolated defects.

Quick Start

Tell the agent to automate a single manual case end-to-end by fetching the case from your configured TMS, producing the automation-ready AFS, implementing the automation inside your existing framework, and finishing with a full run report.

Frequently Asked Questions about test-automation-workflow

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

FAQPage Schema
How do I convert manual TMS test cases into executable end-to-end automation?▼

Converting manual TMS test cases into executable end-to-end automation requires an analyst-to-implementer-to-reviewer workflow that produces an Automation-Friendly Spec (AFS) with selector evidence, implemented inside your existing framework without masking defects.

What is an Automation-Friendly Spec (AFS) and how does it guide Playwright test implementation?▼

An Automation-Friendly Spec (AFS) is a quality gate contract that implementers execute without guessing, providing selector evidence and known-defect handling rules for Playwright end-to-end tests. It ensures tests are built consistently and honestly.

Does this test automation workflow support integration with TestRail, Zephyr Scale, and Azure Test Plans?▼

Yes, test automation workflow integration supports TestRail, Zephyr Scale, Azure Test Plans, Xray, and markdown-based cases via a pluggable TMS adapter interface. Adapters fetch manual cases and feed them into the automation pipeline.

What is the best way to handle known product defects during end-to-end test automation?▼

The best way to handle known product defects during end-to-end test automation is enforcing strict no-defect-masking behavior, using expect.soft with ticket references for isolated defects rather than test.fail() or skip-style hiding of real product issues.

Can I automate a single regression test case from TMS into a green framework test?▼

Yes, you can automate a single regression test case by fetching it from your configured TMS, producing the automation-ready AFS, implementing the automation inside your existing framework, and finishing with a full structured run report.

Why are structured run reports required after executing automated end-to-end tests?▼

Structured run reports are required after executing automated end-to-end tests to maintain honest reporting standards and ensure no real product defects are hidden. They provide visibility into test execution outcomes and defect status.