Integration Tests

[Dan Klco <da...@sixdimensions.com>]

All,

For doing some end-to-end testing of the new Resource Access Tags, I added some integration tests into the project.   These tests take approximately 16 seconds to run and require starting up an instance of Sling on a random port.  Should these tests be included as part of the default build or moved into a profile or be put into a separate integration testing project?  

I have attached a patch containing the changes I am intending to make.

Please let me know if you have any questions or concerns about this approach.   

Thanks,
Dan

Re: Integration Tests

[Bertrand Delacretaz <bd...@apache.org>]

Hi Dan,

On Mon, May 20, 2013 at 7:39 PM, Dan Klco <da...@sixdimensions.com> wrote:
> For doing some end-to-end testing of the new Resource Access Tags, I added some integration tests into the project.
> These tests take approximately 16 seconds to run and require starting up an instance of Sling on a random port.
> Should these tests be included as part of the default build or moved into a profile or be put into a separate integration testing project?...

IMO you can integrate these new tests under
launchpad/integration-tests - if the module that you test is included
in the default launchpad.

If that's not the case, we should either discuss a way for extensions
to contribute tests to the launchpad integration test suite, or create
a simpler way of testing those extensions in a Sling context.

-Bertrand