4

I have several OSGi-bundles that I build with Eclipse Tycho. All code dependencies are managed manifest-first.

Now I want to develop some pure JUnit-Tests in order to test bundle-internal functionality. These tests do not need an OSGi-container in order to be executed, but they do need Mockito.

As Mockito obviously is only needed when this non-OSGi-tests are being run and not during the execution of the bundle itself, it feels wrong to add the dependency to the MANIFEST.MF file.

My current approach is that I added a project/lib-folder that holds the mockito.jar and that I added this jar to his classpath manually. This works for local eclipse execution, which is fine for the moment.

The problem is, that every coworker needs to add the jar to the classpath as well, as the .classpath-file is obviously not checked in. Also, I guess that there will be problems when the tests eventually will be executed e.g. on a build server because of the missing classpath entry.

So my question is: How can I add the dependency to Mockito in a way that will work effortless for every coworker and will not cause any problems during bundle execution?

I could add it as optional dependency to the MANIFEST.MF-file, but as stated above, it doesn't feel like thats the correct solution.

Can I add the mockito-dependency as normal pom-first dependency with scope test or will this cause conflicts with the normal manifest-first approach?

I also found the maven-eclipse-plugin which offers a classpathContainers configuration option, but I did not find a similar option to add a library to the classpath.

The tests are located in the src/test/java folder of the bundle itself.

What is the best way to add test-only dependencies to a project built with eclipse Tycho, given that I technically don't need Tycho in order to execute those tests?

Improve this question

2 Answers 2

Reset to default
1

If you can run your test with a class path that you completely only compose of Maven dependencies (e.g. to Mockito), you could also create a module with jar packaging for these tests. From that module, you'd also add a dependency to the bundle, which would then be used as plain JAR.

What you'd loose in this case is the resolution of transitive dependencies. The jar project would then be resolved by Maven, and Maven doesn't know about the Manifest dependencies of the OSGi bundle. But depending on the exact nature of what you want to test, this may still work.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

0

Typically you'll see tests in a separate bundle, with it's own manifest and dependencies. This is not the standard Maven structure, but it fits better with how OSGi bundles want to be structured.

For example, look at the JDT-core git repository, you'll see separate test bundles. Note that test bundles have a special packaging-type of eclipse-test-plugin.

Improve this answer

2 Comments

We do that for integration tests which require an OSGi-container and several bundles in order to be executed. But for simple JUnit-tests that seems to be quite an overhead (those tests in their current location also run perfectly fine with "Run as JUnit test" and do not need to be executed as Plug-In test). I'm looking for some solution to solve the dependency problem (it looks like it should be such a small issue!) without having the management and runtime overhead that comes with creating a bundle for the tests.
In the end, creating a separate bundle will be the last resort, but if theres another suitable solution, I'll gladly take it.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.