How to set-up a project that creates server-side (sling-based) tests in a CQ Author Instance

[cfBeth]

Aside from junit tests incorporated in every build and selenium tests for components, we want to explore the use of server-side (sling-based) tests for integration testing.  There will be cases where we need to test components that use references to classes such as SlingRepository or ResourceResolverFactory classes without using mock objects.  How should we go about it? What is the best way to implement?  We would want to create separate project that: executes all the test cases , create pages or nodes to test certain functionalities and then be able to delete created content nodes after all tests have been executed (specially if running in the production environment).

[smacdonald2008]

Why not just  set-up a test CQ app that uses server-side OSGi bundles and other assets that you want to test. A lot of teams do that.  

[Sham_HC · Accepted solution]

http://sling.apache.org/documentation/development/sling-testing-tools.html#server-side-junit-tests-c...