AutoBogus VS fsharp-hedgehog

To do all this you need test though...and that's where ]Bogus](https://github.com/bchavez/Bogus) and Auto Bogus come in handy. They both generate semi random test data that you can use to populate whatever method you've decided to use. You can setup rules so for specific fields, they have built in generators for common things like names and addresses. Auto Bogus can be used to populate large/complicated objects with data automatically (it can be slow if you don't use .WithRecursiveDepth() or.WithTreeDepth() )

Just be careful, this is an outstanding bug in this library that's been going on for years. If you try to dummy up an object with a large amount of properties, it ends up in some sort of deadlock (or just takes an extremely large amount of time). People seem to have also reproduced it with properties marked virtual. I sometimes deal with 3rd party vendor libraries and it would had been nice to be able to use this with the worst offenders.

Unit testing: I personally use FsUnit, specifically FsUnit.Xunit. There's some other libraries like Expecto and Hedgehog (property testing), but I haven't found a reason to use them. I recently started experimenting a little with Hedgehog. FsUnit integrates well into Visual Studio, since it sits nicely on top of NUnit and xUnit, and it's done everything I've needed so far.

Looks cool. Is there a reason why you didn't use FsCheck or Hedgehog? They're built to generate random data for testing, and can return the seed if a test fails so you can rerun the test with the exact same data once you figure out what the problem is - which is useful if the failure condition is rare.

Haskell has QuickCheck and Hedgehog, and dotnet has both as well. F# is favored, but there's C# interop.

Dotnet has FsCheck and Hedgehog. Both are primarily aimed at F#, but C# is supported as well.

Hedgehog