I also just observed that the WebconsoleClient still has a dependency towards testing.tools. I created a bug report in https://issues.apache.org/jira/browse/SLING-5725 <https://issues.apache.org/jira/browse/SLING-5725>.
> On 12 May 2016, at 14:14, Konrad Windszus <[email protected]> wrote: > > Just had a closer look at those classes and to me the difference between > WebconsoleClient and OsgiConsoleClient is not really obvious. > Shouldn't we rather merge those two? > Konrad > >> On 04 May 2016, at 14:47, Andrei Dulvac <[email protected]> wrote: >> >> Hi, >> >> Thanks Radu for applying the docu patch. >> You can find a small section here: >> http://sling.apache.org/documentation/tutorials-how-tos/testing-sling-based-applications.html#http-based-integration-tests >> >> Cheers, >> - Andrei >> >> On Tue, May 3, 2016 at 11:54 AM Andrei Dulvac <[email protected]> >> wrote: >> >>> Hi guys, >>> >>> Thanks for the explanations. I've added a section in the sling testing >>> page. >>> Please see the mail "CMS diff: Testing Sling-based applications" on the >>> dev list. >>> Could someone have a look? >>> >>> Thanks! >>> - Andrei >>> >>> On Tue, May 3, 2016 at 10:53 AM Bertrand Delacretaz < >>> [email protected]> wrote: >>> >>>> On Tue, May 3, 2016 at 10:46 AM, Konrad Windszus <[email protected]> wrote: >>>>> Just providing a patch on the markdown pages in the SVN referenced in >>>> [0] should work fine... >>>> >>>> Sure - where cms.apache.org can help is in previewing the changes with >>>> the exact same markdown engine used for sling.apache.org. >>>> >>>> -Bertrand >>>> >>> >
