Thanks Oliver, this ContentLoader mechanism come from the Sling Mocks
<https://sling.apache.org/documentation/development/sling-mock.html> I
believe, it's simply works if your test is not depending on the full setup
which is the reason to have TeleporterRule here. I doubt that the Sling
Mocks are available on the server side usually as that is against the idea
of mocking Sling then.

Of course Sling Mocks / AEM Context extensions are useful and powerful
tools already but it's not in the scope of Teleporter use cases I think.

If we can enhance the existing ContentLoader bundle code that would
certainly resolve the above use cases. Especially if we could simply import
a predefined structure as described above, instead of listing one by one
each resources which we indeed already know how to do.

Regards,
-Thierry


On Wed, Dec 2, 2015 at 10:29 AM Oliver Lietz <[email protected]> wrote:

> On Wednesday 02 December 2015 10:10:26 Bertrand Delacretaz wrote:
> > Hi Oliver,
>
> Hi Bertrand,
>
> > On Wed, Dec 2, 2015 at 10:03 AM, Oliver Lietz <[email protected]>
> wrote:
> > > ...+1 for enhancing the Content Loader. It needs some streamlining and
> > > care
> > > anyway (see open issues) and patches are very welcome....
> >
> > +1 to that, testing looks like a good use case for improving it.
> >
> > Teleported tests shouldn't need anything special for this compared to
> > other OSGi code, as they are running in bundles. And thanks to
> > Thierry's recent contribution resources can also be teleported, we
> > might just need to improve the content loader and/or JUnit rules,
> > distinct from the TeleporterRule to avoid mixing concerns.
> >
> > I'm busy with other things at the moment, hoping to have a look at
> > this early next week.
> >
> > > ...check the very good work done by Stefan in the testing area. Maybe
> > > it's already possible to import content the way you want with the tools
> > > developed by him....
> >
> > Which tools do you mean?
>
> my co-workers used something from wcm.io to import content, not sure if
> that
> tools already live in the Sling repo and how capable they are - better ask
> Stefan himself.
>
> O.
>
> > -Bertrand
>
>
>

Reply via email to