[
https://issues.apache.org/jira/browse/SLING-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372658#comment-14372658
]
Bertrand Delacretaz commented on SLING-1437:
--------------------------------------------
It is unfortunately possible that some modules have no tests but I guess we'll
concentrate first on the core modules found under /bundles.
The next step will be to create a setup (maybe on a Sling github fork of yours)
that produces a coverage report including both the module's local tests and all
tests executed by the launchpad/testing modules, so that we get a meaningful
combined coverage report.
> GSoC project: create more unit and integration tests for Sling and expand
> test coverage information
> ---------------------------------------------------------------------------------------------------
>
> Key: SLING-1437
> URL: https://issues.apache.org/jira/browse/SLING-1437
> Project: Sling
> Issue Type: Task
> Components: Testing
> Reporter: Bertrand Delacretaz
> Labels: gsoc, gsoc2010sling, gsoc2013, gsoc2015, java, mentor,
> testing
>
> Sling already has fairly good test coverage, but there's always room for
> improvement.
> The goal of this Google Summer of Code project is to create more unit and
> integration tests for Sling, as well as measure the test coverage that the
> combination of unit and integration tests provide.
> Interested students are welcome to get in touch with the Sling community via
> its developers mailing list to discuss the project, see
> http://sling.apache.org/project-information.html#mailing-lists
> The student will have to get familiar with the Sling codebase, identify areas
> where tests are missing, write unit and integration tests and submit the
> results as patches that the Sling committers can verify and hopefully apply.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
