CS U370 Assignment #3.
Section:  Clinger
Assigned: Tuesday, 3 October 2006
Due: Tuesday, 10 October 2006

You will write a black-box test program in Java for the Issue
ADT of assignment 2.

Collaboration between students is forbidden on this assignment.
You are responsible for keeping your code hidden from all other
students.  Part of your grade will be determined by how well
you hide your code, part of your grade will be determined by
how well you follow the instructions for submitting your code,
part of your grade will depend upon the correctness of your
code, part of your grade will depend upon the effectiveness
of your tests, and part of your grade will depend upon the
readability of your code (e.g. formatting and comments).

Turn in your work on this assignment before 3 pm on the due
date by sending electronic mail to

    will@ccs.neu.edu

with subject

    CSU370 assignment 3

and a body that consists of nothing but your TestIssue.java
file.  That file should begin with a block comment that lists

    1.  Your name, as you want the instructor to write it.
    2.  Your email address.
    3.  Any remarks that you wish to make to the instructor.

Late assignments may be discounted, and very late assignments
may be discarded.

--------------------------------------------------

Your assignment is to write the code for a single file,
TestIssue.java, in the project package, that declares a
public class named TestIssue, that defines a public
static void main (String[]) method that, when called
with any array of strings as its argument, performs
black-box testing of the Issue ADT that was specifie
in assignment 2.

Your program shall report any failed tests by writing a
failure message to System.out.  When testing is concluded,
your program should write a message to System.out that reports
that all tests have been passed if that is true, or reports
the number of failed tests if that number is positive.

Your black-box test program is a client of the Issue ADT, so
it must work properly with any correct implementation of this
ADT.  It should also do a good job of detecting common errors
in incorrect implementations of this ADT.

--------------------------------------------------