Hi, It cant have been decided, as it wasn't, yet, discussed on-list. I don't have strong feelings about the subject of the "decision". Best Regards Ian
On 28 September 2016 at 23:06, Stefan Seifert <[email protected]> wrote: > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > in sling there is a big integration test project that tests the core sling > functionality and the different sling bundles playing together. a problem > with this apporach ist hat different aspects are mixed in one project, and > if a new module is released it may be required to release the integration > test project as well. > > a goal would be to move most of module-specific integration tests "near to > the module" or just in the module project itself, using one oft the > numerous available integration test tool support available in sling today. > this is already the case for several new and complex modules. > > it was decided that no new integration tests should be added to this > central integration test project. exceptions are integration tests covering > core sling functionality e.g. resource resolving, script resolution. > > stefan > > [1] https://svn.apache.org/repos/asf/sling/trunk/launchpad/ > integration-tests > > >
