pytest-backend-patterns
Backend testing with pytest including fixtures, mocking, async tests, and database testing. Use for FastAPI/Python test implementation.
Discover testing security testing skills, compare source repositories and read the instructions for each workflow.
Backend testing with pytest including fixtures, mocking, async tests, and database testing. Use for FastAPI/Python test implementation.
Performance testing using Chrome DevTools, Lighthouse, and Core Web Vitals monitoring. Use for performance profiling or optimization validation.
Complete testing toolkit for web applications - backend pytest, E2E Playwright, performance profiling, and local automation.
Complete testing toolkit for web applications - backend pytest, E2E Playwright, performance profiling, and local automation.
Performance testing using Chrome DevTools, Lighthouse, and Core Web Vitals monitoring. Use for performance profiling or optimization validation.
End-to-end testing with Playwright including page objects, fixtures, visual regression, and CI integration. Use for E2E test implementation or test architecture.
End-to-end testing with Playwright including page objects, fixtures, visual regression, and CI integration. Use for E2E test implementation or test architecture.
Runs Claude in a retry loop until tests pass or task completes. Use for TDD loops, overnight builds, or any task needing repeated iteration until success. Triggers on: loop until done, keep trying, retry until...
Prevent common testing anti-patterns that undermine test effectiveness and code quality by ensuring tests verify real behavior rather than mock behavior, keeping production code free from test-only pollution, a...
Run tests and analyze failures with actionable fixes. Use when user wants to run tests or debug test failures.
Write focused tests for core user flows and critical paths with clear test names, behavior-focused assertions, mocked external dependencies, and fast execution, deferring edge case testing until explicitly requ...
Guide for writing FoundationDB simulation workloads in Rust. Use when designing chaos testing, simulation testing, deterministic testing, or workload implementations for FDB layers. Covers operation design, inv...
Generates a PHPUnit/Pest test file. Use when adding test coverage for Actions, Features, or Endpoints (e.g., "Create a test for RegisterStudentAction").
Test a Rust solution file against LeetCode's test cases (project)
Generate comprehensive test suites following the test pyramid: static analysis → unit → integration → E2E. LOAD THIS SKILL WHEN: User says "寫測試", "test", "測試", "TG", "coverage", "覆蓋率", "pytest", "unitte...
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automa...
Validate at every layer data passes through to make bugs impossible
AL test development patterns with telemetry verification. MANDATORY when: (1) planning test implementation, (2) creating new tests, (3) modifying existing tests. Invoke proactively at ALL three stages. PLANNING...
Frontend testing with browser automation, assertions, and visual regression. Use when testing web UIs, validating user flows, checking responsive design, form submissions, login flows, or detecting visual regre...
Demonstrates unsafe patterns for testing audits. Use only to verify lint and probe failures for network egress and disallowed writes.
Test Midnight smart contracts using simulators and unit tests. Use when setting up test environments, writing contract tests, or debugging circuit behavior. Triggers on testing, simulator, unit test, or test fr...
End-to-end testing with Playwright for web applications. Use when writing E2E tests, browser automation, visual regression testing, or debugging test failures. Triggers on Playwright, E2E, browser testing, or t...
Implement test-driven development (TDD) practices. Write tests first, then implementation.
Adds visual capabilities to the agent using Playwright MCP with Script Execution support.
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.