property-based-testing
Automated guidance for implementing property-based testing (PBT) in software and smart contracts to improve test coverage and edge case detection.
Discover reusable agent skills, browse implementation details, and find the right skill for your workflow.
105 skills found
Automated guidance for implementing property-based testing (PBT) in software and smart contracts to improve test coverage and edge case detection.
Intelligent unit and integration test generation powered by Minion framework, featuring business logic validation, boundary testing, and Vitest integration.
Standardizes Vitest unit and integration testing workflows for TypeScript, enforcing 70% coverage, proper mocking, and CI/CD-ready verification patterns.
Run, debug, and manage DBHub tests including unit, integration with Testcontainers, and database-specific suites. Perfect for verifying code changes and troubleshooting database connector issues.
Implement professional TDD workflows with strict 80% coverage, automated testing strategies, and AAA pattern enforcement for robust, high-quality code.
Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.
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.
Implement consumer-driven contract testing for microservices using Pact, schema validation, and API versioning to prevent breaking changes and ensure distributed team coordination.
Expert systematic test design using BVA, equivalence partitioning, decision tables, and combinatorial testing to maximize coverage and minimize redundancy.
Guidance for writing, reviewing, and refactoring software tests, focusing on integration strategies, condition-based waiting, and professional mocking patterns.
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.
Enforces disciplined Test-Driven Development (TDD) by requiring a failing test before implementation, ensuring code reliability and preventing premature over-engineering.