You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/07/22 15:35:20 UTC

[jira] [Updated] (SLING-5892) Add smoke tests to the Launchpad

     [ https://issues.apache.org/jira/browse/SLING-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-5892:
-----------------------------------
    Attachment: 0001-SLING-5892-Add-smoke-tests-to-the-Launchpad.patch

I've attached a patch which adds two tests:

* all bundles are started
* the repository is accessible via DAV

I've intentionally kept the tests short, small, and took on minimal dependencies. The launchpad does not depend on any Sling projects to prevent circular dependencies from coming into play or from clashing with the provisioning model.

The tests add about 10 seconds to the build on my machine:

* `mvn clean package` takes about 11 seconds
* `mvn clean verify` takes about 20.5 seconds

> Add smoke tests to the Launchpad
> --------------------------------
>
>                 Key: SLING-5892
>                 URL: https://issues.apache.org/jira/browse/SLING-5892
>             Project: Sling
>          Issue Type: Improvement
>          Components: Launchpad
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Launchpad Builder 9
>
>         Attachments: 0001-SLING-5892-Add-smoke-tests-to-the-Launchpad.patch
>
>
> The launchpad could benefit from a set of small, quick checks to assert that the build is complete
> - all bundles start
> - the JCR repository starts up



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)