Develop a Unit Test Plan for the module that
you have implemented. The Test Plan should identify each test case you intend to
conduct, showing the required input and the expected output. When specifying
the input and output, be precise. That is, specify the exact values to be used
for input and the exact values you expect as output. For example, if your test
case is to test for a value of "month" greater than 12, specify the
required input as "month=13", or "month=17" not just as
"month>12". The reasons for doing this are to make sure that the
person doing the testing inputs the appropriate values, and that if the
expected result does not occur, you know the exact values that were used to
cause the problem. Likewise, specify the exact output you expect. If you expect
your program to display an error message for a given test case, specify the
exact message to be displayed (e.g., "The value specified for the month is
incorrect. It must be an integer between 1 and 12."), not just that you
expect an error message.
Make sure you specify sufficient test cases
to insure that each statement in your module is executed at least once and that
all conditions and loops are tested adequately. Base your test cases on the
logic in your code not on input and output conditions (i.e., do white box, not
black box, testing).
|
UNIT TEST PLAN & TEST RESULTS FOR MODULE: |
|
|
||||
|
Test Case# |
Description |
Required Inputs |
Expected Results |
Actual Results |
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||
|
|
|
|
|
|
||