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

Myrna van Lunteren closed DERBY-6164.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 10.11.1.1

I moved the one remaining issue into a separate issue rather than a subtask 
(DERBY-6164), so this issue can now be closed.

> Improve Derby's Code Coverage - GSoC 2013 Project
> -------------------------------------------------
>
>                 Key: DERBY-6164
>                 URL: https://issues.apache.org/jira/browse/DERBY-6164
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>            Reporter: Bryan Pendleton
>            Assignee: ahsan shamsudeen
>            Priority: Minor
>              Labels: gsoc2013
>             Fix For: 10.11.1.1
>
>
> This year's edition of Google Summer of Code includes, once again, the Apache 
> Software Foundation.
> For the Derby project, I'm offering to mentor a student on the tasks 
> described here.
> For this project, you are required to have some basic knowledge of JUnit and 
> of how code coverage works.
> Currently some packages of Derby have poor code coverage. Emma defines the 
> minimum acceptable code coverage as 70% and some engineers suggest a minimum 
> of 80% is desired. 
> Students are invited to look at [1] to get familiar with Emma's code coverage 
> reports on Derby. 
> The Derby project conducted this effort last year, and substantial 
> improvements were made.
> We are looking to continue this process this year, as there are still areas 
> of the Derby code base where code coverage could be substantially improved.
> The candidate students are also expected to come up with their own schedule 
> for the tests they plan on creating and to discuss this schedule publicly on 
> the mailing list. 
> After a student applies, a small interview will be conducted via email as 
> part of the ASF's evaluation process. 
> [1] - http://dbtg.foundry.sun.com/derby/test/coverage/



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

Reply via email to