db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5674) Improve Derby's Code Coverage - GSoC 2012 Project
Date Thu, 05 Apr 2012 18:22:23 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247462#comment-13247462

Kathey Marsden commented on DERBY-5674:

In the context of a thread on the list there was some advice to applicants from Tiago and
I that I wanted to put here so it is not missed.  There are  just over 24 hours to get your
application in and it would be good to run a draft  by the list.  

Tiago said:

> Finally, here's a heads-up to all the students who would like to apply to this project:
the application deadline is on April 6th, meaning you should get your project proposals submitted
before then. 
> Be sure to submit an abstract, a description of the tests you're willing to take on and
a schedule for the conclusion of the tests. It is also important to mention whether you have
successfully set up the Derby environment and whether you managed to compile Derby. I would
also appreciate if the applicants send me (off-list, directly to my e-mail address) the jars
resulting from their compilation. To strengthen your application I also recommend serious
applicants to come to  our IRC channel (#derby @ irc.freenode.net) for an informal and quick
> If you have developed for Derby before and/or created unit tests, please mention this
in your application.
I added ...

I am not sure if the process is exactly the same this year.  But here is the scoring criteria
for past years.  Some things you might not think of like the interview or indicating how much
time you can  dedicate count for a lot.  So I suggest you review the scored items and make
sure you are covered.


Also if you are not subscribed to the lists and are serious about GSoC for Derby, you should
get subscribed.

> Improve Derby's Code Coverage - GSoC 2012 Project
> -------------------------------------------------
>                 Key: DERBY-5674
>                 URL: https://issues.apache.org/jira/browse/DERBY-5674
>             Project: Derby
>          Issue Type: Task
>            Reporter: Tiago R. Espinha
>            Priority: Minor
>              Labels: gsoc2012
> This year's edition of Google Summer of Code includes, once again, the Apache Software
Foundation. As I did last year, I'm offering to mentor a student again this year, this time
for a different project.
> For this project, the student is 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
> Students are invited to look at [1] to get familiar with Emma's code coverage reports
on Derby.
> A few suggestions of classes that require improvements are:
> - org.apache.derby.client.net - importnat package with poor coverage.
> - org.apache.derby.iapi.types - several classes not tested at all and others with poor
> - org.apache.derby.iapi.jdbc - could use extensive improvements.
> - org.apache.derby.impl.io - another package with poor coverage.
> 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 on IRC as part of the ASF's
evaluation process.
> [1] - http://dbtg.foundry.sun.com/derby/test/coverage/

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message