[ 
https://issues.apache.org/jira/browse/SLING-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372706#comment-14372706
 ] 

Petr Shypila commented on SLING-1437:
-------------------------------------

Hi Bertrand,

Thanks for update. I've already created unit tests for two classes under 
/bundles package:
1. org.apache.sling.jcr.base.SessionProxyHandler - 95% Coverage 
https://github.com/PetrShypila/sling/blob/trunk/bundles/jcr/base/src/test/java/org/apache/sling/jcr/base/SessionProxyHandlerTest.java
2. org.apache.sling.jcr.base.util.AccessControlUtil - 4%. Coverage. 
Unfortunately testing other methods is a bit trickier and I need more time to 
investigate it.
https://github.com/PetrShypila/sling/blob/trunk/bundles/jcr/base/src/test/java/org/apache/sling/jcr/base/util/AccessControlUtilTest.java

I plan to provide my proposal on Thursday 26th. In my proposal I will provide 
links to tests I did and another issue I've found and fixed - SLING-4505. So 
what is the best way here?
1. Make a pull request to your repository and provide this link in my proposal.
2. Just provide links to tests I did, from my forked repository.

Thanks,
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)

Reply via email to