Skip to main content

Property based testing in C#–Part 4

In this multipart blog post I want to introduce you in the world of property-based testing and how to do this in C#.

In the first part, I gave you an introduction on what property-based testing is, why it useful and how it can help you write better code. In the second post, I showed you a concrete example on how to start writing property-based tests in C# using FsCheck. In a third post I explained how property-based tests can help  to find edge cases and to understand a codebase better.

In this post I continue the journey by having a look at how to write our own generators. If you didn’t read my previous post, generators are the tool that helps you to select a value from an interval. For some of the available types in .NET, a default generator (and shrinker) exists but sometimes it is necessary to create your own generators.

Create your own FsCheck generator in C#

Creating your own generator for FsCheck is easy in C#, the only thing you need is a public static class with a public static method that returns an Arbitrary<T>.

In our previous post, we used a Filter() in our test to return only positive dates:

Let’s see how we can do the same thing using a custom generator:

To use this generator, we need to specify it as a parameter of the [FsCheck.NUnit.Property] attribute:

As the library that we were testing allows you to generate National Registration Numbers, we can take our sample above one step further and create a generator for it:

Now we can improve our test code to use this generator:

Remark: It is possible to add multiple static Generator methods to one static class.

Generator utilities

In the example above, we started every time from an existing generator and expanded from there. But it is also possible to start from scratch. In that case, there are a few utility functions that can help you along the way.

One of the most used utility functions is Gen.Choose(), which makes a random choice of a value from an interval, with a uniform distribution.

Here is an example where we use this to generate a month in a specific year:

Create your own FsCheck Shrinker in C#

So far the generators either used the default shrinker for the type or had no shrinker defined. Writing your own shrinker is easy thanks to the support of iterators in C# (through yield return).

One way to add a shrinker is to use an overload of the Arb.From() method:

Another option is to create your own Arbitrary<T> instance and override the Shrinker method:

If we run our tests again, we see that the results are shrinked to 1/01/2000. This is a good indication that there is something wrong with National Registration Numbers generated after that date.

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         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

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’: ...