http://bugs.winehq.org/show_bug.cgi?id=20232
Jörg Höhle hoehle@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #23868|0 |1 is obsolete| |
--- Comment #6 from Jörg Höhle hoehle@users.sourceforge.net 2009-10-16 05:02:15 --- Created an attachment (id=24161) --> (http://bugs.winehq.org/attachment.cgi?id=24161) Many MCI waveaudio tests
The attached file replaces winmm/tests/mci.c as of 1.1.31. Several sections have been protected by #if FULL_TEST because they cause Wine to hang or crash, so they are disabled by default. It does not perform the original record+play hangs test, which will be added later.
The full tests pass on MS-w2k and XP (non virtual). The non-full parts, loaded with todo_wine, pass on Linux without hanging using ALSA, OSS, both HW and emulation.
I was about to submit them when I noted that the (non-full) tests cause Wine to hang in MacOS. Thus I want to move even more tests into the FULL_TEST section until no hang occurs on MacOS. That'll be better for test.winehq.org. What do you think?
My file provide a correct testcase for bug #15060 (RECORD ignores SET wave format). I believe it demonstrates bug #15423 (hang after second PlaySound). If we had had these tests earlier, we'd better known broken areas in Wine (and not written some code at all, e.g. the MCI sequencer does not support RESUME (MIDI tests not included here)). Interesting insight into test driven development (TDD).
Of course, the goal is to improve Wine so that FULL_TEST can be merged into the normal tests. I already have a few minor patches that fix some of the todo_wine. But not yet the major hangs or random crashes at program exit.
I also plan to add mcimidi and cdaudio tests. Is it ok to add a sample .mid to the Wine tree? (and where to find a free one?)