Menu
Add a new Playwright test (API or UI) following project conventions: import from fixtures, use test-data when applicable, Arrange-Act-Assert. Use when the user asks to add a test, create a test, or add a test for a flow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Planning and orchestration patterns for turning messy context into an incremental, verifiable execution plan. Use when you need a step-by-step strategy before coding or delegating to subagents.
Instrumenta frontends Vite 3 + TypeScript com OpenTelemetry para Grafana, Tempo e Mimir (traces, Web Vitals, page views, cliques, erros). Use ao adicionar telemetria em novas páginas, configurar RUM ou revisar código de instrumentação existente.
Perform QA Playwright code review by applying the perspectives of maintain, add-fixture, and add-flow agents; produce a consolidated improvement summary focused on maintenance, quality, and standardization. Use when the user asks for a code review, review of specs/test-data, or improvement summary.
Manages correlation-id in .NET applications using AsyncLocal for async context isolation. Use when implementing correlation-id tracking, HTTP request/response correlation, logging integration, or when working with distributed tracing in .NET applications.
Instruments .NET applications with OpenTelemetry spans following best practices. Use when adding distributed tracing, instrumenting HTTP requests, SOAP calls, database operations, or when implementing observability with OpenTelemetry in .NET Framework 4.8 or .NET 8 applications.
Manages correlation-id in Node.js/TypeScript applications using AsyncLocalStorage for async context isolation. Use when implementing correlation-id tracking, HTTP request/response correlation, logging integration, or when working with distributed tracing in Node.js applications.
Based on SOC occupation classification
| name | qa-playwright-add-new-test |
| description | Add a new Playwright test (API or UI) following project conventions: import from fixtures, use test-data when applicable, Arrange-Act-Assert. Use when the user asks to add a test, create a test, or add a test for a flow. |
When adding a new test to the QA Playwright project, follow these conventions.
test and expect from the fixtures path (three levels up from the spec): import { test, expect } from '../../../fixtures';@playwright/test in any file under tests/.request in the test argument.test-data/api/<fluxo>/inputs.json when applicable; import: import inputs from '../../../test-data/api/<fluxo>/inputs.json';Example: See tests/api/hello/hello-api.spec.ts.
page (and optionally context).test-data/ui/<fluxo>/inputs.json or a builder when applicable; use lib/data-factory.ts (randomEmail, randomString) for varying data.getByRole, getByText, getByLabel; use web-first assertions: await expect(locator).toBeVisible().Example: See tests/ui/whitebeard/whitebeard-forms.spec.ts.
tests/api/<fluxo>/ or tests/ui/<fluxo>/ with suffix .spec.ts../../../fixtures