Hi Oliver I am making good progress but I noticed that I cannot get composum up on both 3.1.0 or 3.0.0 which is the current version I am using because I am still running against Sling 11.
The issues I see is: 'The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved’ Also is there a way to keep the Sling instance running (something like keep running flag) after the tests were done in case I need to investigate an issue with the Sling instance like bundles dependencies etc? Thanks - Andy > On Aug 15, 2022, at 2:20 AM, Oliver Lietz <apa...@oliverlietz.de> wrote: > > On Sunday, 14 August 2022 23:15:16 CEST Andreas Schaefer wrote: >> Hi > > Hi Andy, > >> I am working on some sling components and want to IT test them within the >> server to avoid client-side polling. >> >> It looks like there are two ways to do that: >> >> - Junit Servlet >> - Sling Testing Server Setup and Teleporter >> >> Does Sling do any server side testing? >> What is the currently support way of doing server side tests? > > Running tests inside the OSGi container is the default when using OPS4J Pax > Exam. See the list of Sling modules using Sling's Testing PaxExam and have a > look what the ITs are doing to get some ideas: > > https://sling.apache.org/documentation/development/testing-paxexam.html > > Let me know if more documentation is needed. > > HTH, > O. > > >> Thanks - Andy > > > >
