Hi Suzie, Does this help you at all? This is part of the documentation that goes through an example of using JUnit. Identifying problems in your code In this section, you will review the different indicators for identifying problems in your code. Build problems are displayed in the Problems view and annotated in the vertical ruler of your source code. 1. Open junit.framework/TestCase.java in the editor from the Package Explorer view. 2. Add a syntax error by deleting the semicolon at the end of the package declaration in the source code. Editor with missing semicolon 3. Click the Save button. The project is rebuilt and the problem is indicated in several ways: * In the Problems view, the problems are listed, * In the Package Explorer view, the Type Hierarchy or the Outline view, problem ticks appear on the affected Java elements and their parent elements, * In the editor's vertical ruler, a problem marker is displayed near the affected line, * Squiggly lines appear under the word which might have caused the error, and Jim Homme, Usability Services, Phone: 412-544-1810. ________________________________ This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates.