Thank you very much, and sorry for not replying earlier.
It was a great help. That’s solved my problem.

Stefanko

To get access to a resource inside of your bundle, it’s best to do something like:

Bundle bundle = Platform.getBundle(“com.mybundle.id”);
URL url = bundle.getEntry(“path-to-resource”);

The getEntry method takes a path relative to the root of your bundle. In your case this would be “res/TestData.txt”.

Hope this helps,

— Patrick

Thank you for your quick reply again and excuse my disturbing you again. So I am using your sample for my Headless build process, but some part of the Eclipse Testing Framework side wasn’t clear . Now I understand it, thank you very much.

For example I have a JUnit test where I use a data file from a ‘res’ folder under the plug-ins root folder and I reference to it the following way:
new File(“res/TestData.txt”)
If I run this test from the IDE it works fine, but when I execute it from the headless build the path cannot be resolved.

I receive the following message:
error message=”Source ‘res\TestData.txt’ does not exist” type=”java.io.FileNotFoundException”

So do you have any suggestion how to reference plug-in relatively to this data file?

Thanks in advance.

Stefanko

The Eclipse Testing Framework is specifically meant to run like ‘JUnit Plug-in Test’ in the IDE. It basically runs your unit tests inside of an OSGi framework. Again, setting this up is complex and I would refer you to the sample projects that can be downloaded here. The tests that run as part of the sample are running as plug-in tests, and you should be able to modify the sample to build and test your own plug-ins.

As far as relative file paths are concerned, what are they relative to? Or maybe a better way to approach this is to tell me what you’re trying to achieve with the paths. There are various OSGi and RCP API calls to manage storage locations depending on what you’re trying to do.

— Patrick

Thank you for your quick reply. My question wasn’t enough clear, sorry for it.

I can run my tests from headless build but only as JUnit Tests, but not as JUnit Plug-in Tests. In the Eclipse IDE if I right click on test file there are two options in the ‘Run As’ popup menu:
1. JUnit Test
2. JUnit Plug-in Test

So my question is how to execute my test as a ‘JUnit Plug-in Test’ from headless build?

Another problem is that I have some plug-in relative file paths referenced from my JUnit tests. These relative refernces are working correctly if I run the JUnit test from eclipse IDE, but they are not correctly resolved when I run the same test from headless build.

Would you be so kind as to write me some hint how to solve these problems?

Thanks in advance.

Stefanko

Unit tests are kicked off through Ant targets and must be run in a properly configured test environment. A sample Ant script can be downloaded via the link in the post, and I describe how to set this a test environment here:

http://www.modumind.com/2008/08/01/creating-a-test-environment-for-the-eclipse-testing-framework/

If these don’t answer your question, please feel free to clarify what you need to know.

— Patrick

Thanks for this article. It was very helpful. I tried the new eclipse Testing framework(3.6M4) with my JUnit4 test case and it was working.

Could you perhaps give me some suggestion on how to execute JUnit Plug-in tests from headless Build?

Thanks in advance.

Stefanko

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