On Fri, Jun 27, 2008 at 12:35 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Bertrand Delacretaz schrieb: >> ...Why would having tests create more pain than not having tests? > > Because of non-production dependencies you include (e.g. JUnit etc).... Ok, that can be an issue, agreed. > ...how about this approach: We keep the testing and production support > separate. We distribute special testing support (bundles). People may wish > to install and use the to integration test our and their bundles. If the are > satisfied, they remove the testing bundles again, and we are done.... Agreed, having separate testing bundles looks like the best way to solve this. A good first use-case for this would be to extract the integration tests from the launchpad/webapp module into a separate testing bundle, and in a second step create a simple UI to run those from within Sling, without requiring Maven. -Bertrand
