Unit Testing

You should unit-test everything, of course. However, you also need to make sure you don't omit anything from testing and ensure that you're testing your classes in the correct manner. The following IEEE standards are intended for software quality, including testing and verification:

• IEEE 829-1983, "Standard for Software Test Documentation"

• IEEE 1008-1987, "Standard for Software Unit Testing"

• IEEE 1012-1986, "Standard for Software Verification and Validation Plans"

• IEEE 1059-1993, "Guide for Software Verification and Validation Plans"

The IEEE standard 1008-1987, "Standard for Software Unit Testing" (http://standards.ieee.org/reading/ieee/std_public/description/se/), provides a helpful overview of how you should test your application. It has the following outline:

1.	Introduction
1.1	Abstract ” The abstract and purpose of this document and who the audience is.
1.2	Scope ” Describe the testing process, including the major phases.
1.3	Glossary ” List and define the technical language included in this document.
1.4	References ” Define any resources used for this document, such as IEEE standard XYZ .
2.	Test Plan ” Describe the plan for testing.
2.1	Schedules and Resources ” Name the people, tasks , and dates for specific testing actions.
2.2	Test Reporting ” Answer the question "How will test results be documented and then reported ?"
3	Testing ” Describe how the actual tests will be conducted .
3.1	Static Testing ” Describe how you will review code and documentation.
3.2	Unit Testing ” Describe how you test each unit, perhaps with JUnit (see http://www.junit.org).
3.3	System Testing ” Describe how you will test the entire application (for example, successfully reserved a seat).
3.4	Acceptance Testing ” Describe how you will have another person test the entire application and then how you will make sure the submission package is complete.