Cleaned up the text concerning the need for conformance tests.

This commit is contained in:
Michael Jacobsen 2004-04-07 19:06:35 +00:00 committed by Alexandre Julliard
parent cd69b118c2
commit f837179645

View file

@ -4,12 +4,17 @@
<sect1 id="testing-intro"> <sect1 id="testing-intro">
<title>Introduction</title> <title>Introduction</title>
<para> <para>
With more The Windows API follows no standard, it is itself a de facto The Windows API follows no standard, it is itself a de facto standard,
standard, and deviations from that standard, even small ones, often and deviations from that standard, even small ones, often cause
cause applications to crash or misbehave in some way. Furthermore applications to crash or misbehave in some way.
a conformance test suite is the most accurate (if not necessarily </para>
the most complete) form of API documentation and can be used to <para>
supplement the Windows API documentation. The question becomes, "How do we ensure compliance with that standard?"
The answer is, "By using the API documentation available to us and
backing that up with conformance tests." Furthermore, a conformance
test suite is the most accurate (if not necessarily the most complete)
form of API documentation and can be used to supplement the Windows
API documentation.
</para> </para>
<para> <para>
Writing a conformance test suite for more than 10000 APIs is no small Writing a conformance test suite for more than 10000 APIs is no small