autotest-runner

Execute Playwright E2E tests and store results in SQLite.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates running Playwright E2E tests and analyzing results to help teams quickly identify failures and monitor test health over time.

Core Features & Use Cases

  • Parallel execution of Playwright tests with optional project scope and tagging for faster feedback.
  • SQLite-backed result storage and trend analysis for long-term quality monitoring.
  • Per-test failure details extraction (name, status, duration, error message) for rapid triage.
  • Support for running all tests or subsets by module, tag, project, or last-failed.

Quick Start

Run the generated Playwright E2E tests and review the results stored in SQLite.

Frequently Asked Questions about autotest-runner

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

FAQPage Schema
How do I run Playwright E2E tests and store results in SQLite?▼

Run Playwright E2E tests and store results in SQLite by executing all tests or targeted subsets like module, tag, project, or last-failed, with the runner automatically extracting per-test details and saving structured trend data for analysis.

What is the best way to run a specific subset of Playwright tests?▼

Run a specific subset of Playwright tests by filtering your execution scope to target modules, tags, specific projects, or previously failed tests to isolate failures and achieve faster feedback.

Can I parse Playwright failure details like error messages and test duration?▼

Yes, you can parse Playwright failure details. The runner automatically extracts per-test information including the test name, status, duration, and specific error messages to enable rapid triage.

Does parallel execution work with Playwright project scoping and tagging?▼

Yes, parallel execution works with Playwright project scoping and tagging. It applies optional project scopes and tags during automated execution to accelerate testing feedback.

Why do I need SQLite for Playwright test trend analysis?▼

You need SQLite for Playwright test trend analysis because it provides backed storage to record per-test results over time, enabling long-term quality monitoring and historical trend data evaluation.