qa-playwright-add-test-data

Estrellas12

Forks6

Actualizado31 de enero de 2026 a las 23:09

Add or extend test data for a QA Playwright flow: create or edit inputs.json and optional builder.ts in test-data, use lib/data-factory for generated data. Use when the user asks to add inputs, test data, or a builder for a flow.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

whitebeardit

whitebeardit/.cursor

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name: qa-playwright-add-test-data description: Add or extend test data for a QA Playwright flow: create or edit inputs.json and optional builder.ts in test-data, use lib/data-factory for generated data. Use when the user asks to add inputs, test data, or a builder for a flow.

Add test data (inputs and builders)

When adding or extending test data for a flow, follow this structure.

Where

API flow: test-data/api/<fluxo>/
UI flow: test-data/ui/<fluxo>/

Static inputs (inputs.json)

Create or edit inputs.json (or inputs.ts) with entries per scenario (e.g. getPost, createPost; or formUrl, sobreVoce).
In the spec, import: import inputs from '../../../test-data/<api|ui>/<fluxo>/inputs.json'; and use (e.g. inputs.getPost, inputs.sobreVoce).

Example: test-data/api/hello/inputs.json, test-data/ui/whitebeard/inputs.json.

Generated data (builder.ts, optional)

When you need to vary data (e.g. unique email per run), add builder.ts in the same flow folder.
Export a function that builds a default object and accepts overrides; use lib/data-factory.ts (randomEmail, randomString, randomNumber) inside the builder.
In the spec, import the builder and call it (e.g. createFormInput({ email: randomEmail() })).

Example: test-data/ui/whitebeard/builder.ts.

Checklist

Folder exists under test-data/api/<fluxo>/ or test-data/ui/<fluxo>/
inputs.json (or inputs.ts) defines static cases; builder.ts only if varying data is needed
Spec imports from ../../../test-data/... (three levels up from tests/<api|ui>/<fluxo>/)

Full reference

docs/04-test-data.md — inputs and builders
docs/05-lib.md — lib/data-factory (randomString, randomEmail, randomNumber)

Más de este repositorio

mismo repositorio

planning

whitebeardit/.cursor

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.

2026-03-0212

skill-frontend-instrumentation-otel

whitebeardit/.cursor

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.

2026-03-0112

qa-code-review

whitebeardit/.cursor

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.

2026-02-0412

correlation-id-tracking

whitebeardit/.cursor

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.

2026-01-3112

opentelemetry-instrumentation

whitebeardit/.cursor

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.

2026-01-3112

correlation-id-tracking

whitebeardit/.cursor

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.

2026-01-3112

name: qa-playwright-add-test-data description: Add or extend test data for a QA Playwright flow: create or edit inputs.json and optional builder.ts in test-data, use lib/data-factory for generated data. Use when the user asks to add inputs, test data, or a builder for a flow.

Add test data (inputs and builders)

When adding or extending test data for a flow, follow this structure.

Where

API flow: test-data/api/<fluxo>/
UI flow: test-data/ui/<fluxo>/

Static inputs (inputs.json)

Create or edit inputs.json (or inputs.ts) with entries per scenario (e.g. getPost, createPost; or formUrl, sobreVoce).
In the spec, import: import inputs from '../../../test-data/<api|ui>/<fluxo>/inputs.json'; and use (e.g. inputs.getPost, inputs.sobreVoce).

Example: test-data/api/hello/inputs.json, test-data/ui/whitebeard/inputs.json.

Generated data (builder.ts, optional)

When you need to vary data (e.g. unique email per run), add builder.ts in the same flow folder.
Export a function that builds a default object and accepts overrides; use lib/data-factory.ts (randomEmail, randomString, randomNumber) inside the builder.
In the spec, import the builder and call it (e.g. createFormInput({ email: randomEmail() })).

Example: test-data/ui/whitebeard/builder.ts.

Checklist

Folder exists under test-data/api/<fluxo>/ or test-data/ui/<fluxo>/
inputs.json (or inputs.ts) defines static cases; builder.ts only if varying data is needed
Spec imports from ../../../test-data/... (three levels up from tests/<api|ui>/<fluxo>/)

Full reference

docs/04-test-data.md — inputs and builders
docs/05-lib.md — lib/data-factory (randomString, randomEmail, randomNumber)