[
https://issues.apache.org/jira/browse/SLING-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844431#action_12844431
]
Carsten Ziegeler commented on SLING-1437:
-----------------------------------------
In general a gread idea.
For measuring code coverage in integration tests, it would be cool to have some
Sonar integration - the same goes for coverage of script code.
> GSoC 2010: create more unit and integration tests for Sling
> -----------------------------------------------------------
>
> Key: SLING-1437
> URL: https://issues.apache.org/jira/browse/SLING-1437
> Project: Sling
> Issue Type: Task
> Components: Testing
> Reporter: Bertrand Delacretaz
>
> 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.
> The student will have to get familiar with the Sling codebase, identify areas
> where tests are missing, write unit and integration tests to improve the test
> coverage, and submit the result as patches that the Sling committers can
> verify and hopefully apply.
> Another aspect is measuring and reporting (automatically, ideally as part of
> our Hudson builds) the actual test coverage - that's easy for unit tests
> which run as part of the module builds, but seems to be harder for
> integration tests which run in a separate JVM than the one that executes
> tests.
> See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the
> ASF, and http://community.apache.org/gsoc for general GSoC information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
