puppeteer-efficient-ui-verification
Fast, repeatable UI verification using Puppeteer without paying browser startup per test. Use scenario suites + deterministic fixtures before jumping to full Jest E2E.
Discover testing security testing skills, compare source repositories and read the instructions for each workflow.
Fast, repeatable UI verification using Puppeteer without paying browser startup per test. Use scenario suites + deterministic fixtures before jumping to full Jest E2E.
Autonomous UI inspection using a dual channel: (1) visual screenshots via Playwright MCP tools, (2) numeric layout metrics via Puppeteer scripts. Includes server --check standardization so agents can start/stop...
Testing patterns for Next.js App Router with Supabase. Use when adding tests, verifying fixes, or preventing regressions. Keywords: test, testing, jest, vitest, unit test, integration test, mock, Supabase mock,...
Guide for writing comprehensive tests and achieving >= 95% coverage. Use this when asked to write tests, fix test coverage, or debug failing tests.
Run TypeScript UI tests with Vitest and summarize results. Shows failures and coverage stats. Use when testing UI code in src/ui, validating TypeScript changes, or debugging test failures.
Run full project validation - Java tests, UI tests, lint, and typecheck. Comprehensive validation before commits or PRs. Use when you need to verify all code quality checks pass.
Run Java tests with Gradle and summarize results. Shows only failures and key statistics. Use when testing Java code, validating backend changes, or debugging test failures.
Generates comprehensive UI test scenarios with template-based quality check. Use when user requests UI test scenarios, manual test cases, or end-to-end test documentation.
Detects test flakiness patterns including timing issues, environmental dependencies, state pollution, and non-deterministic behaviors. Use as part of parallel test review execution.
Reviews UI test scenarios for RALPH chart and AC coverage. Detects uncovered constraints and acceptance criteria. Use as part of parallel UI test scenario review.
Reviews UI test scenarios for consolidation opportunities. Identifies scenarios that can be merged to reduce operation counts. Use as part of parallel UI test scenario review.
TDD workflow executor using Canon TDD (Red-Green-Refactor). Supports test list creation, failing test writing, minimal implementation, and refactoring with test verification. Use when implementing features with...
Reviews UI test scenarios for wording accuracy. Detects variables and dynamic values that cannot be verified from actual UI. Use as part of parallel UI test scenario review.
Reviews test code for assertion quality including precision levels, property coverage, and validation patterns. Use as part of parallel test review execution.
Reviews UI test scenarios for behavioral appropriateness. Detects design tests (colors, fonts, layout) that should not be in scenario tests. Use as part of parallel UI test scenario review.
Run E2E tests for React, Vue, and Svelte frameworks. Use when testing components, verifying changes, or before committing.
Maven integration testing with Failsafe plugin, IT naming conventions, and profile configuration
Domain-agnostic module testing task execution with two-tier skill loading
Cypress E2E testing standards including framework adaptations, test organization, and best practices
CUI test library standards for test data generation, value object contracts, and JUL log testing
JUnit 5 core testing patterns with AAA structure, test organization, and coverage standards
CUI MockWebServer standards for HTTP client testing with JUnit 5 integration
Jest unit testing standards covering configuration, test structure, testing patterns, and coverage requirements
Translates iOS workflow markdown files into Playwright E2E tests for CI using WebKit with mobile viewport. Use this when the user says "convert ios workflows to playwright", "translate ios workflows to CI", or...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.