EclipseLink/Development/Testing/SDO

Summary

This page is intended to outline the setup and execution steps required to successfully run the SDO JUnit tests. There are 2 ways to develop using EclipseLink.

1. Checkout using subclipse all projects individually into your eclipse workspace and develop/debug there by using eclipse to build classes.
2. Checkout using tortoiseSVN the root trunk into a folder outside your workspace and either use ant to build an eclipselink.jar or create proxy projects using link to source from eclipse - Recommended if you would like to build the eclipselink.jar

Building & Running the SDO Junit tests

Prerequisites:

1. Eclipse installed with the subclipse pluggin or TortoiseSVN for out of eclipse checkouts
2. Required projects eclipselink.core and eclipselink.lib checked out into workspace/view
3. eclipselink.sdo, eclipselink.sdo.lib and eclipselink.sdo.test checked out into workspace/view
4. Edit build.properties either at this project level or globally in your user directory.

• Windows: C:\Documents and Settings\<user-dir> Linux:
  • javaee.lib=<jar_location>/javaee.jar
  • junit.lib=<JUNIT_HOME>/junit.jar
  • tools.lib=<JAVA_HOME/lib/tools.jar

• Configuration options
• The tests run with a non-static customContext which is the mode that will normally be used in a multithreaded container.
  • customContext = true (run test using an thread-safe instantiable instance of SDOHelperContext) - default
  • customContext = false (run test using static HelperContext Singleton)

• 1) Building & Running within an Eclipse Workspace via subclipse checkout

The SDO test suite is written using JUnit. It consists of a set of jars that contain various tests and resources. The SDO tests are contained in the eclipselink.sdo.test project

1. Running using Ant
   1. Navigate to the <workspace>/eclipselink.sdo.test directory
   2. Run the sdo.test/build.xml by typing "ant". This will compile in order eclipselink.core, eclipselink.sdo and eclipselink.sdo.test.

1. Running using Eclipse
   1. Setting up Eclipse
      1. Create 5 of 11 new projects (core,core.lib,sdo,sdo.lib,sdo.test) using SVN (turn off automatic build temporarily)

1. View results in the reports subdirectory

• 2) Building & Running within a Subversion checkout

1. Create your own view directory - for example "c:/view_el/"
2. Check out the SVN project for SDO into this directory using the format svn+ssh://<username>@<svn_session>/svnroot/technology/org.eclipse.persistence/trunk
3. Either build all 4 core, jpa, moxy and sdo projects into an eclipselink.jar by following the instructions in Building EclipseLink Source - specifically the section on setting up the extension jars not included in eclipselink.core.lib, or allow the sdo test script to run off classes by doing the following...
4. Navigate to the eclipselink.sdo.test directory
5. Run sdo.test/build.xml by typing "ant"
6. View results in the reports subdirectory under true|false

1. Setting up Eclipse
   1. Create 5 of 11 new projects (core,core.lib,sdo,sdo.lib,sdo.test) from existing source = "c:/view_el/eclipselink.* (turn off automatic build temporarily)

1. 1. At this point you should get 2 errors if the TOOLS_LIB variable is not set for sdo.test. Set this variable globally using Window | Preferences | Java | Build Path | Classpath Variables - new -> name=TOOLS_LIB, path==<JAVA_HOME/lib/tools.jar
2. Running a suite
   1. Pick a suite - we will use org.eclipse.persistence.testing.helper.pluggable,PluggableTestSuite as it is small and utilizes resources as well as core xsd/xml define/load functions.
   2. Create a new java application run/debug target
   3. Modify the arguments tab|working directory to point to ${workspace_loc:eclipselink.sdo.test/resource} or create a resource variable to reuse in other targets - this is where all tests will execute.
   4. Run the test and observe results in the Console

• Interpreting Test Results
  • See the test results page at []
  • Depending on the value of the customContext variable look under the true|false subdirectory in junit-noframes.html