I'm currently trying to improve test structure for Jboss Fuse Tooling
On Max recommendation, I take a look at jbosstools-devdoc
When i take a look to
. This project is in tests folder but it launches tycho-surefire-plugin.
As far as I understand Tycho, it means that it is launching an OSGi
platform. From my point of view, it means that these tests are already
integration tests and the only difference between tests and itests
currently is more fast vs slow tests.
What I wanted to achieve is to have really fast unit test, so I created
a fragment and so use maven-surefire-plugin. You can see the fragment
and the parent pom configuration:
Did I misunderstood something?
Are there counterpoints to use fragments and maven-surefire-plugin?
Are there other examples which are matching more closely to my usecase
in jboss tools codebase?
Thanks by advance for your help
Senior Software Engineer in JBoss Fuse Tooling Team
Here is a proposal for a change to the JBoss Tools and Red Hat JBoss
Developer Studio 4.52.0.Final-SNAPSHOT target platforms (for JBT
4.3.1.Final / JBDS 9.1.0.GA).
org.eclipse.epp.logging.aeri.feature 1.100.0.v20160304-1116 (was
p2diff report attached to the above JIRA.
Please review the above PR(s), as they will be applied as soon as possible in
preparation for CR1/GA code freeze.
You can use the following to build & test the
target-platform locally against your component(s).
$ cd /path/to/jbosstools-target-platforms/jbosstools/multiple
$ git fetch origin pull/123/head && git checkout FETCH_HEAD
$ mvn clean install
Then, to test the new "multiple" target platform against your component's build:
$ cd /path/to/your/jbosstools-component
$ mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio