Testing Plan
The Plan
The testing of java tester consisted of 4 main stages with 4 different
data types (BSet, Stack, BBag, Pnet), all of which were tested with the
command line version (danish) first, and then with the user interface.
Each stage had specific aspects in mind in regards to the testing of the
overal product.
BSet
BSet is a bounded set of integers, or an unordered set of integers with no
duplicate entries of a fixed maximum size. This was used to test the
basics of the tester yet had some reasonably complicated axia to attempt
to find any large glaring bugs that may have existed.
Stack
Stack is a stack of integers of a fixed maximum size. Stacks are a "first
in last out" (FILO) data structure. Stack was used as another simple data
structure to try to find any other existing large bugs that may have been
missed in the testing with BSet, as it had some differences in the code,
axia, etc.
BBag
BBag is a bounded bag of integers, similar to BSet only it allows
duplicates in the structure, i.e. it has an additional array to hold the
number of each element in the structure. Hence, it was a natural derived
class from BSet (i.e. inherits BSet). It was also contracted through the
class contract.java that was included with the tester. The object of BBag
was to begin to test the tester with more complicated structures, more
specifically, one that used inheritance and importing files, to make sure
they were compatible with the tester.
Pnet
Pnet is a Petrinet, or a version of a finite state machine. This is a
very complicated structure, and had many axia to test. We felt this
constituted an industrial strength data structure with enough axia that,
if the tester did not fail, would provide us with the confidence that the
tester worked correctly. NOTE: Pnet was not used as an example in the
user manual since it is used in Comp204.
Previous Topic
Next Topic
Created 04/06/98 by Tim Preston
Revised 04/29/98