coyote VS NSubstitute

ex: https://github.com/microsoft/coyote/blob/main/Samples/Accoun...

Microsoft has a library/tool called Coyote* that helps with testing distributed systems; you can write tests/specifications, Coyote will systematically explore nondeterminism in your system and check if your tests still pass. If there's a failure, it'll show the sequence of events that led to the failing test.

I started a project to implement Raft with a KV-store on top, similar to the article, meaning to use Coyote to test it; I didn't get that far before losing interest, though. It's reassuring to read that it took Phil several months to write the code in the post, it's good to know that this is a decidedly nontrivial problem.

* https://github.com/microsoft/coyote

Something like coyote by MS?

If you're looking for similar concurrency testing in the dotnet world, checkout Coyote:

https://microsoft.github.io/coyote/

https://innovation.microsoft.com/en-us/exploring-project-coy...

MS provides a framework for testing for concurrency issues: https://microsoft.github.io/coyote/.

I suggest you try Microsoft Coyote

Visualizations do help a lot when model checkers and concurrency schedule exploration tools like Coyote find bugs. Coyote include the ability to visualize the traces if you express your concurrency using actors (see https://microsoft.github.io/coyote/#concepts/actors/state-ma...)

It also allows you to implement your own "logger" through which you can emit enough information to construct some cool visualizations. I had a lot of fun working on visualizing an implementation of Paxos using Coyote (then P#) (screenshot at https://ibb.co/TTk2hYb)

If curious, you can learn more in the Coyote website https://microsoft.github.io/coyote

Hi HN,

The tweet links to a couple of tutorials showing how to test an extremely simple CRUD service using Coyote to find concurrency bugs. Developers write simple unit tests whose concurrency is explored by Coyote to find bugs. You might be surprised to learn how we can write a number of interesting concurrency tests for even the simplest of CRUD services.

https://microsoft.github.io/coyote/#tutorials/first-concurre...

a. you might do so purely out of argo cult, i.e. because someone told you this was the right thing to do™, and that's a silly exercise. b. you could also be doing this for a good reason: to use the interface with a mocking tool like NSubstitute

When comparing it to one of its most well-known alternatives, NSubstitute, which has "only" reached 85.6 million downloads, it is fair to say that Moq is the most widely used mocking library in the .NET ecosystem.

Maintainer rejected the PR. They have temporarily disabled the integration in https://github.com/moq/moq/pull/1375 but kept the SponsorLink project reference in the source code. It seems like their intent is to re-enable the integration at a later point :(

NSubstitute [0] might be an alternative. Or to fork Moq pre-4.20.

[0] https://nsubstitute.github.io/

In terms of mocking there are several frameworks you can use, but I've mainly relied on Moq and NSubstitute. Within this demo, I'm going to use NSubstitute as I've found it a little easier to use.

it will change the URL from https://github.com/nsubstitute/NSubstitute to https://github.dev/nsubstitute/NSubstitute (or you can just nav there yourself).

NSubstitute

🔗 NSubstitute documentation | NSubstitute

If you use NSubstitute (the best mocking .NET framework), then you have to install this small yet useful plugin right now. It kindly generates mocks and Arg.Is / Arg.Any.

Another nice mocking framework is NSubstitute https://nsubstitute.github.io/