mmdevapi tests

Hi,

I've a couple of mmdevapi tests that I could put into submittable
form soon, however there's one big problem: There are three different
backends (ALSA, OSS, MacOS) and each one needs a different set of todo_wine.

How to deal with that?

In the past, when I worked alone (e.g. on the MCI), I simply submitted
problematic tests only after I had patches that prevented Wine from
crashing or possibly even implemented the functionality.

Now of course, I could open an issue (one per backend?), append the patch
and say "Wine must pass this". However that won't get as much test coverage
(by neither native machines, nor Wine boxes).

What do you suggest?
 Jörg Höhle

[Andrew Eikum]

On 08/02/2011 09:30 AM, [e-mail] wrote:
> I've a couple of mmdevapi tests that I could put into submittable
> form soon, however there's one big problem: There are three different
> backends (ALSA, OSS, MacOS) and each one needs a different set of todo_wine.
>
> How to deal with that?

I think the best thing to do is mark only the tests that fail on all 
drivers as todo_wine. Tests that pass on any driver should not be marked 
todo_wine. The idea is that the drivers should be as similar as 
possible. So if something works on one driver and not others, then the 
broken drivers will appear in the test results and should be fixed.

Tests that crash on some drivers and not others should be accompanied by 
a fix for the crashes.

Andrew