On Thu, 2018-11-08 at 17:07 +0100, Oliver Lietz wrote: > I wrote a proposal about how this could look like in terms of > > results > > > > https://cwiki.apache.org/confluence/display/SLING/Moving+integration+tests+c > > loser+to+the+code+they+test > > > > I purposefully avoided looking into implementation details to avoid > > doing too much work for nothing. > > > > What do you think about this possibility? > > did I get your point - we keep free-style and "managed" (using Sling > Testing > PaxExam) Pax Exam tests (which may also use Sling's HTTP API) as is?
Yes, my suggestion is to keep pax-exam tests separate and not run with the larger set of ITs. This is mainly because I think it's simpler to not tackle them right now. The Pax-Exam ITs manage their own Sling runtime rather than run against a given Sling release. This in turn makes it harder for me to propose a unified way of launching them as ITs running against the latest Sling starter. Thanks, Robert
