sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7936) Execute module integration tests in the launchpad-testing module
Date Tue, 15 Jan 2019 21:41:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-7936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743418#comment-16743418
] 

Robert Munteanu commented on SLING-7936:
----------------------------------------

Stopping progress since I think any maven plugin enhancements would be better found in the
feature model tooling, but we're not using the feature model yet.

> Execute module integration tests in the launchpad-testing module
> ----------------------------------------------------------------
>
>                 Key: SLING-7936
>                 URL: https://issues.apache.org/jira/browse/SLING-7936
>             Project: Sling
>          Issue Type: Improvement
>          Components: Build and Source Control, Starter
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Starter 12
>
>
> In the last years we've decided to move integration tests closer to the modules they
live in, which is a good thing (TM).
> There are also good things about having a central place to execute them, such as the
ability to run those tests on multiple Java versions.
> One idea of how to approach this is to define integration tests in the modules, and run
them during the regular build. On top of that, deploy the integration tests as their own artifacts
(maybe same but with {{integration-test}} classifier ) and then execute them as part of the
Sling ITs.
> This would get us the best of both worlds - tests living next to their module, and also
the ability to execute "all" tests in a single unit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message