apache-tuscany

History

slaws 9b875446ce Add profile for the policy tests git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@834089 13f79535-47bb-0310-9956-ffa450edef68		2009-11-09 14:53:43 +00:00
..
tuscany-java-caa-test-runner	Try out moving the otests out of 2.x trunk by copying the tuscany/sca/java/otest folder to tuscany/otest. - A copy not a move so the old one can continued to be used. Can worry about the name tuscany/otest later	2009-11-02 09:59:23 +00:00
tuscany-java-ci-test-runner	Sort and clean the error messages file	2009-11-06 15:24:23 +00:00
tuscany-policy-test-runner	add policy test runner	2009-11-09 14:51:12 +00:00
tuscany-test-runner	Update error message for ASM_6016	2009-11-09 11:00:27 +00:00
build.xml	Try out moving the otests out of 2.x trunk by copying the tuscany/sca/java/otest folder to tuscany/otest. - A copy not a move so the old one can continued to be used. Can worry about the name tuscany/otest later	2009-11-02 09:59:23 +00:00
pom.xml	Add profile for the policy tests	2009-11-09 14:53:43 +00:00
README	Try out moving the otests out of 2.x trunk by copying the tuscany/sca/java/otest folder to tuscany/otest. - A copy not a move so the old one can continued to be used. Can worry about the name tuscany/otest later	2009-11-02 09:59:23 +00:00

README

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

To get the OASIS compliance tests from SVN:

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

To run the tests:

cd otest/newlayout
mvn

should build and run all of the Assembly spec otests

mvn -Pscajcaa

should build and run all of the SCA-J CAA spec otests

The file otest\newlayout\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/newlayout
mvn eclipse:eclipse

import otest/newlayout/tuscany-test-runner into eclipse
import otest/newlayout/sca-assembly/General into eclipse
import otest/newlayout/sca-assembly/General_Java into eclipse

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

mvn -Pscajcaa eclipse:eclipse

import otest/newlayout/tuscany-java-caa-test-runner into eclipse
import otest/newlayout/sca-java-caa 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
    tuscany-test-runner           - the tuscany specific code + code copied from sca-assembly/Test_Client
    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
    tuscany-java-caa-test-runner  - the tuscany specific code + code for running the SCA-J CAA 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.