autotest-fixer

Diagnose and fix failing Playwright E2E tests by analyzing errors and updating selectors or logic.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and fixes failing Playwright E2E tests by analyzing errors, inspecting the running application, and applying robust fixes to selectors and test logic.

Core Features & Use Cases

  • Error analysis and classification for selectors, timeouts, data, logic, auth, and flaky failures.
  • Live selector discovery using the playwright-vpn MCP to obtain robust selectors against UI changes.
  • End-to-end fix workflow including patching selectors, adjusting waits, ensuring proper test data, and re-verification.

Quick Start

Submit the failing Playwright E2E test output and let Autotest-Fixer diagnose the issue, patch selectors or test logic, and verify the fix.

Frequently Asked Questions about autotest-fixer

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

FAQPage Schema
How do I fix failing Playwright E2E tests with broken selectors?

To fix failing Playwright E2E tests, analyze the error output and update broken selectors. This Skill diagnoses selector failures, discovers robust live selectors via the playwright-vpn MCP, patches test logic, and verifies the fix by re-running the tests.

Why do my Playwright E2E tests time out and how can I resolve flaky failures?

Playwright E2E tests time out and become flaky due to dynamic UI elements or insufficient waits. This Skill classifies timeout and flaky failures, adjusts wait handling, updates test logic, and re-runs the scenarios to ensure stability.

What's the best way to diagnose Playwright E2E test failures automatically?

The best way to diagnose Playwright E2E test failures is to analyze error outputs and inspect the running application. This Skill classifies root causes across selectors, timeouts, data setup, and auth, then applies fixes and documents them in the knowledge base.

Does this Skill require the playwright-vpn MCP to discover live selectors?

Yes, this Skill requires the playwright-vpn MCP for live selector discovery. It uses the MCP to inspect the running application and obtain robust selectors that withstand UI changes, ensuring accurate test flow adjustments and re-verification.

Can I patch test data setup and logic for Playwright tests using this approach?

Yes, you can patch test data setup and logic for Playwright tests. This Skill diagnoses data and logic failures, ensures proper test data configuration, adjusts test flows, and re-runs the tests to verify the applied patches.

When should I not use an automated approach for Playwright test repair?

You should not use automated Playwright test repair when the application is not running or accessible for live inspection. The diagnostic workflow requires a live environment to discover selectors via the playwright-vpn MCP and verify fixes by re-running tests.