make test drill

Steven Edwards winehacker at gmail.com
Wed Oct 10 02:46:15 CDT 2007


On 10/10/07, H. Verbeet <hverbeet at gmail.com> wrote:
> At that point the only real option is keeping a list of blacklisted
> video drivers (which some applications actually sort of do), but I'm
> not sure we really want to go there. I do think we should investigate
> native failures, and fix them if possible, but if tests fail because
> eg. vmware has a broken d3d implementation, I think the test is
> essentially doing what it should do.

Conversely couldn't you write a test that detects known good
drivers via the loaded kernel module and make the test dependent
on their presence? Rather than running the test and not knowing
if it will pass or fail, it makes more since to only run the test when
we know it SHOULD pass and then if it fails we have identified
a regression.

-- 
Steven Edwards

"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo



More information about the wine-devel mailing list