"Saulius Krasuckas" <[EMAIL PROTECTED]> wrote:

Using test cases to determine the behaviour of Windows provides a way to verify both the code that's written today, and code that will be written a year later. It's not just legally better, it's easier to do, easier for others to understand, and gives us a way to verify our code.

Yes, but how would you write a test for a badly implemented function, when you don't know its name or even name of a DLL it resides in?

Then by what means do you know that the API is misbehaving?

--
Dmitry.


Reply via email to