Community
Participate
Working Groups
An setup I use is to have unit tests in a fragment, whose host is the bundle under test. It has the benefit of giving you full access to package and protected things, even if not exported by the host while keeping the tests tidy in a separate bundle. However, the test framework assumes that the bundleid you pass it is a host, and knows nothing about it being a fragment. A simple workaround is to invoke the test script in the fragment but to pass the id of the host plugin, which is weid. I'll try to submit a patch.
Created attachment 63224 [details] Fragment support based Eclipse 3.2.2 release
Created attachment 63225 [details] Fragment support based HEAD release
The attached patches check if the plugin is a fragment or host. If this is a fragment, the host bundle is found, and used instead to load classes. Without that patch, the current implementation fails to loads tests when they are provided in a fragment.
Any chances to look at that? or after 33?
Patch for the HEAD stream has been applied. Will test in nightly build. Will require approval from PMC for 3.2.x stream.
I'm now encountering this issue for the first time running 3.4. I had no problems running fragment tests in 3.3, probably because of this patch. I'm wondering if I should submit a new bug report for this in 3.4 or if it's related to what's already been done here. Thanks, --- Patrick
I wanted to revisit this entry because I recently attempted to run fragment based unit tests with the Eclipse Test Framework under 3.5.1. The tests in the fragment still cannot be found. BTW, I'm putting the id of the host plugin in the core-test target, but I've tried the fragment id as well. Is anyone able to run fragment based unit tests using the ETF? Am I doing something wrong? Thanks, --- Patrick
I don't know that this would work in 3.5. I personally don't have any any fragment test bundles. Does anyone else on the bug run tests on fragments in the 3.5.x stream?
I'm going to mark this as "won't fix", because a) its so old, and b) I think with OSGi and our test framework, there is no way to "invoke" tests on a fragment. In a sense, by the time bundles are loaded, the fragment "becomes part of the host bundle". But, I've heard of people doing similar things using the "normal" JUnit support with annotations in the fragment to identify classes/methods as tests. I'm perfectly willing to reconsider if you still think this possible, but ... you'll have to try and provide current patches for 4.x stream to be considered. Thanks, though, for reporting. I'm just trying to clean up "old bugs".
