[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678424#comment-16678424
]
Robert Munteanu commented on SLING-7935:
----------------------------------------
[~olli] - that's something I hadn't considered before, sorry. My medium-term
plan is the following ( will send a proposal to dev@ before starting work on it
):
- extract integration tests for specific bundles and move then to the
respective bundle
- run those ITs alongside the bundle in the regular build (this is IMO the big
win)
- in the launchpad-testing module, collect IT modules for modules part of the
starter and run then like we do today
In this scenario, the tests will be released with the bundle, so you will
always refer to then by a released version.
Would that work for you?
> Consolidate all 'launchpad-testing' modules into a single git repository
> ------------------------------------------------------------------------
>
> Key: SLING-7935
> URL: https://issues.apache.org/jira/browse/SLING-7935
> Project: Sling
> Issue Type: Task
> Components: Launchpad
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Starter 12
>
>
> We currently have seven testing-related modules in Git:
> * org-apache-sling-launchpad-integration-tests
> * org-apache-sling-launchpad-test-bundles
> * org-apache-sling-launchpad-test-fragment
> * org-apache-sling-launchpad-testing
> * org-apache-sling-launchpad-testing-war
> * org-apache-sling-launchpad-test-services
> * org-apache-sling-launchpad-test-services-war
> All of these are related to testing the starter application and typically we
> only release them when the starter is also released. As such, it's a pain to
> manually keep versions in sync and release the modules one by one. This is
> one scenario where a single git repository would make sense.
> Whether this should be the actual starter repository or a starter-testing one
> is something that is not set in stone, but the current situation is not
> optimal.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
