FsCheck

FsCheck is a free property-testing library for .NET, best suited to developers who want to probe program behavior with generated inputs. Its failure shrinking and flexible generators make it a strong fit for properties that are hard to cover with hand-picked examples, provided teams are comfortable with its API constraints and documentation caveats.

Overview

FsCheck checks developer-defined properties against randomly generated cases, helping uncover edge cases that a short list of examples may miss. The approach works best when a team can state a useful rule about its code; it does not supply those rules or replace ordinary example-based tests.

When a check fails, FsCheck shrinks the input and reports a minimal counterexample. That gives developers a more focused failure to investigate. Custom generators and shrinkers can be grouped into Arbitrary instances, allowing teams to shape both the test data and how failures are reduced.

Properties can be written in F#, C# or VB. The project documents integrations with xUnit.net and NUnit, plus user-created integrations for Expecto, Fuchu, AutoFixture and MSTest. Its built-in runner can execute properties from F# or C# Interactive, command-line programs, or a test framework. Parameterized cases and parallel execution are supported.

Key features

• Generated property checks: Random inputs exercise a stated property across many cases, which suits rules expected to hold broadly. Properties cannot have generic types; type annotations can resolve types when needed.
• Failure shrinking: FsCheck reduces a failing input to a minimal counterexample, making an unexpected case easier to inspect and reproduce.
• Custom generators and shrinkers: Arbitrary instances bundle custom data generation with custom shrinking. This is useful when the default shape of generated inputs does not match the domain being tested.
• Runner and framework support: The built-in runner offers a way to run checks from interactive sessions, command-line programs, or test frameworks. The documented exception-expectation function is unavailable in the C# API, a relevant gap for C# teams that need that behavior.

Pricing

FsCheck costs nothing. The plan is a BSD-licensed library distributed through NuGet; the project says the license permits modification and redistribution for commercial and non-commercial use. There is no paid tier or free trial to weigh against a capped entry plan.

FsCheck and its NUnit and xUnit.NET plugins can be installed from NuGet. Developers can use the same free library across F#, C# and VB, with no per-seat or usage charge stated.

Platforms

FsCheck supports Linux, macOS and Windows. Its language support covers F#, C# and VB, making it relevant to .NET teams working across those operating systems.

Who it's for

FsCheck is a good choice for .NET developers who can express expected behavior as properties and want generated cases to challenge those rules. Teams that need control over domain-specific inputs can benefit from custom generators and shrinkers, while shrinking can reduce the work of understanding a discovered failure.

Teams adopting it should account for the documentation gap: the site says its 2.x documentation is out of date and incomplete, while version 3.x is maintained and receives new features and fixes. Developers should check which version their project uses. Stateful model-based testing is available in an Experimental namespace, where minor releases may break code because semantic-versioning guarantees do not apply; it is a less suitable foundation for code that needs a stable API.

Pros and cons

• Pros: Minimal counterexamples make generated failures easier to diagnose; custom generators and shrinkers let teams tailor inputs; the built-in runner and documented framework integrations offer several ways to run properties; the BSD license permits commercial use and redistribution.
• Cons: The current documentation is described as out of date and incomplete for 2.x, so version-specific guidance needs care; properties cannot use generic types; the documented exception-expectation function is missing from the C# API; experimental stateful testing carries API breakage risk between minor releases.

Alternatives

Property-Based Testing Tools is a useful category overview for comparing options. For a .NET project, FsCheck is the option here with F#, C# and VB properties and a NuGet distribution.

Choose ScalaCheck if a free BSD-3-Clause library better fits your project. Choose Racket QuickCheck when you want a free Racket package and can use Racket v6.0 or newer. Gopter is a free, MIT-licensed Go property-testing library. Choose fast-check for a free, MIT-licensed JavaScript or TypeScript option. JSVerify is another free, open-source JavaScript property-testing library. Choose Scala Hedgehog for an open-source Scala testing library, or PropCheck for a free MIT-licensed Ruby gem requiring Ruby 2.5.1 or newer. QCheck is a free OCaml property-testing library under the BSD-2-Clause license.

Unit Testing Frameworks provides a broader category view for readers comparing testing approaches.

Verdict

Choose FsCheck if you build .NET software and want generated inputs, customizable data and shrunk counterexamples in a free property-testing workflow. Its main advantage is turning a failing property into a small, inspectable case. Look elsewhere if the C# exception API gap, generic-property constraint, or experimental model-based API conflicts with your needs; check the version 3.x documentation carefully before settling on an integration.