Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Development/Testing/SDO
< EclipseLink | Development | Testing
Revision as of 10:14, 25 October 2007 by Unnamed Poltroon (Talk) (→Building & Running the SDO Junit tests)
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.
- Checkout using subclipse all projects individually into your eclipse workspace and develop/debug there by using eclipse to build classes.
- 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:
- Eclipse installed with the subclipse pluggin or TortoiseSVN for out of eclipse checkouts
- Required projects eclipselink.core and eclipselink.lib checked out into workspace/view
- eclipselink.sdo, eclipselink.sdo.lib and eclipselink.sdo.test checked out into workspace/view
- 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
- Running using Ant
- Navigate to the <workspace>/eclipselink.sdo.test directory
- Run the sdo.test/build.xml by typing "ant". This will compile in order eclipselink.core, eclipselink.sdo and eclipselink.sdo.test.
- Running using Eclipse
- Setting up Eclipse
- Create 7 of 11 new projects using SVN (turn off automatic build temporarily)
- eclipselink.core
- eclipselink.core.lib
- eclipselink.moxy
- eclipselink.moxy.lib
- eclipselink.sdo
- eclipselink.sdo.lib
- eclipselink.sdo.test
- Create 7 of 11 new projects using SVN (turn off automatic build temporarily)
- Setting up Eclipse
- View results in the reports subdirectory
- 2) Building & Running within a Subversion checkout
- Create your own view directory - for example "c:/view_el/"
- Check out the SVN project for SDO into this directory using the format svn+ssh://<username>@<svn_session>/svnroot/technology/org.eclipse.persistence/trunk
- 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...
- Navigate to the eclipselink.sdo.test directory
- Run sdo.test/build.xml by typing "ant"
- View results in the reports subdirectory under
- Setting up Eclipse
- Create 7 of 11 new projects from existing source = "c:/view_el/eclipselink.* (turn off automatic build temporarily)
- eclipselink.core
- eclipselink.core.lib
- eclipselink.moxy
- eclipselink.moxy.lib
- eclipselink.sdo
- eclipselink.sdo.lib
- eclipselink.sdo.test
- 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
- Create 7 of 11 new projects from existing source = "c:/view_el/eclipselink.* (turn off automatic build temporarily)
- 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