Hi, Currently I looking on how Sling's tests are designed and can't understand some moments. I'll be very thankful if you clarify it to me. The main moment here is that I can't clearly understand role of launchpad/testing module on testing. I main I see a lot of tests under launchpad/integration-tests directory(or some other tests directories under launchpad dir). But how do they differ from tests under src/test directory of each module? I have read readme files, but unfortunately it didn't helped me.
Thanks in advance, Petr 2015-03-06 13:03 GMT+03:00 Bertrand Delacretaz <[email protected]>: > Hi, > > On Thu, Mar 5, 2015 at 9:12 PM, Petr Shypila <[email protected]> wrote: > > ...probably I just do something wrong and there is a nice and easy > solution or > > I just should investigate this problem deeper?... > > I don't think there's an easy solution now for getting the overall > coverage of a module, including whatever launchpad/testing tests. > > The use case would be, when working on a module like > bundles/servlets/post, to get a coverage report when running "mvn > clean install" that include the coverage of the last run of the > launchpad/testing tests. > > This was working using the patch mentioned in my 10/Apr/13 18:25 > comment to SLING-1803, by deploying the test coverage data from > launchpad/testing to Maven, but I wasn't sure if that's the right > approach. Maybe you can try that patch and see where that leads. > > -Bertrand >
