The default Eclipse and also Tycho way for tests it to have separate bundles or fragments. See https://wiki.eclipse.org/Tycho/Packaging_Types#eclipse-test-plugin . Such tests are also not executed in Maven's test phase but integration-test phase and startup an OSGi environment.

This blog https://resheim.net/2014/12/unit-testing-eclipse-rcp-applications.html shows a way that allows to have unit tests in traditional Maven way. It works fine when building from command line, all tests are executed. But if one wants to edit and run them within Eclipse two manual steps per bundle are required (add src/test/java to source folders and add JUnit to build path).

As we currently only have 21! unit test classes I'd recommend to try the 2nd approach for them, otherwise we'd need to 8 additional test projects.

For integration tests (SWTBot) of course we need to create proper test bundles, I'll try to do that.

Thoughts?

Unit tests and core integration tests are new executed within the normal build. UI tests are also functioning (both from within Eclipse and from maven tycho), but not yet included as some tests are failing, requires more investigation.

UI tests are now configured in the build but disabled by default. They are not yet fully working, for now its good enough, but later I'd like to improve them.