qa-playwright-maintain-conventions

Enforce Playwright project conventions for test files and specifications.

12|6|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/whitebeardit/.cursor --skill qa-playwright-maintain-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-playwright-maintain-conventions
Source: https://github.com/whitebeardit/.cursor/tree/main/skills/qa/skill-qa-playwright-maintain-conventions
Command: npx skills add https://github.com/whitebeardit/.cursor --skill qa-playwright-maintain-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that your Playwright tests adhere to established project conventions, leading to more maintainable, readable, and robust test suites.

Core Features & Use Cases

  • Consistent Imports: Guarantees tests import from the correct fixture path, preventing direct @playwright/test imports.
  • Data Management: Encourages the use of test-data for inputs and lib/data-factory.ts for dynamic data, reducing hardcoding.
  • Directory Structure Adherence: Reinforces the standard placement of specs and test data.
  • Use Case: When adding a new API test, this skill will guide you to place the test file in tests/api/<fluxo>/ and any associated input data in test-data/api/<fluxo>/, ensuring project consistency.

Quick Start

Use the qa-playwright-maintain-conventions skill to ensure new tests follow project standards.

Frequently Asked Questions about qa-playwright-maintain-conventions

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

FAQPage Schema
How do I enforce Playwright test conventions for consistent imports and directory structure?

Playwright test conventions are enforced by importing from fixtures instead of @playwright/test, placing specs in tests/api/<fluxo>/, and storing inputs in test-data/api/<fluxo>/ to maintain project consistency and readability.

What is the best way to manage test data in Playwright without hardcoding values?

Playwright test data management is handled by using test-data inputs and lib/data-factory.ts for dynamic data generation, reducing hardcoded values and ensuring maintainable, robust test suites across your project.

How do I structure Playwright API test files to align with project standards?

Playwright API test files should be structured by placing specifications in tests/api/<fluxo>/ directories and associated input data in test-data/api/<fluxo>/, ensuring your test suite adheres to established project directory conventions.

Why should I import from fixtures instead of @playwright/test in my Playwright tests?

Importing from fixtures instead of @playwright/test prevents direct framework imports, enforces consistent project conventions, and ensures your Playwright test suite remains maintainable, readable, and aligned with established standards.

Does this Playwright convention enforcement apply when refactoring existing test specifications?

Playwright convention enforcement applies to editing tests, refactoring, and aligning code with project standards, guiding you to use correct fixture imports, test-data for inputs, and proper directory structure throughout the process.