Francois Gouget wrote: > > It seems what you want is unit tests that would garantee that WineD3D > behaves in the way which _you_ have decided. Most of the time that's the > same as writing a _conformance_ test, but apparently in this specific > case it's different. If that's so, then maybe we have to see how we can > distinguish the two (separate test suites, enabling additional tests > when running in Wine, etc). > > This sort of infrastructure could also be useful in the case I > mentionned above, where a specific version of Windows returns something > stupid, but where we'd very much prefer to match the behavior of the > other non-buggy versions. >
This is very interesting and what I always thought lacking in Wine testing. We need both a way of checking that Wine works like Windows and, our a test to our own standards. regards, Jakob