Jump to: navigation, search

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

Line 1: Line 1:
 
== Summary ==
 
== Summary ==
 
The EclipseLink test suites are written using JUnit.  They consist of a set of jars and classes that contain various tests and resources. The tests are contained in the eclipselink.*.test projects.  This page is intended to outline the setup and execution steps required to successfully run the JUnit tests.  There are 2 ways to checkout EclipseLink and for each of these there are 2 ways to run tests.
 
The EclipseLink test suites are written using JUnit.  They consist of a set of jars and classes that contain various tests and resources. The tests are contained in the eclipselink.*.test projects.  This page is intended to outline the setup and execution steps required to successfully run the JUnit tests.  There are 2 ways to checkout EclipseLink and for each of these there are 2 ways to run tests.
# Checkout using [[http://subclipse.tigris.org/update_1.2.x | Subclipse]] all projects individually into your eclipse workspace
+
# Checkout using [http://subclipse.tigris.org/update_1.2.x Subclipse] all projects individually into your eclipse workspace
 
## Build classes in eclipse and run/debug there
 
## Build classes in eclipse and run/debug there
 
## Build/run classes using Ant
 
## Build/run classes using Ant
# Checkout using [[http://tortoisesvn.tigris.org | TortoiseSVN]] the root trunk into a folder outside your workspace ''(IE: c:/view_el)'' 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 - but you will requires some build.properties changes.
+
# Checkout using [http://tortoisesvn.tigris.org TortoiseSVN] the root trunk into a folder outside your workspace ''(IE: c:/view_el)'' 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 - but you will requires some build.properties changes.
 
## Build classes in eclipse and run/debug there
 
## Build classes in eclipse and run/debug there
 
## Build/run classes using Ant
 
## Build/run classes using Ant
  
 
===Prerequisites===
 
===Prerequisites===
* [[http://tortoisesvn.tigris.org | TortoiseSVN]] and a saved [[http://www.chiark.greenend.org.uk/~sgtatham/putty | PuTTY]] SSH session
+
* [http://tortoisesvn.tigris.org TortoiseSVN] and a saved [http://www.chiark.greenend.org.uk/~sgtatham/putty PuTTY] SSH session
 
* ''TortoiseSVN - network setting - SSH client'' set as '''<TortoiseSVN_HOME>\bin\TortoisePlink -l <userName> -pw <password_cleartext>'''
 
* ''TortoiseSVN - network setting - SSH client'' set as '''<TortoiseSVN_HOME>\bin\TortoisePlink -l <userName> -pw <password_cleartext>'''
 
[[Image:Explorer_right_click_svn_settings_menu.JPG|400px]]  
 
[[Image:Explorer_right_click_svn_settings_menu.JPG|400px]]  
Line 37: Line 37:
 
== How To ==
 
== How To ==
  
* [[EclipseLink/Test/Prereq| General prerequisites for building & running EclipseLink tests]]
+
* [[EclipseLink/Testing/Prereq| General prerequisites for building & running EclipseLink tests]]
 
* [[EclipseLink/Build/Antlr| Make changes to ANTLR generated JPA code]]
 
* [[EclipseLink/Build/Antlr| Make changes to ANTLR generated JPA code]]
* [[EclipseLink/Test/LRG| Run the legacy LRG]]
+
* [[EclipseLink/Testing/LRG| Run the legacy LRG]]
* [[EclipseLink/Test/JPA| Run the JPA Junit tests]]
+
* [[EclipseLink/Testing/JPA| Run the JPA Junit tests]]
 
* [[EclipseLink/Development/TestStatus/MOXy-Instructions| Run the MOXy Junit tests]]
 
* [[EclipseLink/Development/TestStatus/MOXy-Instructions| Run the MOXy Junit tests]]
 
* [[EclipseLink/Development/TestStatus/SDO-Instructions| Run the SDO Junit tests]]
 
* [[EclipseLink/Development/TestStatus/SDO-Instructions| Run the SDO Junit tests]]
  
 
[[Category:EclipseLink|Building]]
 
[[Category:EclipseLink|Building]]

Revision as of 12:02, 7 January 2008

Summary

The EclipseLink test suites are written using JUnit. They consist of a set of jars and classes that contain various tests and resources. The tests are contained in the eclipselink.*.test projects. This page is intended to outline the setup and execution steps required to successfully run the JUnit tests. There are 2 ways to checkout EclipseLink and for each of these there are 2 ways to run tests.

  1. Checkout using Subclipse all projects individually into your eclipse workspace
    1. Build classes in eclipse and run/debug there
    2. Build/run classes using Ant
  2. Checkout using TortoiseSVN the root trunk into a folder outside your workspace (IE: c:/view_el) 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 - but you will requires some build.properties changes.
    1. Build classes in eclipse and run/debug there
    2. Build/run classes using Ant

Prerequisites

  • TortoiseSVN and a saved PuTTY SSH session
  • TortoiseSVN - network setting - SSH client set as <TortoiseSVN_HOME>\bin\TortoisePlink -l <userName> -pw <password_cleartext>

Explorer right click svn settings menu.JPG

  • Eclipse 3.2|3.3|1.5 installed with the subclipse plug-in for in-eclipse checkouts
  • Referenced core projects eclipselink.core and eclipselink.lib checked out into workspace or view
  • Required projects for your specific view eclipselink.sdo|moxy|jpa|dbws, eclipselink.sdo|moxy|jpa|dbws.lib and eclipselink.sdo|moxy|jpa|dbws.test checked out into workspace or view
  • If using Ant instead of Eclipse to run - edit build.properties either at this project level or better - globally override the following in your user directory on windows: C:/Documents and Settings/<user-dir>/build.properties
javaee.lib=<jar_location>/javaee.jar - required by MOXy or core tests
junit.lib=<JUNIT_HOME>/junit.jar 
  • Override any project specific variables in your <user-dir>/build.properties depending on whether you are running inside an eclipse workspace or outside.

Classpath Variables

Ensure the following (Java | Build Path | Classpath Variables) are set:

  • ORACLE_JDBC_LIB variable has been mapped to your database's JDBC driver (compile-time for extension project)
  • JDBC_LIB variable has been mapped to your database's JDBC driver (vendor-agnostic driver)
  • Some JDBC drivers may require the system library path to be set, or dlls to be on the path
  • TOOLS_LIB variable has been mapped to your JDK tools.jar
  • The following jars may be placed into extension.oracle.lib.external
    • AQAPI_LIB variable has been mapped to your aqapi*.jar
    • SPATIAL_LIB variable has been mapped to sdoapi.jar
    • XDB_LIB variable has been mapped to xdb.jar
    • XML_LIB variable has been mapped to xml.jar
    • XMLPARSERV2_LIB variable has been mapped to the oracle specific xmlparserv2.jar

How To