http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660The ability to stop all threads except this one. The ability to view current locks for each thread The ability to see what a thread is waiting on. http://ayende.com/3262/brute-force-concurrency-testing#comment4http://ayende.com/3262/brute-force-concurrency-testing#comment4Sun, 13 Apr 2008 12:50:40 GMTOnly slightly OT, but what would you want the debugger tooling to ideally provide/do (that it doesn't today) to assist with debugging threading/concurrency/parallelism scenarios... If you have any thoughts please share. http://ayende.com/3262/brute-force-concurrency-testing#comment3http://ayende.com/3262/brute-force-concurrency-testing#comment3Fri, 11 Apr 2008 19:03:54 GMTShuffling the tests or any other way of automatic random testing is not a bad idea but on each test run you need to log the random seed or the shuffle order. If you cannot rerun the test exactly as it was ran you cannot recreate the bug which makes is useless for any real debug work. http://ayende.com/3262/brute-force-concurrency-testing#comment2http://ayende.com/3262/brute-force-concurrency-testing#comment2Thu, 10 Apr 2008 08:13:04 GMTMaybe you could shuffle the list of tests before you begin executing them? This would let you expose more bugs as you wouldn't always have the same sequence of tests and hence similar overlapping tests every time. Of course, it makes the test even more nondeterministic.... http://ayende.com/3262/brute-force-concurrency-testing#comment1http://ayende.com/3262/brute-force-concurrency-testing#comment1Wed, 09 Apr 2008 20:56:03 GMT