ObdaDebuggingReport

Integration Test

The main purpose of this test is to check the correctness of the SQL queries porduced by a newer version of the quonto reasoner. It is executing a given conjuctive querie twice, one time with the old version and one time with the new version of the reasoner and finally it compares the number of returned tuples of the resulting SQL queries. If the number of tuples is the same the test is considered successfull otherwise it fails. The source code of the test is located in the int.unibz.it.quonto.owlapi.integrationtest project. The project can be downloaded/update from the usual SVN repository.

Setting up the Test

Step 1: Configure the Test The test is configured using a java properties file. The file has to contain 4 properties:

• reasoner1
• reasoern2
• owlfiles
• resultfiles

reasoner1 and reasoner2 should specify the path to the configuration file of the old respectively the new reasoner version of the quonto reasoner. owlfiles should specify the path to the owlfiles which should be used in the test. resultfiles specifies the path to a properties file, which contains already the number of tuples returned by the old reasoner. If the file exist the results listed in it are used for running the test, otherwise the file is created and the results obtained by using the old reasoner are stored in it so that it can be reused later. It is also possible to run several tests at once by specifing a list of owlfiles and resultfiles separeted by a semicolon. Note that for each owlfile one has to specify in a resultfile even though it does not exist yet.

Example:

Step 2: Creating an Eclipse Launch Configuration for the test

• Start your Eclipse installation and navigate to Run --> Run Configuration... This opens the Run Configuration Dialog of Eclipse
• Select JUnit in the left menu and crate a new lauch configuration.
• Select inf.unibz.it.quonto.owlapi.integrationtest as project and
• Select the class SQOTupleCountTest as Test Class

Step 3: Setting the Eclipse Environment Variables

• Select the Environment Tab in the Lauch Configuration Dialog
• Create a new Environment Variable configfile. It should contain the full path to the properties file created in Step 1.
• Create a new Environment Variable timeout. It should the contain the max time in seconds a query execution should take, once this limit is reached the execution is aborted.

Step 4: Lauch the test

• Press the Run button and the test will start.