cscheck

1# CsCheck
2 
3Use CsCheck to explore inputs and action sequences; keep the application's contract visible in the test.
4Let the library generate, shrink, print, and replay counterexamples. Start with the smallest test that
5can falsify the claim, rather than building a testing framework around CsCheck.
6 
7## Choose the test shape
8 
9| What needs checking | Start with | Read when needed |
10| --- | --- | --- |
11| A function, round trip, algebraic law, or data transformation | `Gen` + `Sample` | [Properties and generators](references/properties.md) |
12| An implementation with a simpler reference representation | `SampleModelBased` / `SampleModelBasedAsync` | [Stateful and async tests](references/stateful-and-async.md) |
13| A protocol or lifecycle with explicit state, guards, and requirements | `Spec.From`, then `Exhaustive` and `Conform` | [Executable specifications](references/specifications.md) |
14| Async resources or expectations that must incorporate observed outcomes | Generated command arrays + `SampleAsync`, with cleanup inside each case | [Stateful and async tests](references/stateful-and-async.md) |
15| A failing property, seed replay, or a before/after bug demonstration | Native sampling controls and a concrete regression | [Failure discovery and replay](references/failures.md) |
16 
17Read only the references needed for the task. These examples use xUnit, but CsCheck itself is test-framework
18independent. Preserve the project's existing framework and package-management conventions.
19…