db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project
Date Mon, 29 Apr 2013 14:12:16 GMT

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

Bryan Pendleton commented on DERBY-6164:

That's great, it looks like you have the tools configured successfully now.

The next step is to start reading the reports at http://dbtg.foundry.sun.com/derby/test/coverage/
which are from runs that perform the full Derby test suite.

Looking at those runs, see if you can identify some areas of the Derby code base that
have low coverage; those are the areas where we are trying to write new tests to
improve our test coverage.

Many areas of the Derby code base are quite well covered by our test suite, but we
can still identify substantial portions of the code that are not well-tested, and our
goal this summer is to find some of those areas and address them.

For example, consider this class: http://dbtg.foundry.sun.com/derby/test/coverage/_files/6d.html
This is the report for IndexStatisticsDaemonImpl.java. This is a quite new class in the
Derby code base, I believe, and although we have a number of test cases for it,
perhaps there are additional test cases that can be written to increase the coverage.

Have you drafted your proposal to Google?
> 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: Bryan Pendleton
>            Priority: Minor
>              Labels: gsoc2013
> This year's edition of Google Summer of Code includes, once again, the Apache Software
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message