Hey Andrei, could you briefly mention those new bundles in
just to have the complete picture on those pages?
To me the difference to the Teleporter approach is not that obvious. Maybe you
can write some sentences on when it is recommended to choose which approach.
> Am 21.09.2016 um 10:11 schrieb Andrei Dulvac <dul...@apache.org>:
> Hi Stefan.
> Thanks for the +1.
> On Tue, Sep 20, 2016 at 6:20 PM Stefan Seifert <sseif...@pro-vision.de>
>> this is a lot of interesting stuff - do we already have some
>> documentation/sample project for this?
> We have some docu on the junit rules  - the entrypoint for writing a
> test, some docu on the clients  (the FAQ at the end also provides some
> insight into some design choices).
> I've also adapted the old SlingTestBase from sling.testing.tools in
> serversetup  in order to use those in the sling tests, using the
> existing mechanism to start a new sling instance for tests, as part of the
> maven build. It's used in the SlingInstanceRule  which I used to adapt
> some sample tests like  (I didn't want to touch launchpad tests or
> anything like that, but I'm willing to put in some work if needed). I see
> Bertrand also adapted some tests there, in samples/ lately.
> That's mostly what we have, no wholesome documentation, unfortunately. Ah,
> another helpful thing to have a look at is the unit tests for the clients,
> like AbstractSlingClientGetUrlTest  which makes sure there are no
> regressions in terms of how URIs are dealt with.
> - Andrei
>  https://github.com/apache/sling/tree/trunk/testing/junit/rules
>  https://github.com/apache/sling/tree/trunk/testing/http/clients