There are a number of scripts to run to test a deployment of the cipres REST API.  They're meant 
to be run from the same machine that you build and deploy on.    

- Build and deploy the rest api and then run testAndDemoAccounts (a script that's installed
when you build and deploy).  You'll need to supply the username and password of a REST Admin user.  
One way to get this info is from the build properties admin.username and admin.password.  (You could
also look in the database to find an admin user).

- The first set of test scripts is in the source code directory: scigap/rest/cipresrest.  Cd to this
directory to run them.  You'll need to supply the REST admin username and password on the command line.
You can run the majority of these tests in one shot by running:

$ sh alltests.sh USERNAME PASSWORD > out.txt

At the end of the output there should be a line saying how many tests passed and how many failed.  If any failed
you'll need to look through the output to see which ones they are, then look at the script for that test to 
figure out what went wrong.   If alot is going wrong, I'd recommend running the scripts individually instead
of using alltests.sh.  Just look at alltests.sh to see which individual scripts it calls and run them solo, 
for example:

$ sh user.sh USERNAME PASSWORD > out.txt

- Background info: 

* You'll notice that the scripts all begin by source'ing "testfw.sh", which is a bit of code that
reads configuration information from $SDK_VERSIONS/testdata/pycipres.conf, a file that was created 
automatically during the build.

* when setting up a new database for use with a REST API installation you should 
pick a username and password for a Cipres admin user and set the build propertyes admin.username and
admin.password accordingly, then do the build.  Next, run the script "cipresAdmin" and pass it the same username
and passrword inorder to create the admin user record in the database.  Then run the script "testAndDemoAccounts"
to create or update a few other database records that will be needed to run these tests and demos.  
Among other things testAndDemoAccounts registers a client application named "pycipres". Collectively
these test and demo scripts are the "pycipres application". TestAndDemoAccounts also writes the APPID 
for pycipres to $SDK_VERSIONS/testdata/pycipres.conf.  You can safely run testAndDemoAccounts multiple times.  
In fact, I think you may need to run it after each build, before running tests, to populate the 
APPID field in pycipres.conf.

- The second set of tests are what we call "tool tests".  They're for testing the cipres tools, like mrbayes, raxml,
etc, whereas the first group of tests are for testing more generic aspects of the rest api.  The tool tests
are in scigap/cipres-config/tests.   The simplest way to run these tests is from the same machine
where you built the REST API.  There's a Readme.txt file in the tests dir explaining what to do.  A couple of things
to note:

1. Running the tests with the "validate" argument should go pretty quickly but running with the "run" argument
can take quite awhile since it will be submitting many jobs and waiting for them to be scheduled and executed.
Most of the time I just use the validate argument.

2. The tooltests *can* be run from a different machine and will use pycipres.conf in your home dir.