testing-strategies
Implement robust software testing strategies, including unit, integration, and E2E tests, mocking frameworks, TDD patterns, and best practices for high-quality, reliable code across any stack.
Discover reusable agent skills, browse implementation details, and find the right skill for your workflow.
93 skills found
Implement robust software testing strategies, including unit, integration, and E2E tests, mocking frameworks, TDD patterns, and best practices for high-quality, reliable code across any stack.
Dedicated E2E testing agent for Playwright and Docker-based web applications, supporting automated test execution, report generation, and test creation.
A rigorous TDD workflow agent that enforces test-first development, ensuring 80%+ code coverage across unit, integration, and E2E tests for features, bug fixes, and refactoring.
Guides writing, debugging, and maintaining Bun bundler tests using itBundled and expectBundled to verify transpilation, minification, and code transformation.
Evidence-based debugging for Python, Node.js, and Java applications using runtime execution traces and diagnostic MCP tools.
Guidelines for testing HashQL code using compiletest (UI tests), unit tests, and insta snapshots. Includes commands for --bless, annotation syntax, and strategies for compiler components.
Systematic triage and reproduction workflow for investigating flaky CI test failures in Payload CMS repositories.
Run OpenResponses API compliance tests to validate schema adherence, streaming responses, and endpoint reliability for LobeHub integrations.
Accelerate software delivery by shifting testing to the earliest development phases, using AI-driven requirements validation, TDD, and automated CI pipelines to reduce defect costs.
Validate test suite effectiveness and uncover weak assertions by introducing code mutations and measuring kill rates. Essential for proving tests genuinely catch bugs rather than just satisfying coverage metrics.
Techniques for writing effective fuzzing harnesses across languages. Use when creating new fuzz targets or improving existing harness code.
Mandatory execution-based validation for all software implementation tasks. Ensures code works through empirical verification before confirmation.