Loading...
Loading...
Found 117 Skills
Run tests from skill examples and generate a report (project)
Provides comprehensive guidance for Cypress end-to-end testing including commands, assertions, component testing, CI/CD integration, and best practices. Use when the user asks about Cypress, needs to write E2E tests, component tests, or configure Cypress for testing.
Testing patterns and best practices for unit, integration, and E2E testing.
Cypress end-to-end testing for web apps. Use for E2E testing.
TYPO3 extension testing (unit, functional, E2E, architecture, mutation). Use when setting up test infrastructure, writing tests, or configuring CI/CD.
Builds end-to-end browser tests for critical user flows using Playwright or Cypress. Includes selector strategies, test data management, page objects, and visual regression testing. Use for "E2E testing", "browser tests", "Playwright", or "Cypress tests".
Complete browser automation with Playwright. **ALWAYS use when user needs browser testing, E2E testing, screenshots, form testing, or responsive design validation.** Auto-detects dev servers, saves test scripts to working directory. Examples - "test this page", "take screenshots of responsive design", "test login flow", "check for broken links", "validate form submission".
Generic E2E patterns with Playwright—state setup, seeds, test IDs, auth, environment, and Sail integration
AI-powered E2E testing for any app. Test 8 platforms with natural language — no test code needed.
QA skill orchestrator for test strategy, Playwright/E2E, mobile testing, API contracts, LLM agent testing, debugging, observability, resilience, refactoring, and docs coverage; routes to 12 specialized QA skills.
Use the Playwright MCP server (@playwright/mcp) for browser-driven verification, screenshots, console logs, and UI flow validation; use when debugging or validating Angular UI behavior beyond unit tests.
Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.