WHITE BOX TEST PLAN
The white box test plan consists of the invocation
coverage plan, the branch coverage plan, the loop coverage plan,
and the condition coverage plan. Basically, this plan test to
see that every line of code in our system is executed. The individual
coverage plans are as follows:
For the Control Panel:
Invocation Coverage Plan
Every method involved in the Look-and-Feel will write
out to a test window which will display strings consisting of
what method and what parameters were passed to it.
Example: If we create a Button, a call will be
placed inside the constructor, and update, along with other methods.
When these methods are invoked, relevant strings are written
to the test window.
We then view the test window to see if all the necessary
calls were made.
Branch Coverage Plan
Exhaustive user input testing. By this we mean that
every possible combination of components and their properties
must be selected and displayed in a window. With 17 components,
each having at most three property settings, we are looking at
a very large list of possible cases.
Loop Coverage Plan
The loops within the control panel are fully exercised
when a component_list is updated and when a component is removed
from a component_list.
Condition Coverage Plan
Again, by the nature of our program, conditional
branching situations are brought up by user selected combinations
within the Graphical User Interface.
Example: If the saved data file exists (yes/no) then
run the applet with the file OR run the applet without the file.
Example: If the property does not exist, add it by
creating a dummy M_Class component which will add a test property
and change it, OR create a new instance of a M_Class which already
exists.
Example: If the M_Class name does not exist on the
Component List then a dummy M_Class is added to the Component
List and a new list is created for this specific component OR
a new instance of a component is placed at the tail of the linked
list of the same type.
Example: If all the Instances of M_Classes are removed from a type of component list then the component is removed from the Component List.
Page 3 |
Document Index |
Page 5 |