RunOntopTestOnServer

Table of Contents Run onTop Tests On Server Step 1: Check out a clean copy of the onTop project from the repository Step 2: Run the script Step 3: Check the reports Troubleshooting

Run onTop Tests On Server

Step 1: Check out a clean copy of the onTop project from the repository

You may also just update the existing copy to the most recent revision.

Step 2: Run the script

Run the test-ALL script in /build directory. However, before you run the script make sure several things:

1. Log in as root user.

2. Set the environment variables for testing.

• Set ONTOP_BUILD_PATH that points the location of the check-out folder.

   root#: export ONTOP_BUILD_PATH=/build/ontop-build-2472

• Set `ONTOP_REPORT_PATH that points the location for publishing the report files for public viewing.

   root#: export ONTOP_REPORT_PATH=/var/lib/tomcat7/webapps/ontop-test-result

3. All the database servers are running

• The location for MySQL, PostgreSQL and DB2 is in obdalin3 server (IP: 10.7.20.39)

 root#: service mysql.server start
 root#: service postgresql start
 root#: su - db2inst1
 #: db2start

• The location for SQL Server and Oracle is in obdawin server (IP: 10.7.20.91). Use the GUI interface to start/stop the database services. (Note: the SQLServer test cases use the server instance named "MSSQLSERVER" (SQL Server 2012) instead of "KASIMIR" (SQL Server 2008)).

Run this command to create the reports. This call will run all the tests, create the reports and upload the report files to the server.

root@/build#: ./test-ALL.sh

In addition, you can run the test individually based on the project packages.

root@/build#: ./obdalib-core-test.sh
root@/build#: ./quest-owlapi3-test.sh
root@/build#: ./quest-rdb2rdf-compliance-test.sh
root@/build#: ./quest-sesame-test
root@/build#: ./quest-sparql-compliance-test.sh
root@/build#: ./reformulaton-core-test.sh

Step 3: Check the reports

Go to http://10.7.20.39:8080/ontop-test-result/ to see the generated reports.

Troubleshooting

If the test run doesn't seem to recognize you changes, run mvn install -DskipTests to re-install the package to Maven repository.