+1 To achieve that, it would be good, if there would be some documentation available how testing stuff (especially integration tests) should be done in the Sling project.
best regards Mike > -----Original Message----- > From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] > Sent: Friday, April 05, 2013 11:11 AM > To: dev@sling.apache.org > Subject: Re: Automated tests, at least under /bundles > > On Fri, Apr 5, 2013 at 10:56 AM, Carsten Ziegeler <cziege...@apache.org> > wrote: > > ...basically +1 - but I don't consider this a blocker > > > > We have the same situation with documentation... > > The impact of incomplete documentation is way less than having > untested code to our core. > > Either we care about Sling being a high-quality framework, and we > supply tests to demonstrate it and ensure it stays that way - or it's > just a pile of code that's supposed to work. > > I'm in favor of the former ;-) > > -Bertrand
