test-by-playwright

Generate and execute Playwright tests from PR descriptions.

2|Updated Nov 27, 2017
One-click install
npx skills add https://github.com/tomoasleep/dotfiles --skill test-by-playwright
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-by-playwright
Source: https://github.com/tomoasleep/dotfiles/tree/main/config/.claude/skills/test-by-playwright
Command: npx skills add https://github.com/tomoasleep/dotfiles --skill test-by-playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation and execution of Playwright tests from provided content or GitHub pull requests, reducing manual test creation time and ensuring consistent QA workflows.

Core Features & Use Cases

  • Test Code Generation: Create MCP-compatible Playwright test scripts from described scenarios.
  • Test Execution: Run generated tests locally or in CI to validate UI behavior.
  • Use Case: Imagine validating a new UI flow described in a PR; this skill will generate the necessary Playwright tests and run them to verify expectations.

Quick Start

Use the test-by-playwright skill to generate tests from a PR description or feature spec, then execute them in your Playwright environment. Ensure Playwright is installed and configured for your project.

Frequently Asked Questions about test-by-playwright

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

FAQPage Schema
How do I generate Playwright tests from a pull request description?

You can generate Playwright tests from a pull request by providing the PR description or feature spec to the skill. It creates MCP-compatible test scripts from the described scenarios, targeting QA workflows during PR reviews to automate test creation.

Can I run generated Playwright tests automatically during PR validation?

Yes, you can run generated Playwright tests locally or in CI to validate UI behavior during PR validation. The skill automates test execution to verify expectations for new UI flows described in your pull requests.

Do I need a specific project layout to execute Playwright tests generated from feature specs?

Yes, you need a project layout that places tests under the .playwright-tests directory. The skill requires Playwright tooling to be installed and configured, using deterministic folder naming for test cases to execute properly.

What is QA automation with Playwright and MCP-compatible test scripts?

QA automation with Playwright and MCP-compatible scripts involves generating test code from described scenarios and running them to validate web UI behavior. This reduces manual test creation time and ensures consistent QA workflows for web applications.

Does this approach work for validating new UI flows in web applications?

Yes, this approach works for validating new UI flows in web applications. It generates the necessary Playwright tests from feature specifications or PR descriptions and runs them to verify that the UI behavior matches expectations.

Why are my generated Playwright tests not working in my project?

Generated Playwright tests may not work if your project lacks the required .playwright-tests directory structure or if Playwright tooling is not installed and configured. The skill requires MCP-compatible test scripts and deterministic folder naming for test cases.