Loading...
Loading...
Found 230 Skills
Use when symfony e2e panther playwright
Execute complete user flow testing with Playwright MCP, testing end-to-end journeys through the application
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.
WebDriver browser automation protocol. Use for cross-browser testing.
Use when jUnit extensions including custom extensions, rules, and conditional test execution.
Run test → fix → refactor loop with TDD workflow
core usage of pw (playwright cli) on protocol-first surface. use when user requests browser tasks.
Generate runnable Vitest and Playwright test files from BDD test cases and scaffold code. Use when generating test implementations.
Full closed-loop QA combining issue discovery and software testing. Scout -> Strategist -> Generator -> Executor -> Analyst with multi-perspective scanning, progressive test layers, GC loops, and quality scoring. Supports discovery, testing, and full QA modes.
Write a playwright test, make sure it runs, and is not flaky.
Invoke this skill when a user shares test code and questions whether it actually works as intended — not to run or fix the test, but to evaluate whether the test has real value. Triggers on: "is this test any good?", "would this catch a real bug?", "this test always passes — is that normal?", "review these tests before I commit", or "does this test verify anything meaningful?". Also triggers when someone suspects a test is useless, wants a pre-commit quality gate, or is unsure if an auto-generated test is worth keeping. The core question this skill answers: "Would this test fail if the feature broke?" If not, the test gets rejected. Do NOT use for generating new tests, fixing failing tests, or exploring application features.
Execute YAML test plan, stop on first failure, output rich debug prompt