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"

(Running the SDO Junit tests)
(Running the SDO Junit tests)
Line 2: Line 2:
 
This page is intended to outline the setup and execution steps required to successfully run the SDO JUnit tests - It is currently undergoing the first draft as of 20071019.
 
This page is intended to outline the setup and execution steps required to successfully run the SDO JUnit tests - It is currently undergoing the first draft as of 20071019.
  
== Building the SDO Junit tests==
+
== Building & Running the SDO Junit tests==
 
+
20071023
+
 
+
== Running the SDO Junit tests==
+
  
 
Prerequisites:
 
Prerequisites:
Line 13: Line 9:
 
# eclipselink.sdo, eclipselink.sdo.lib and eclipselink.sdo.test 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..
 
# Edit build.properties either at this project level or globally in your user directory..
Windows: C:\Documents and Settings\<user-dir>
+
*Windows: C:\Documents and Settings\<user-dir>
Linux:
+
*Linux:
 +
**javaee.lib=<jar_location>/javaee.jar
 +
**junit.lib=<JUNIT_HOME>/junit.jar
 +
**tools.lib=<JAVA_HOME/lib/tools.jar
 +
 
  
* '''Running within an Eclipse Workspace subclipse checkout
+
* '''Building & Running within an Eclipse Workspace 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
 
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
Line 24: Line 24:
 
# View results in the reports subdirectory for either customContext = true|false
 
# View results in the reports subdirectory for either customContext = true|false
  
* '''Running within a Subversion checkout
+
* '''Building & Running within a Subversion checkout
  
 
# Create your own view directory - for example "c:/myview/"
 
# Create your own view directory - for example "c:/myview/"

Revision as of 09:54, 24 October 2007

Summary

This page is intended to outline the setup and execution steps required to successfully run the SDO JUnit tests - It is currently undergoing the first draft as of 20071019.

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


  • Building & Running within an Eclipse Workspace 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 for either customContext = true|false
  • 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
  3. Navigate to the eclipselink.sdo.test directory
  4. Run sdo.test/build.xml by typing "ant"
  5. View results in the reports subdirectory

Back to the top