Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 344285

Summary: Update /org.eclipse.test/testframework.html to support local runs
Product: [Eclipse Project] Platform Reporter: Markus Keller <markus.kell.r>
Component: RelengAssignee: Platform-Releng-Inbox <platform-releng-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: david_williams
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Markus Keller CLA 2011-04-29 10:27:05 EDT
Once upon a time, the ETF was supposed to allow running tests locally via an Ant task. But the instructions in /org.eclipse.test/testframework.html under "Running the Test Suite from the UI" don't really work in HEAD.

When I try to run e.g. performance-suite from /org.eclipse.jdt.text.tests/test.xml, I run into a bunch of issues:

* testframework.html is unclear about how I have to install the 2 plug-ins. When I look at /org.eclipse.test/library.xml, I see references to various conflicting locations:
- JaCoCo refers to ${basedir}/plugins/org.eclipse.test_${org.eclipse.test}/lib/jacocoagent.jar
- junit-stylesheet refers to ${eclipse-home}/dropins/eclipse/plugins/org.eclipse.test/JUNIT.XSL
- testframework.html refers to <property name="library-file" value="${eclipse-home}/fragments/org.eclipse.test/library.xml"/>, but the example contains 	<property name="library-file"
            value="${eclipse-home}/plugins/org.eclipse.test/library.xml"/>

* The recommended default
<property name="eclipse-home" value="${basedir}\..\.."/> 
looks strange. If the Ant script is run locally (in the same JRE as the workspace), then the "eclipse.home" property is pre-defined (note the '.' instead of the '-'). Looks like that's the one that should be used.



I tried to run the test framework locally, but I failed
Comment 1 David Williams CLA 2013-04-29 18:48:58 EDT
I'm not sure the performance tests will currently run. If that's the purpose of this bug please reopen as its own bug and change title ... otherwise, will count as a dup of 406646.

*** This bug has been marked as a duplicate of bug 406646 ***