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

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

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.

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. www.myangularapp.com ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. www.mywebsite.com/angularapp ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: https://angular.io/guide/deployment --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should