qa-regression_skill

Overview

This skill automates QA regression testing by providing reusable Playwright test skills for common flows like login, dashboard checks, and user management. Tests are organized as composable specs and helpers so you can assemble full regression suites that run consistently in CI or locally. It includes config, helpers, and examples to get a repeatable test pipeline up quickly.

How this skill works

Each test is a small, focused Playwright spec that interacts with the app using stable data-testid selectors and shared helper functions for actions like login and user cleanup. Tests live under a tests/ directory and can be imported into a single regression.spec to run the full suite. Playwright config sets environment-driven baseURL, cross-browser projects, reporting, and retry/trace behavior for CI stability.

When to use it

• Automating nightly or PR regression runs in CI
• Validating critical user journeys (login, dashboard, user creation)
• Running fast local checks during development
• Measuring dashboard load time and widget availability
• Ensuring test data is created and cleaned up reliably

Best practices

• Use data-testid attributes for stable selectors instead of fragile CSS
• Clean up any test data you create (delete test users via API)
• Prefer waitForSelector and explicit assertions over hardcoded timeouts
• Run tests in parallel where safe; restrict workers in CI if needed
• Capture screenshots and traces on failure to speed debugging
• Keep credentials and endpoints in environment variables, not in source

Example use cases

• Login flow.verify successful login and error handling for invalid credentials
• Dashboard performance.check load time under a threshold and widget visibility
• User lifecycle.create a user, verify it appears in the list, then delete it
• Full regression.run all auth, dashboard, and user tests as a single suite
• CI integration.schedule daily runs and upload Playwright reports for review