coyote VS awesome-analyzer

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...

Well the problem is that there isnt really any proper toolchain for this. https://github.com/Cybermaxs/awesome-analyzer here you can find some analyzers that I would recommend. I would suggest roslynator, errorprone, sonar and multithreading analyzers. Also you might want to check out the one created by microsoft (altough as I understand this is more for desktop/vs plugin scenarios) https://www.nuget.org/packages/Microsoft.VisualStudio.Threading.Analyzers/ Keep in mind that altough theese analyzers can help you they can also easily stab you in the back if you are apply refactorings without understanding them. (for example blindly using ConfigureAwait(false) with async code is fine in an aspnet app but might backfire in uwp or wpf.