Results for “property-testing”
11 skillsProperty Based Testing
Provides guidance for property-based testing across multiple languages and smart contracts, helping detect patterns where PBT offers stronger coverage than example-based tests.
6k · bundle
Rust Testing
Guides writing Rust tests with TDD, covering unit, integration, async, property-based, mocking, and coverage patterns.
1
Rust Testing
Provides Rust testing patterns covering unit, integration, async, property-based tests, mocking, and coverage, following TDD methodology.
0
Kotlin Testing
Write reliable, maintainable Kotlin tests using Kotest, MockK, coroutine testing, property-based testing, and Kover coverage following TDD methodology.
226k
More results
Kotlin Testing
Write reliable Kotlin tests using Kotest, MockK, coroutine testing, property-based testing, and Kover coverage, following a TDD workflow.
0
Fsharp Testing
Write and organize F# tests using xUnit, FsUnit, Unquote, FsCheck for property-based testing, and integration test patterns with ASP.NET Core and Testcontainers.
226k
Fsharp Testing
Provides F# testing patterns using xUnit, FsUnit, Unquote, FsCheck, and integration testing with Testcontainers and WebApplicationFactory, including test organization and anti-patterns.
0
Test Tagging
Analyzes test suites across multiple languages and tags each test with standardized traits (positive, negative, critical-path, etc.) for better test categorization and coverage visibility.
4k
Testing Quality Assurance
Coordinates quality assurance workflows by routing testing tasks to specialized sub-skills for API testing, performance benchmarking, test analysis, tool evaluation, and process optimization.
2 · bundle
Tdd
Enforces strict outside-in red-green-refactor TDD with one-failure-per-turn discipline, predicting failures before every run, hardcoding minimum changes, and using triangulation and property-based testing. Triggers on explicit TDD requests and tasks phrased as 'implement', 'add', 'write a function', 'build a feature'.
7
Tw Invariant Ace
Define owned inductive invariants and enforce them at parse, construct, API, DB, lock, or transaction boundaries, with counterexample-driven verification.
7