dbt-tools-web-e2e-fix

Automates running and debugging Playwright E2E tests for the @dbt-tools/web project.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill dbt-tools-web-e2e-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbt-tools-web-e2e-fix
Source: https://github.com/yu-iskw/dbt-artifacts-parser-ts/tree/main/.claude/skills/dbt-tools-web-e2e-fix
Command: npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill dbt-tools-web-e2e-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates running and debugging Playwright E2E tests for the @dbt-tools/web project.

Core Features & Use Cases

  • Run Playwright E2E tests from the repository root to validate web app changes.
  • Fix flaky, failing, or timed-out E2E tests with minimal, targeted changes and re-run until green.
  • Debug failing tests with traces, screenshots, and selective replays, preserving test integrity.

Quick Start

From the repository root, run pnpm test:e2e to start the E2E fixer loop and iteratively fix failures.

Frequently Asked Questions about dbt-tools-web-e2e-fix

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

FAQPage Schema
How do I fix flaky Playwright E2E tests automatically?

To fix flaky Playwright E2E tests automatically, run an iterative fixer loop from the repository root using pnpm. This loop debugs failures with traces and screenshots, applies minimal targeted fixes, and re-runs tests until they pass, limited to five iterations.

What do I need to run Playwright E2E tests for a web project?

To run Playwright E2E tests, you need pnpm and Node installed as specified in the repository, along with Playwright included via devDependencies. You must execute the test commands from the repository root to ensure the environment matches the project configuration.

Why does my Playwright E2E test time out and how can I debug it?

Playwright E2E tests time out due to application delays or selector issues. You can debug timed-out tests by using traces, screenshots, and selective replays to identify the bottleneck, then applying minimal changes and re-running until the tests pass.

What is the best way to debug failing E2E tests without breaking test integrity?

The best way to debug failing E2E tests while preserving test integrity is to use Playwright's built-in traces, screenshots, and selective replays. This approach guides minimal, targeted fixes rather than altering the core test logic to force a pass.

What are the limitations of automated E2E test fixing loops?

The main limitation of this automated E2E test fixing loop is the strict cap of five iterations. If the Playwright tests remain flaky, failing, or timed-out after five targeted fix and re-run cycles, the automated loop terminates without achieving a green state.