browser-control
Full browser control for authenticated web interactions using Playwright scripts
Full browser control for authenticated web interactions using Playwright scripts
Senior Frontend QA Engineer with 10+ years JavaScript/TypeScript testing experience. Use when writing unit tests for React components, creating integration tests with React Testing Library, testing custom hooks, mocking APIs, or following TDD for frontend.
Achieves 100% test coverage with minimal redundancy through progressive test writing. Writes tests one-at-a-time with immediate coverage verification, removes redundant tests while maintaining coverage, fixes standards violations, restructures fixtures. Use when creating test suites for existing code, or optimizing test efficiency
Test Swift applications - XCTest, Swift Testing, UI tests, mocking, TDD, CI/CD
Test infrastructure patterns - PGlite for in-memory PostgreSQL, Redis/S3 mocks, TestSetup factory, Bun test. Use when writing tests or adding test infrastructure.
Python testing best practices with pytest. Covers unit, integration, async tests, mocking, fixtures. Triggers: "напиши тесты", "write tests", "add tests", "test coverage", "pytest"
Web application testing principles. E2E, Playwright, deep audit strategies.
Test-Driven Development workflow enforcement with RED-GREEN-REFACTOR cycle. Use when implementing features test-first or improving test coverage.
Senior QA Automation Engineer with 10+ years E2E testing experience. Use when writing end-to-end tests for web apps with Playwright, mobile apps with Detox, testing critical user flows, cross-browser testing, or visual regression testing.
PHPUnit testing conventions and best practices for any PHP project
Expert testing patterns for GhostSpeak monorepo (January 2026). Use when (1) Writing unit tests, (2) Building integration tests, (3) Creating E2E tests with Playwright, (4) Testing Solana programs, (5) Testing React components, (6) Testing Convex functions, or any testing strategy questions.
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling
Creates comprehensive test suites for Odoo 16.0 modules following Siafa project standards. This skill should be used when creating tests for Odoo modules, such as "Create tests for this module" or "Generate test cases for stock_location_usage_restriction" or "Add unit tests to validate this functionality". The skill provides test templates, patterns, and best practices specific to Odoo 16.0 Enterprise with knowledge of database constraints and common pitfalls in the Siafa codebase.
Validate test effectiveness with mutation testing using Stryker (TypeScript/JavaScript) and mutmut (Python). Find weak tests that pass despite code mutations. Use when user mentions mutation testing, Stryker, mutmut, test effectiveness, finding weak tests, or improving test quality through mutation analysis.
How to write idiomatic assertions with the Bupkis assertion library for TypeScript and JavaScript
Before submitting code or creating a Pull Request, when about to claim that work is complete, fixed, or passed, you must run verification commands and confirm the output results before making any success claims; evidence must appear before any assertions
This is a test fixture with intentional violations for regression testing. It contains <angle brackets> which trigger B5, and has an unexpected frontmatter property which triggers W2.
Comprehensive testing strategies for Rust including property-based testing with proptest, fuzz testing with cargo-fuzz, benchmark testing with Criterion, contract testing for traits, and Miri for undefined behavior detection. Use when writing tests, ensuring code correctness, detecting edge cases, or measuring performance.
Use when asked to evaluate PR test coverage or explicitly asked to run the pr-test-analyzer subagent.
Write browser-based tests using Playwright or similar tools for E2E testing, visual regression, and cross-browser compatibility. Use when adding automated UI tests or validating user flows.
Before submitting code or creating a Pull Request, when about to claim that work is complete, fixed, or passed, you must run verification commands and confirm the output results before making any success claims; evidence must appear before any assertions