FsCheck vs jqwik
FsCheck
fscheck.github.io
jqwik
jqwik.netSide by side
| Figure | FsCheck | jqwik |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| Plans published | 1 | 0 |
| Spec score · Unit Testing Frameworks | 8.4 (#2) | 6.9 (#31) |
| Spec score · Property-Based Testing Tools | 8.4 (#3) | 7.0 (#19) |
| Audience | FsCheck is for developers who want to test properties of .NET programs with generated inputs. | The site describes jqwik as a library for programmers writing and running properties on the JVM. |
| Failure reports | When a property fails, FsCheck displays a minimal counterexample by shrinking the failing input. | When a property fails, jqwik reports the relevant exception, base parameters, original failing sample, and shrunk sample. |
| Purpose | FsCheck automatically tests .NET programs by checking properties against randomly generated cases. | jqwik brings property-based testing to the JVM, focusing mainly on Java and Kotlin, with Groovy also supported. |
Plans
In their own words
FsCheck
FsCheck checks properties of.NET programs against randomly generated cases. Developers can express properties in F#, C# or VB, then run them with the built-in runner from an interactive session, a command-line program or a test framework. Integrations are documented for xUnit.net and NUnit, with user-created integrations for Expecto, Fuchu, AutoFixture and MSTest. When a property fails, FsCheck shrinks the input and shows a minimal counterexample. Developers can also define custom generators and shrinkers and group them in Arbitrary instances. The library supports parameterized cases and parallel execution, and its packages and NUnit and xUnit.NET plugins are available from NuGet. FsCheck is free: its listed plan is free, with a BSD license permitting commercial and non-commercial modification and redistribution. It runs on Linux, macOS and Windows. The project maintains version 3.x, but its documentation covers 2.x and is described as out of date and incomplete. Its model-based testing API is experimental and exempt from semantic-versioning guarantees.