How to Test Multithreaded Code

Mike Perham says multithreaded code is hard to write and even harder to test. His advice is to keep thread management simple, move complexity into smaller methods that can be called directly, and design APIs so threaded behavior can be tested without relying on sleep.

Reading notes

#

• Separate threading from work so the test suite can call smaller internal methods directly.
• Keep the run loop as simple as possible and move most complexity into methods such as fetch and process.
• In some cases, thread management code is verified manually instead of being covered by tests.
• To test threaded code, start the other thread, tell it to process something, wait for the result, and then assert the results.
• Avoid sleep-based tests by using a callback block that sends results back and signals the waiting thread.
• The example uses a queue, a mutex, and a condition variable to coordinate work between threads.