[
https://issues.apache.org/jira/browse/SLING-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352755#comment-14352755
]
Petr Shypila commented on SLING-1437:
-------------------------------------
I've got a JaCoCo code coverage summary and it looks like some modules under
/bundles are not covered with tests at all:
{noformat}
#bundles/commons
org.apache.sling.commons.logservice - Code coverage 0%
org.apache.sling.commons.scheduler - Code coverage 0%
org.apache.sling.commons.threaddump - Code coverage 0%
org.apache.sling.commons.threads - Code coverage 0%
#bundles/extensions
org.apache.sling.bundleresource.impl - Code coverage 0%
org.apache.sling.discovery.api - Code coverage 0%
#bundles/engine
org.apache.sling.engine - Code coverage 20%
#bundles/extensions
org.apache.sling.featureflags - Code coverage 0%
org.apache.sling.fsprovider.internal - Code coverage 0%
org.apache.sling.hc.webconsole.impl - Code coverage 0%
org.apache.sling.models - Code coverage 0%
org.apache.sling.extensions.webconsolesecurityprovider.internal - Code coverage
0%
#bundles/jcr
org.apache.sling.jcr.base - Code coverage 0%
org.apache.sling.jcr.classloader.internal - Code coverage 0%
org.apache.sling.jcr.jackrabbit.accessmanager - Code coverage 0%
org.apache.sling.jcr.jackrabbit.server - Code coverage 0%
org.apache.sling.jackrabbit.usermanager - Code coverage 0%
org.apache.sling.jcr.registration - Code coverage 0%
org.apache.sling.jcr.webconsole.internal - Code coverage 0%
org.apache.sling.jcr.webdav.impl - Code coverage 0%
org.apache.sling.resourceaccesssecurity - Code coverage 0%
#bundles/scripting
org.apache.sling.scripting.jsp - Code coverage 0%
#bundles/servlets
org.apache.sling.servlets.get.impl - Code coverage 13%
org.apache.sling.servlets.post - Code coverage 16%
{noformat}
I still don't have a clarity of the scope of work to cover all these modules
with test, but I think it's a good task improve my skills in unit and
integration tests development. So I still want to be applied for this project
as a part of GSoC. And my next point is to present some examples of my work.
BTW: It's also looks like all changes from SLING-1803 are already in trunk.
Anyway I have deployed trunk branch with maven jacoco-report profile and it has
created for me all reports I need.
Best,
Petr
> 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)
