Loading...
Loading...
Found 12 Skills
Expert-level JavaScript testing skill focused on writing high-quality tests that find bugs, serve as documentation, and prevent regressions. Advocates for property-based testing with fast-check and protects against indeterministic code in tests. Does not cover black-box e2e testing.
Run project tests using the X07 test harness (x07 test), producing a machine-readable JSON report.
Write and run Rust tests using cargo test with unit tests, integration tests, doc tests, and property-based testing. Use when writing Rust tests or setting up test infrastructure.
Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.
Advanced testing - Testcontainers, contract testing, mutation testing, property-based
Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Use when testing API boundaries, verifying contracts, or validating cross-service integration.
Comprehensive testing standards including unit, integration, security, and property-based testing with TDD methodology
F# testing patterns with xUnit, FsUnit, Unquote, FsCheck property-based testing, integration tests, and test organization best practices.
Use when writing, reviewing, or refactoring tests in any language. Test behavior at real boundaries, delete change-detector tests, choose doubles in order (real, fake, stub, mock), pick the cheapest layer that catches the risk (SMURF), author tests DAMP, keep them deterministic, prove they can fail, with dialects for Rust, TypeScript, Go, and Python.
Testing patterns and standards for this codebase, including async effects, fakes vs mocks, and property-based testing.
Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
Validate that an Antithesis property catalog can actually catch bugs. For each safety property, inject one realistic mutant into the SUT, run it, and confirm the targeted property fires. Diagnoses survivors as a bad mutant, bad oracle, bad workload, or bad property, and routes fixes back to antithesis-workload or antithesis-research. Use once the harness is built and a baseline run is green.