Where to put new (vfw32) compatibility tests that wine fails?
Joerg-Cyril.Hoehle at t-systems.com
Fri Dec 12 10:10:23 CST 2008
I have attached to http://bugs.winehq.org/show_bug.cgi?id=15915#c3 ("Cinepak reportedly not installed") the skeleton of a test that wine fails but win2k passes.
I could turn this into a format that git and wine-patches understands, if I knew the answer to these questions:
o Is it "right" to add compatibility tests that wine is known to fail now (people are already complaining that a wine build does not pass all tests), or are the tests considered more like regression aids and should be added only when they succeed for the first time?
o What directory to add this test specific to vfw32 (or rather iccvid) ?
winmm seems to test sound only, although in principle, it could be there as well.
o Which files to change (beside Makefile.in and testlist.c) so that the patch builds and becomes fully integrated into the wine source tree if it were located in a new file, instead of e.g. being added to tests/mmio.c?
More information about the wine-devel