Re: Integration tests near to modules

[Robert Munteanu <ro...@apache.org>]

On Wed, 2016-09-28 at 22:06 +0000, Stefan Seifert wrote:
> a goal would be to move most of module-specific integration tests
> "near to the module" or just in the module project itself, using one
> oft the numerous available integration test tool support available in
> sling today. this is already the case for several new and complex
> modules.

+1, I think this is a good idea, and makes even more sense once/if we
move to a git module per repository setup.

Robert

Re: Integration tests near to modules

[Andrei Dulvac <du...@apache.org>]

On Mon, Oct 3, 2016 at 12:48 PM Robert Munteanu <ro...@apache.org> wrote:

> On Wed, 2016-09-28 at 22:06 +0000, Stefan Seifert wrote:
> > a goal would be to move most of module-specific integration tests
> > "near to the module" or just in the module project itself, using one
> > oft the numerous available integration test tool support available in
> > sling today. this is already the case for several new and complex
> > modules.
>
> +1, I think this is a good idea, and makes even more sense once/if we
> move to a git module per repository setup.
>
I wholeheartedly second that +1 (test should be next to the code they're
written for; forking, branching, etc. work ootb), which adds up to a +2 :)
- Andrei

>
> Robert
>