System Testing -- Current plan

[Andrew L Roth]

I'm currently planning on doing manual tests for the system tests. By
that I mean I will do as much beforehand as possible, but will manually
pick up and dial phones to perform the test, then manually use the GUI to
show that it passed or failed. We can have a script to clean out the db
and put in preset values.

Does that sound reasonable? Based on what clarifications we've been given
I think it is.

The reasons I think it is:

I have a difficult time imagining how the system tests will be done in
JUnit. All 5 system tests given in section 3.2 of the project description
document require both a client and server running.

A typical system test in JUnit would have to set up the database with the
correct clients and mappings, start the server, start the client, send the
appropriate offhook and digits pressed to the client (which requires
modifying the code JUnit can do this) then check the database to determine
pass or fail. I've left out many other details and issues that would have
to be considered.

There's an even bigger problem with tests that require multiple clients,
because we need one computer per client. This affects tests 3, 4 and 5.

-Andrew Roth