qa-playwright-add-new-test

Create Playwright API or UI tests with project conventions and Arrange-Act-Assert structure.

12|6|Updated Jan 26, 2026

Search Tags:#testing #e2e #playwright #ui testing #api testing #qa automation

Ready to run

npx skills add https://github.com/whitebeardit/.cursor --skill qa-playwright-add-new-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-playwright-add-new-test
Source: https://github.com/whitebeardit/.cursor/tree/main/skills/qa/skill-qa-playwright-add-new-test
Command: npx skills add https://github.com/whitebeardit/.cursor --skill qa-playwright-add-new-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of adding new Playwright tests (API or UI) by enforcing project-specific conventions and best practices, ensuring consistency and maintainability.

Core Features & Use Cases

Convention Enforcement: Automatically applies project standards for imports, test structure, and locator strategies.
Data Handling Guidance: Provides direction on using test data fixtures or data factories for dynamic inputs.
Use Case: When a developer needs to add a new API endpoint test or a new user flow simulation for the UI, this Skill guides them to create a well-structured and maintainable test file.

Quick Start

Use the qa-playwright-add-new-test skill to add a new UI test for the login flow.

Frequently Asked Questions about qa-playwright-add-new-test

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

FAQPage Schema

How do I add a new Playwright test for an API endpoint?▼

To add a new Playwright API test, structure your test file using the Arrange-Act-Assert pattern and load inputs from data fixtures or factories to ensure maintainability and follow project conventions.

What is the best way to structure Playwright UI tests for user flows?▼

The best way to structure Playwright UI tests is by enforcing the Arrange-Act-Assert structure, using correct import paths, and sourcing dynamic data from fixtures to maintain robust and conventional test suites.

How do you handle test data in Playwright automation scripts?▼

Handle Playwright test data by utilizing data fixtures or data factories for dynamic inputs rather than hardcoding values, ensuring your API and UI testing scenarios remain maintainable.

Can I use this approach for both API and UI testing in Playwright?▼

Yes, you can use this Playwright testing approach for both API endpoint interactions and UI user flow simulations, applying consistent import paths and data handling conventions across all test files.

Why follow the Arrange-Act-Assert pattern in e2e testing?▼

Follow the Arrange-Act-Assert pattern in e2e testing to separate test setup, execution, and verification, which enforces project conventions and results in a highly maintainable Playwright test suite.