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.
Difference between revisions of "EclipseLink/Development/Testing/SDO"
< EclipseLink | Development | Testing
(→Running the SDO Junit tests) |
(→Running the SDO Junit tests) |
||
Line 8: | Line 8: | ||
== Running the SDO Junit tests== | == Running the SDO Junit tests== | ||
− | * '''Running within an Eclipse Workspace | + | * '''Running within an Eclipse Workspace subclipse checkout |
Prerequisites: | Prerequisites: | ||
# Eclipse installed with the subclipse pluggin | # Eclipse installed with the subclipse pluggin | ||
# Required projects eclipselink.core and eclipselink.lib checked out into workspace | # Required projects eclipselink.core and eclipselink.lib checked out into workspace | ||
# eclipselink.sdo, eclipselink.sdo.lib and eclipselink.sdo.test checked out into workspace | # eclipselink.sdo, eclipselink.sdo.lib and eclipselink.sdo.test checked out into workspace | ||
+ | # Edit build.properties either at this project level or globally in your user directory.. | ||
+ | Windows: C:\Documents and Settings\<user-dir> | ||
+ | Linux: | ||
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 18: | Line 21: | ||
# Navigate to the <workspace>/eclipselink.sdo.test directory | # 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. | # Run the sdo.test/build.xml by typing "ant". This will compile in order eclipselink.core, eclipselink.sdo and eclipselink.sdo.test. | ||
− | # View results in the reports subdirectory | + | # View results in the reports subdirectory for either customContext = true|false |
− | * '''Running within a Subversion | + | * '''Running within a Subversion checkout |
Prerequisites: | Prerequisites: | ||
# Eclipse installed with subversion for out-of-workspace projects | # Eclipse installed with subversion for out-of-workspace projects |
Revision as of 09:45, 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 the SDO Junit tests
20071023
Running the SDO Junit tests
- Running within an Eclipse Workspace subclipse checkout
Prerequisites:
- Eclipse installed with the subclipse pluggin
- Required projects eclipselink.core and eclipselink.lib checked out into workspace
- eclipselink.sdo, eclipselink.sdo.lib and eclipselink.sdo.test checked out into workspace
- Edit build.properties either at this project level or globally in your user directory..
Windows: C:\Documents and Settings\<user-dir> Linux:
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
- 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.
- View results in the reports subdirectory for either customContext = true|false
- Running within a Subversion checkout
Prerequisites:
- Eclipse installed with subversion for out-of-workspace projects
- Required projects eclipselink.core and eclipselink.lib checked out into workspace
- eclipselink.sdo, eclipselink.sdo.lib and eclipselink.sdo.test checked out into workspace
- Create your own view directory - for example "c:/myview/"
- Check out the SVN project for SDO into this directory
- Navigate to the eclipselink.sdo.test directory
- Run sdo.test/build.xml by typing "ant"
- View results in the reports subdirectory