next up previous
Next: Functionality testing Up: Test procedure Previous: Unit testing

Installation testing

Installation tests will check the installation and configuration procedure as well as any missing dependencies. These tests are a set of scripts that automatically download all necessary packages and install them.

To test that the installation was succesful there is a edg-java-security-test RPM, which cointains two simple scripts to test the ssl handshake with the secure service and the use of a basic authorization policy.

To use both of them you should first get your proxy certificate, either generated by edg-voms-proxy-init or by normal grid-proxy-init.

The first script is called edg-java-security-tomcat-test.sh and takes two arguments: the server name and the port number. A simple example would be
$EDG_LOCATION/sbin/edg-java-security-tomcat-test.sh localhost 8443.

The second script is called edg-java-security-authz-test.sh. Before running this script you must create a link to the authorization test web application:

ln -s \$EDG\_LOCATION/share/webapps/edg-java-security-authz-test.war 
\$CATALINA\_HOME/webapps-secure/edg-java-security-authz-test.war
The script may take two optional arguments: the role and the policy requested by the client. By default the client running the script is authorized if it is mapped in the grid-mapfile or it is using a voms-proxy-certificate. A simple example would be $EDG_LOCATION/sbin/edg-java-security-authz-test.sh -role myRole -policy myPolicy.


next up previous
Next: Functionality testing Up: Test procedure Previous: Unit testing
2004-05-05