[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073556#comment-17073556
]
Bertrand Delacretaz edited comment on SLING-7935 at 4/2/20, 9:44 AM:
---------------------------------------------------------------------
bq. ...Launchpad ITs are a moving target which is hard to track also because
new tests are added for snapshots....
That used to be a problem but recently we've been adding ITs closer to or
directly in the modules that they test, AFAICS the last addition of a test
there was in January 2019, [commit
3da37cc96|https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/commit/3da37cc963fa1367d07eb1ed2d37cb3296d6b270].
These tests are very important to preserve backwards compatibility IMO but
nowadays we have better ways to implement ITs in their own modules.
I think it would be reasonable to declare the Launchpad ITs as "frozen legacy
integration tests" that we don't touch except to fix the tests themselves if
really needed, and declare that new ITs go elsewhere.
Would that help with your concern about ITs being a moving target?
was (Author: bdelacretaz):
bq. ...Launchpad ITs are a moving target which is hard to track also because
new tests are added for snapshots....
That used to be a problem but recently we've been adding ITs closer to or
directly in the modules that they test, AFAICS the last addition of a test
there was in January 2019, [commit
3da37cc96|https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/commit/3da37cc963fa1367d07eb1ed2d37cb3296d6b270].
These tests are very important to preserve backwards compatibility IMO but
nowadays we have better ways to implement ITs in their own modules.
I think it would be reasonable to declare the Launchpad ITs as "frozen legacy
integration tests" that we don't touch except to fix the tests themselves if
really needed, and declare that new ITs go elsewhere.
Would that help with you concern about ITs being a moving target?
> 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
(v8.3.4#803005)
