Hi, Just thinking out loud: How about adding another section besides bundles, commons and launchpad called "testing" ?
We could place your work there as well as the launchpad IT infrastructure projects and the commons/testing bundle. I think this would even increase the relative importance of testing. But could we handle the dependency tree ? WDYT? Regards Felix Am Mittwoch, den 02.02.2011, 17:19 +0000 schrieb Bertrand Delacretaz: > Hi, > > I've been working on SLING-1963 these days, which allows you to > > a) Run JUnit (3 or 4) tests in a live Sling instance by supplying them > in exported packages in bundles and pointing to them via a > Sling-Test-Regexp bundle header > > b) Run scripted tests by creating nodes with a sling:Test mixin and > setting them up so that a request with .test.txt outputs just > TEST_PASSED in case of success. > > The "user interface" at /system/sling/junit is still very rough, but I > think the current code demonstrates all of the "hard" parts, and is > already usable. > > Now, do we want this under contrib or bundles/extensions? > > Being the fan of testing that I am, I'd put this under > bundles/extensions, also to be able to use it in our launchpad test > suite. > > WDYT? > > -Bertrand
