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.
Difference between revisions of "EclipseLink/Development/Testing/Prereq"
< EclipseLink | Development | Testing
(New page: == 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 eclip...) |
(→Prerequisites) |
||
| Line 18: | Line 18: | ||
<blockquote style="background: grey; border: 1px solid rgb(153, 153, 153); padding: 1em;"><pre><nowiki> | <blockquote style="background: grey; border: 1px solid rgb(153, 153, 153); padding: 1em;"><pre><nowiki> | ||
javaee.lib=<jar_location>/javaee.jar - required by MOXy or core tests | javaee.lib=<jar_location>/javaee.jar - required by MOXy or core tests | ||
| − | junit.lib=<JUNIT_HOME>/junit.jar | + | junit.lib=<JUNIT_HOME>/junit.jar |
</nowiki></pre></blockquote> | </nowiki></pre></blockquote> | ||
*Override any project specific variables in your ''<user-dir>/build.properties'' depending on whether you are running inside an eclipse workspace or outside. | *Override any project specific variables in your ''<user-dir>/build.properties'' depending on whether you are running inside an eclipse workspace or outside. | ||
Revision as of 11:22, 12 December 2007
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.
- Checkout using [| Subclipse] all projects individually into your eclipse workspace
- Build classes in eclipse and run/debug there
- Build/run classes using Ant
- 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.
- Build classes in eclipse and run/debug there
- 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>
- 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.