autotest-generator

Generates Playwright+TypeScript autotest artifacts from XLSX test documentation and vault data.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/midas44/ttt-expert-v2 --skill autotest-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autotest-generator
Source: https://github.com/midas44/ttt-expert-v2/tree/main/.claude/skills/autotest-generator
Command: npx skills add https://github.com/midas44/ttt-expert-v2 --skill autotest-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts XLSX-based test documentation into complete Playwright + TypeScript autotest artifacts, eliminating manual boilerplate and aligning tests with structured specifications.

Core Features & Use Cases

  • XLSX-to-code generation: transforms module-level test cases into data classes, page objects, fixtures, and spec files following the 5-layer architecture.
  • Vault-enriched automation: augments generated code with selectors, validation rules, and edge-case knowledge from the expert vault to ensure realistic tests across TTT, CS, and PMT.
  • Data-mode agnostic: supports static, dynamic, and saved data modes for reproducible or data-fresh executions.

Quick Start

Provide the XLSX test documentation and run the skill to generate the full autotest artifacts (data classes, page objects, fixtures, and specs).

Frequently Asked Questions about autotest-generator

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

FAQPage Schema
How do I convert XLSX test documentation into Playwright autotests?

To convert XLSX test documentation into Playwright autotests, provide the spreadsheet file to the generator to automatically parse and create data classes, page objects, fixtures, and TypeScript spec files.

What is the 5-layer architecture used for generating TypeScript automation tests?

The 5-layer architecture organizes generated TypeScript automation tests into distinct modules: data classes, page objects, fixtures, and specs, ensuring structured and maintainable test artifacts from your XLSX documentation.

How do I handle data-driven testing in Playwright with static and dynamic data modes?

Handling data-driven testing in Playwright with static and dynamic data modes is supported by generating data class variants that allow reproducible or data-fresh executions based on your XLSX specifications.

Can I use expert vault notes to enrich Playwright test generation with selectors and validation rules?

Yes, you can use expert vault notes to enrich Playwright test generation. The system augments generated code with selectors, validation rules, and edge-case knowledge from the vault to ensure realistic tests.

Does the Playwright autotest generator support module-specific test cases for TTT, CS, and PMT?

Yes, the Playwright autotest generator supports module-specific test cases for TTT, CS, and PMT modules, transforming structured XLSX documentation into complete end-to-end automation artifacts.

What is the best way to eliminate manual boilerplate when creating Playwright page objects and fixtures?

The best way to eliminate manual boilerplate when creating Playwright page objects and fixtures is using an XLSX-to-code generator that automatically parses test cases and outputs the complete 5-layer architecture files.