Unit Test Frameworks
by Paul Hamill

This errata page lists errors outstanding in the most recent printing.

If you have technical questions or error reports, you can send them to
booktech@oreilly.com.  Please specify the printing date of your copy.

This page was updated March 16, 2006.

Here's a key to the markup:
	[page-number]: serious technical mistake
	{page-number}: minor technical mistake
	<page-number>: important language/formatting problem
	(page-number): language change or minor formatting problem
	?page-number?: reader question or request for clarification



Confirmed errors:


{27}  Figure 3-3;
Both classes in the diagram are labelled TestFixture. The lower class should be label TestCase.



(33)  2nd paragraph;
"With the additional message, the rest results..." should read
"With the additional message, the test results...".  The word "rest" should be "test".



(71)  Figure 7-3;
TestSucessListener class is misspelled (it's missing one 'c').


{114}  paragraph below code, 5th sentence;
the text should be changed from:

"If it is FALSE, the function test_failure() is
called. This function reports the file location of the
failure and exits."

to:

"If it is FALSE, the file location of the failure is
reported, and the test terminates."