Does anyone have any advice for a consistent way to unit test a multithreaded application? I have done one application where our mock \"worker threads\" had a thread.sleep
TypeMock (commercial) has a unit testing framework that automatically tries to find deadlocks in multithreaded applications and I think can be set up to run threads with predictable context switching.
I saw a demo this week at a show -- apparently it's in Alpha (called Racer)
http://www.typemock.com/Typemock_software_development_tools.html