http://bugs.winehq.org/show_bug.cgi?id=11188
--- Comment #169 from Jason Heeris jason.heeris@gmail.com 2010-06-20 05:53:23 ---
So why is it so hard to ask the people interested in this (or the person who
wrote the fix) to write a test case?
Because you need someone who ticks all the boxes:
1. Encounters this bug with enough frequency to be motivated to help 2. Knows enough about the wine internals to write a test case 3. Has easy access to a copy of Windows to test the other side of things
#2 is sort of optional, since the patch has already been written. #3 is tricky, I know I don't meet it. Anyone who does, AND also meets #1, might just use Windows anyway when they want to play the game, so they don't care as much.
So people who tick #1 get annoyed at the people who tick #2, and no-one likes people in group #3 anyway, and everyone flames everyone else :)
There is noone who reports any issues with the patch.
This could be because the only people who use the patch are listed on this page (maybe not, I don't know).
Can you explain to us how to write a test case to something that happens randomly?
From normal use of WC3, you can get an idea of how frequently the crash occurs.
Then, unless the test case takes a really long time, you run a test case in a loop over a significantly greater number of times than the usual number of attempts it takes to reproduce.