Concurrent Code - Test It! - How?

Felix is running a draft of his ACCU 2020 presentation:

Most probably everybody who has written code that runs concurrently experienced that one has to think differently compared with code that runs serially. Since we, humans are pretty bad at predicting the future, especially when there are multiple futures in parallel, we guard our code with tests against an unexpected outcome.
In this session I want to share my experience that I gained by developing the open source stlab.concurrency library and the products I am working on in my company.

At the beginning I will give an overview of the differences and potential problems compared to single threaded tests, for example race conditions, non-deterministic program flow, and the influence of different hardware.

In the second part I will provide an overview of tools for the major platforms that can support the development, and how to set up a toolbox that extends one's favourite unit test framework.

I want to go into much deeper detail in the third part of the session with a case study of extending existing code.

After this session everyone should have a scratch pad filled with guidance on how to start writing tests for concurrent code and how to strengthen already existing tests.