Intro So far, we've talked about the benefits of property-based tests in my two previous blog posts and . I'm sure for most of you; this concept is still pretty abstract. We've seen the technique, but how do we implement it in C#? In this series, we'll go through all the steps to solve the Diamond Kata using TDD and property-based tests. here here The Diamond Kata Given an input letter, print a diamond starting with A and having the supplied letter at the widest point. e.g., For input: D ---A---
--B-B--
-C---C-
D-----D
-C---C-
--B-B--
---A--- Why did I choose this specific Kata? Well, if you try to solve it with example-based tests, you effectively need 26 tests to make sure it works properly. It may not seem like a lot of tests, but if you try it, you'll soon discover that the first few tests are trivial, and as you approach Z, the tests are becoming harder to read and harder to write. It's usually a code smell that indicates that some property-based tests would be a better approach. TDD In this series, we'll also use TDD, and you'll see that it's much easier to use with Property-based tests than example-based tests. So in excellent TDD practitioners that we are, we are going to start with the most straightforward implementation of the algorithm that we can think of. { { ;
    }
} public class Diamond IEnumerable< > ( ) private static string Generate c char yield return "A" Easy, right? It only works for the A case, but it's a good starting point. I already hear the purists among you. This is not the right way to do TDD! Red -> Green -> Refactor! You should start with a failing test, not with the implementation. You are not wrong, but let's be realistic here. It's just a starting point, and I promise we'll do better TDD going forward :D. The tools Property-based tests is a simple enough concept, but generating proper pseudo-random inputs can be harder than it looks. Fortunately for us, other people solved that issue and built great tools. In our case, we'll use , a property-based testing framework made for F#. FsCheck I'm confused, are we doing this in C# or F#? That's the beauty of .NET, even though the library is made for F#, all the .NET languages compile to and thus are interoperable. It means we can call that library from C#. Intermediate Language (IL or MSIL) Install the NuGet packages, and you are ready to go. dotnet add package FsCheck --version . dotnet add package FsCheck.Xunit --version . 2.14 2 2.14 2 Closing word I think we have all the prerequisites to get started. Stay tuned for the where we'll implement our first test. next post Previously published at https://blog.miguelbernard.com/how-to-get-started-with-property-based-testing-in-csharp/

Introduction To Property-Based Testing in C#

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

5 Tips to Improve Your Productivity in C# 8.0

100 Pieces of Programming Advice from the Book Clean Code by Robert Martin

10 Ways to Prevent and Manage Technical Debt—Tips from Developers

10 Expert Tips for Improving Code Reviews: A Guide for Developers

10 Coding Hacks to Remember in 2023

12 Essential Coding Standards for Quality Web Development

5 Tips to Improve Your Productivity in C# 8.0

100 Pieces of Programming Advice from the Book Clean Code by Robert Martin

10 Ways to Prevent and Manage Technical Debt—Tips from Developers

10 Expert Tips for Improving Code Reviews: A Guide for Developers

10 Coding Hacks to Remember in 2023

12 Essential Coding Standards for Quality Web Development

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps