The JAXR workspace is available on the jeeves.sfbay server. You need to
check out the jaxr-test module to get the test workspace1.
Alternately, you could get a tar-ball from here.2
Note: In the following discussion, ${jaxr.test.home} denotes the directory where you installed the JAXR Test Workspace and ${j2ee.home} is your J2EE installation root.
The workspace uses ant to run the tests. You have the flexibility to run all the tests in the workspace or a subset. The tests are organized in a tree structure, and running ant at any node in the tree will run all the tests from that node down.
To run all the tests in the workspace go to the ${jaxr.test.home}/test/jaxr directory and type ant at the prompt [As mentioned in the following paragraph, you can also set command line properties here to over-ride the default settings.]
At the end of a test-run, the logs are generated in a time-stamped directory under ${jaxr.test.home}/logs. The directory structure for the generated logs directory looks similar to the one shown below:
${jaxr.test.home}/logs
|___20030520
|_____jwsdp-ms-SunOS-5.9-jdk1.4
|_____<log files>
The tests use Reporter to produce XML result files. To generate HTML reports from these, type ant generateHTMLReport at the prompt. This will produce an html report (result.html) in the same directory as the log files. [Note: If you override either test.env or test.env.registry on the command line, when you run the tests, you need to make sure you do the same when generating the HTML report. This is because these values are used in computing the log directory and ant would not remember the settings from one run to the other]
As a general rule, all user-modifications for running the JAXR tests should be done only in ${jaxr.test.home}/config/jaxr-commons.xml (It has a section at the top which indicates the modifiable properties) All these properties have default values in the files. To override these, the recommended way is to specify the appropriate values on the command line when invoking ant (E.g. ant -Dtest.env.registry=private to run the tests against the UDDI registry-server) [ Note: Unless, of course, you want to change the default itself, in which case you should modify these properties in the jaxr-commons.xml file and these would become your default settings ]
Here are some important properties and their default settings (For detailed documentation, please
browse the jaxr-commons.xml file )
1.) test.env.registry : private (for running against the
UDDI registry-server. Setting up the registry-server is not done by the scripts.
This needs to be done separately)
[Note: Running the private registry on SunOne is not supported due to a
known issue. If you wish to test the jaxr tests in a SunOne environment against
the private registry, please start the private registry bundled with JWSDP, and
point to it in the registry properties file]
2.) test.env : Default - jwsdp. Acceptable values:
jwsdp : For running the tests on the Java Web Services Developer Pack
jaxpack : For running the tests on the Java and XML Pack
s1as: For running the tests on the SunOne App Server 7.0 Personal Edition (Evaluation copy). Before running the tests, the JWSDP libraries must be integrated with SunOne by running the jwsdponsunone scripts bundled with the JWSDP.
s1as8: For running the tests on the SunOne App Server 8.0 Technology Preview edition (The JWSDP libraries are already bundled with S1AS 8.0, so you do not need to run the integration scripts.)
3.) test.env.vmargs : Default - "" (empty string) Acceptable values:
anything that you would like to pass to the JVM running the test.
In addition to the above, there is a one-time configuration that you need to do in the jaxr-commons.xml file. In the top portion of the file, there are pointers to your jwsdp, j2ee,
s1as (for S1AS 7.0) ,s1as8 (for S1AS 8.0) and jaxpack installations. You need to make sure these are pointed to the correct locations.
(You need to set the pointers only for the environments you would be using. The
rest would be ignored. E.g, if you are running the tests on s1as8, you do not
need to worry about the installation directories for jwsdp. Also, if you plan to
run only on unix, you do not need to worry about setting the windows
installation directory.)
The registry settings, that the tests use, are configured in registry property files under ${jaxr.test.home}/config/registry-properties. Please modify these settings as appropriate for your installation. (These primarily contain the connection properties required for setting up a JAXR connection)
The UML design document for the Service Portal Test Suite can be found here (For a PDF version of this StarOffice document, please click here )
Additionally, there are some tests (e.g regression tests) that are not included in the Service Portal. However, all the tests are completely documented. For an explanation of what these tests do, please browse the source code documentation.
Note: Some of the features listed in the ServicePortal (e.g FederatedQueries ) are not yet supported. These features will be exercised as they are available in the RI.
Date | Tag | Comments |
---|---|---|
April 29, 2002 | iPlanet-1 | First drop to iPlanet |
June 28, 2002 | iPlanet-2 | JWSDP FCS drop to iPlanet |
Notes:
1. You will need to have an account in the sfbay domain, since AFAIK, this CVS server is not configured for anonymous logins.
2. The tar-ball is not regularly updated. It is current as of June 28, 2002
For any questions, please contact us at jaxr-sqe@sun.com