hedgehog VS FsCheck

> - rose tree "integrated shrinking" (eg. Hedgehog) follows the constraints of the generators, but has issues with monadic bind.

We're at the limits of my amateur knowledge, but I believe this is a fundamental limitation of monadic bind/generators. Instead, you should prefer applicative generators for ideal shrinking. https://github.com/hedgehogqa/haskell-hedgehog/issues/473#is...

In other words, applicative generators do not use "results of generators to dispatch to another generator", but instead shrinking is optimal due to the "parallel" nature of applicatives (I'm using "parallel" in the monadic sense, and not the sense of article's "threading" sense).

I've had some PRs open on hedgehog for one and two months respectively. It looks like the maintainer isn't currently very active, which is fair enough. This isn't about criticizing him, and I'm not trying to take over the repo.

Testing libraries like hedgehog often run tests in parallel, so you may find related issues to work on.

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

As you can see from the imports statement we're relying on FsCheck to generate some random values for us.

C# - FsCheck

https://fscheck.github.io/FsCheck/ can hopefully generate random inputs automatically or with low effort for many methods to get your code coverage up. You don’t even need to write real tests right now, just call the methods with the random inputs and check they don’t fail.

Try using F# for tests. It has some great libraries like FsCheck (https://fscheck.github.io/FsCheck/).

At Symbolica we're building a symbolic execution service that explores every reachable state of a user's program and verifies assertions at each of these states to check that the program is correct. By default it will check for common undefined behaviours, such as out-of-bounds memory reads or divide by zero, but it can also be used with custom, application specific, assertions too just like the kind you'd write in a unit test. Seen from this perspective it's kind of like FsCheck (or Haskell's QuickCheck or Python's Hypothesis), but much more exhaustive and without the randomness.

Maybe something like QuickCheck, a quick search gave me this library for .NET https://github.com/fscheck/FsCheck

Because of the above I've generally been using tools like Stryker.NET and FsCheck to augment my testing suite. I'm still doing unit testing to find the more obvious "I haven't had my coffee, let's make sure I'm doing what I think I'm doing" bugs. I'm just using things like mutation testing, property testing, fuzzing, etc. to find the deeper issues in my code. There's a ton of libraries out there, including one that I've built for myself to help with testing but FsCheck and Stryker are just beautiful. And if you're interested in fuzzing, SharpFuzz is a great option. But that one isn't quite as easy of an on ramp compared to the other two that I mentioned.

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.

Side note, if you are thinking about testing in general, might be interested in property based testing. See for example https://fscheck.github.io/FsCheck/