Hi Julian, I think this is a great idea. It would increase the integration of modules by defining common combinations of bundles to test on and simplify the maintenance significantly (the combination of bundle is sorted out at a single location).
Regards, Timothee 2016-12-13 10:02 GMT+01:00 Julian Sedding <[email protected]>: > Hi all > > I looked at a PaxExam-based i18n test yesterday[0]. It was failing due > to missing service user + configuration amendment, which was already > adjusted for the launchpad. > > Furthermore noticing the long list of bundles installed into the > PaxExam container, I started thinking that it would be very convenient > to have a utility that can consume a provisioning file and use the > contained information as Pax-Exam-Options during the construction of a > test case. This way tests could depend on a released or snapshot > version of the launchpad[1], as well as defining their own > provisioning model. > > It may also be helpful to allow re-using the versions of the bundles > defined in a provisioning model, but only installing the ones whose > grouId+artifactId are explicitly mentioned in the test. > > WDYT? > > Regards > Julian > > [0] https://github.com/apache/sling/blob/trunk/bundles/ > extensions/i18n/src/test/java/org/apache/sling/i18n/it/ > ResourceBundleProviderIT.java#L165 > [1] https://repo1.maven.org/maven2/org/apache/sling/org. > apache.sling.launchpad/8/org.apache.sling.launchpad-8-slingfeature.txt >
