Running the otests with Tuscany using Maven
===========================================

To get the OASIS compliance tests from SVN:

svn co https://svn.apache.org/repos/asf/tuscany/otest/newlayout/ otest

To run the tests:

cd otest
mvn

should build and run all of the spec otests

To run specific spec otests, the following profiles are available 

assembly : Run all Assembly spec otests
javacaa  : Run all SCA-J CAA spec otests
javaci   : Run all SCA-J CI spec otests
policy   : Run all Policy spec otests

To run a specific profile, use:

mvn -P<profile name>
mvn -Passembly

should build and run all of the Assembly spec otests

The file tuscany-test-runner\src\test\resources\oasis-sca-tests.properties configures the 
test environment. Currently you can run in either the Java standalone or OSGi runtimes
which is configured by the org.oasis.sca.tests.assembly.runtime_bridge property.

Running the otests with Tuscany using Eclipse
=============================================

For the Assembly tests:

cd otest
mvn eclipse:eclipse

import tuscany-test-runner into eclipse (tuscany-otests-asm-tests)
import sca-assembly/General into eclipse (General)
import sca-assembly/General_Java into eclipse (General_Java)

import which ever other contributions you need into eclipse (depends on which tests you are running)
  
For the SCA-J CAA tests:

mvn -Pjavacaa eclipse:eclipse

import tuscany-java-caa-test-runner into eclipse
import sca-java-caa into eclipse

For the SCA-J CI tests:

mvn -Pjavaci eclipse:eclipse

import tuscany-java-ci-test-runner into eclipse
import sca-java-ci into eclipse

For the Policy tests:

mvn -Ppolicy eclipse:eclipse

import tuscany-policy-test-runner into eclipse
import sca-java-policy into eclipse


Structure of the otests
======================

The otest directory, once checked out, contains files from both OASIS and Tuscany svn. As follows

otest/
  newlayout/                        - the latest otests
    sca-assembly/                   - the Assembly otest source pulled directly from OASIS svn via svn:externals
    sca-java-caa/                   - the SCA-J CAA otest source pulled directly from OASIS svn via svn:externals
    sca-java-ci/                    - the SCA-J CI otest source pulled directly from OASIS svn via svn:externals
    sca-java-policy/                - the SCA-J Policy otest source pulled directly from OASIS svn via svn:externals
    tuscany-test-runner             - the tuscany specific code + code copied from sca-assembly/Test_Client
    tuscany-java-caa-test-runner    - the tuscany specific code + code for running the SCA-J CAA tests
    tuscany-java-ci-test-runner     - the tuscany specific code + code for running the SCA-J CI tests
    tuscany-java-policy-test-runner - the tuscany specific code + code for running the SCA-J CI tests

The Junit test cases are copied, using an ant script called by maven, from sca-assembly/Test_Client
into tuscany-test-runner so that we can overlay them with Tuscany specific bridges and property
files. In particular the Tuscany version of the test property files can be found at

tuscany-test-runner/src/test/resources/  
 
Maven puts this on the classpath before 

tuscany-test-runner/src/main/resources

Which is where the otest versions get copied to and hence the Tuscany ones get picked up.