Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/Testing/SDO"

(Building & Running the SDO Junit tests)
(Building & Running the SDO Junit tests)
Line 17: Line 17:
  
 
*'''Configuration options'''
 
*'''Configuration options'''
**customContext = true (run test using an thread-safe instantiable instance of SDOHelperContext) - default
+
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)
 
**customContext = false (run test using static HelperContext Singleton)
  

Revision as of 09:38, 25 October 2007

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.

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. 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.
  3. View results in the reports subdirectory
  • 2) Building & Running within a Subversion checkout
  1. Create your own view directory - for example "c:/myview/"
  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 extension jars, 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
  • 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

Back to the top