Still no luck. I’ve also tested with Eclipse 3.5.1 and it doesn’t work there either. I just left a comment on the Bugzilla entry to see if there’s anything we can do to get this working.

https://bugs.eclipse.org/181508

If you’re really interested in this, you may want to comment on the Bugzilla entry too.

— Patrick

The collector is pretty simple and could easily be extended to organize tests in different ways. There are no output options right now, though.

To run tests in the IDE, you can just run the test suite that extends the bundle test collector. The tests should run normally in the IDE, but make sure you choose Run As -> JUnit Plug-in Test.

I’ve haven’t been able to run any fragment based tests under the ETF either, at least under 3.4. The fragment doesn’t get activated along with the bundle. Haven’t tried it on 3.5 yet. What version are you using?

— Patrick

2 questions:

After creating an AllTests class that extends BundleTestCollector (like shown in the example provided in the zip archive) I cant get it to run as part of my build through ETF but all the tests are shown in a flat list. Can I provide a heirarchy so it is easier to see which tests belong to which package/class?

How can I run directly from the Eclipse IDE?

I still run on the junit4 problem with etf. I checked out etf from cvs. Then I exported the etf feature and it seemed to be valid. Of course before I removed every dependency to org.junit and added org.junit4.
But if i run the test target in build.xml I get the message:
…
core-test:
java-test:
[echo] Running com.rcpquickstart.helloworld.test.collector.AllTests. Result file: E:\WS_AutomatedBuildExample\com.rcpquickstart.helloworld.build-and-test/buildDirectory/test/eclipse/results/com.rcpquickstart.helloworld.test.collector.AllTests.xml.
[java] Java Result: 13
collect-results:
[junitreport] the file E:\WS_AutomatedBuildExample\com.rcpquickstart.helloworld.build-and-test\buildDirectory\test\eclipse\com.rcpquickstart.helloworld.test.collector.AllTests.xml is empty.
[junitreport] This can be caused by the test JVM exiting unexpectedly
[style] Warning: the task name is deprecated. Use instead.
[style] Transforming into E:\WS_AutomatedBuildExample\com.rcpquickstart.helloworld.build-and-test\buildDirectory\test\eclipse\results
collect:
[junitreport] the file E:\WS_AutomatedBuildExample\com.rcpquickstart.helloworld.build-and-test\buildDirectory\test\eclipse\com.rcpquickstart.helloworld.test.collector.AllTests.xml is empty.
[junitreport] This can be caused by the test JVM exiting unexpectedly
…

Even with debugging I couldn’t find out, what exactly the problem is. Maybe since there is no actual build instruction for etf, can you explain more precisely how you made it.

I would appreciate the help.

Martin

no, its surprisingly easy to get this etf running on junit4, just replace all the references in the etf to org.junit with org.junit4. You don´t have to change anything within the SDK (why would you anyway?)

Johannes

I just would like to give a pointer to an alternative test framework to ETF which is called Autotestsuite and is part of Pluginbuilder.

The Autotestsuite collects both JUnit3 and
JUnit4 Test Cases and creates a test suite automatically. JUnit 3
tests are determined by hierarchy (subclasses of TestCase) whereas
JUnit 4 tests are determined by annotations.

The advantage of the autotestsuite is that you neither need to create
All* suites nor add any XML configuration. Every (except ignored JUnit
4) test will be executed without additional tedious configuration. If
you really want to exclude tests, you can do so with regular
expressions. The regular expressions also provide an easy way to
create conventions for your projects, e.g. *UITest* to execute all UI
specific tests.

That’s great, but can you be more specific? Do you mean you removed the org.junit plug-in from the test environment and removed all references to it in other Eclipse SDK plug-ins? I’d love to have a detailed solution to this problem, and I’d be interested to hear what you did.

— Patrick