blob: 6a1966535806fae1490b777d52c3e57234a14928 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
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.
|
