Skip to main content

Property based testing - Updating FsCheck to version 3.x

f you have never heard about Property based testing, I would recommend to check my blog series about it first. But if you are too lazy to go through all these posts, here is a short definition:

Property-based testing is a powerful testing methodology used in software development to verify that a system behaves correctly across a wide range of inputs. Instead of writing individual test cases with specific inputs and expected outputs, property-based testing defines properties—general rules that should always hold true for a given system.

It serves as an alternative to example based testing where we focus on a set of example cases to validate the behavior of our code.

There are a lot of libraries out there that help you write Property Based Tests. In .NET I mainly use FSCheck and CSCheck. As I’m doing more and more Python, I also start using Property Based Tests there through Hypothesis.

In this post I’ll focus on FSCheck and how to update to the latest version as some breaking changes were introduced and the documentation is not that helpful when upgrading (although you can find some details in the release notes).

Updating FsCheck to version 3.x

FsCheck works for both C# and F#. Due to the language differences however the 2.x version didn’t feel always that intuitive when using it in C#. To improve the experience in version 3.x, the API is now split into a functional (for F# consumers) and fluent (for C# and VB.NET consumers) interface.

Update to the latest version of FsCheck:

dotnet add package FsCheck

dotnet add package FsCheck.XUnit

After upgrading I got a few compiler errors that I had to fix.

First add a reference to the FSCheck.Fluent namespace:

This already fixes a lot of the errors I got.

To make the Prop.Throw work again I had to add a reference to the FSCheck.FSharp namespace:

Next thing I had to do was to replace the calls to Arb.Default with ArbMap.Default:

A last change I had to make was to update the configuration code as the configuration object is now immutable:

More information

Property based testing in C#–Part 1

Property based testing in C#–Part 2

Property based testing in C#–Part 3

Property based testing in C#–Part 4

Property based testing in C#–Part 5

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...