Hey, If you are talking about integratino tests, then I like the approach of using the slingfeature-maven-plugin and the feature-launcher-maven-plugin to create a specific sling containing the bundles you need for your test suite and launch that to run your tests against
An example of one I created you can find here: https://github.com/orbinson/opentelemetry-osgi-wrappers/tree/main/integration-tests/src/main/features https://github.com/orbinson/opentelemetry-osgi-wrappers/blob/main/integration-tests/pom.xml#L122 https://github.com/orbinson/opentelemetry-osgi-wrappers/blob/main/integration-tests/src/test/java/be/orbinson/osgi/opentelemetry/it/OpenTelemetryIT.java#L30 Greets, Roy > On 11 Apr 2025, at 17:04, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > > Hi, > > It's been a while since I touched any Sling code, and I now have a > small change to make to the servlets-resolver module, SLING-12739 [1]. > > The code changes are simple but I want serious testing, and the age of > that module shows in the tests which use somewhat old versions of the > pax testing stuff and older dependencies in general. > > I'd prefer using a separate POM for my new tests, tried a setup using > exec-maven-plugin and that looks reasonable to me [2]. > > This helps keep the changes to the original (stable, core) module to a > minimum while providing a convenient testing environment for new > integration tests. > > What do people think of this approach, and do we have other similar > examples already, with tests in a submodule? > > -Bertrand > > [1] https://issues.apache.org/jira/browse/SLING-12739 > [2] > https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/2ebbb8e1ff23fecabe5b5b0100ac3f7be196dfb1
