I wasn’t thinking when trying the fix. I was only using the newer eclipse test framework zip. I would also need to move to the newer SDK in order to get this to work (but I can’t move up, for other reasons).

I have not tried this myself – haven’t had the time yet. If it’s not working for you it would probably be best to ask questions on the Bugzilla entry. I’m definitely interested to hear if you get this working or not, so please keep me posted.

— Patrick

This was *finally* fixed just last week and will be available in Eclipse 3.6. Check out the Bugzilla entry for all the gory details.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=153429

— Patrick

Is it possible to run the tests with Junit 4?
I’ve only been able to run Junit 3 and keep getting a “junit.framework.AssertionFailedError: No tests found…” type of error as soon as I switch to Junit 4.
Is there a trick to get the test running with Junit 4?

Thanks

I used your example and found it very useful. Using eclipse 3.5, managed to build the feature in the example.

Build is successful, but no executable file exists in the archive. Could you please tell me what the problem might be?

Regards,
Marius

Reik

I don’t see any problem specifying an application id instead of a product id. The product is really just adding some branding, so from a unit testing perspective you should be ok.

— Patrick

sorry, in your original sources this parameter is indeed not specified. I have introduced it myself because I performed a ui-test and needed the helloworld application to start. My question is, is this a correct product test? I would have assumed to specifiy a product instead of an application.

Reik