Intro Now that we have all the , we are finally ready to write our first Property-Based test. tools installed FsCheck Creating a property-based test is as simple as tagging a method with the [Property] attribute, similarly as you would do in xUnit with the [Fact] or [Theory] attributes. If you dig a little, you will realize that there's a lot of configurable options on the [Property] attribute. You can control how many random tests will be run each time, timeouts, etc. One of them is essential; the Arbitrary property. That property will define which method to use to generate random inputs. In our specific case, we are not interested in all the possible values of char. We only care about the 26 letters of the alphabet. To scope the input, we'll need to configure a generator that will do just that. Generators Generators are relatively simple. Create a static class Add a static method that returns Arbitrary<TypeYouWantToGenerateValueFor> Voilà You can write your randomization logic, but it's usually better to start from the built-in methods as they are already well balanced. { =>
            Arb.Default.Char().Filter(c => c >= && c <= );
} public static class LetterGenerator Arbitrary< > ( ) public static char Generate 'A' 'Z' Not Empty Test It may seem basic, but it's quite essential. We want to make sure we always have a non-empty result. [ ] { (LetterGenerator) })] { Diamond.Generate(c).All(s => s != .Empty).ToProperty();
} Property(Arbitrary = new[ typeof Property ( ) public NotEmpty c char return string One thing I forgot to mention earlier, the test method also needs to return a property object. Fortunately for us, the library contains an extension method that can transform any boolean expression into a property object by calling ToProperty(). So our test reads like this: Call the method with the provided input char c. Diamond.Generate() Make sure all the lines of the returned diamond are not empty. Use the ToProperty() method to wrap it into a property object. Stay tuned Stay tuned for my on this about solving the diamond kata with property-based testing. The will try to define properties for the first and last lines of our diamond. next posts series following post Previously published at https://blog.miguelbernard.com/input-generators-in-property-based-tests-with-fscheck/

Alphabet

Property-Based Testing: The Diamond Kata, First and Last Line Content

Introduction To Property-Based Testing in C#

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

Testing in C#: Property-Based Testing With Input Generators

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

5 Tips to Improve Your Productivity in C# 8.0

111 Stories To Learn About Csharp

130 Stories To Learn About Dotnet

C# 8.0 Indices and Ranges

3 Insanely Easy Changes You Can Make To Clean Up Your Code

5 Tips to Improve Your Productivity in C# 8.0

111 Stories To Learn About Csharp

130 Stories To Learn About Dotnet

C# 8.0 Indices and Ranges

3 Insanely Easy Changes You Can Make To Clean Up Your Code

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps