next up previous contents
Next: 5 Integration Testing Up: 4 Unit Testing Previous: 4.5 Procedure for Unit   Contents


4.6 Unit Testing Reports

Unit Testing reports are to be named UNITNAME.UTreport.REPORTNUMBER, where UNITNAME is the name of the unit that has been tested, and REPORTNUMBER is the number of the report. These reports are to be stored under /test-reports/sam/unit in the home directory. For example, if unit GetFood is tested for the first time, the report will be called GetFood.UTreport.1. The format of a Unit Test report is just the output from running a PyUnit (see section 14.1) or Mtest (see section 6) test suite. Unit Test Reports are created automatically by the testing script (see section 1.7).

Here is an example of a Unit Testing report:

-------------------------------------------------------------
Unit Test Report for AboutDialog

Fri, 12 Jul 2002 15:11:35 +0000

-------------------------------------------------------------
Running setUp: no setUp needed for this unit test
-------------------------------------------------------------

		Name:			Test1
		Purpose:        Tests that the widget_tree of AboutDialog is assigned
		Uses:           AboutDialog 
		Preconditions:  None 
		Postconditions: None 
		Author:         mayadm 
		Date:           12/7/02
		
Test case Passed
.Running setUp: no setUp needed for this unit test
-------------------------------------------------------------
Name:		Test2
		Purpose:        Tests that the widget_tree of AboutDialog hides itself
		Uses:           AboutDialog 
		Preconditions:  None 
		Postconditions: None 
		Author:         mayadm 
		Date:           12/7/02
		
Test case Passed
.
----------------------------------------------------------------------
Ran 2 tests in 0.109s

OK