[
https://issues.apache.org/jira/browse/DERBY-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575098#action_12575098
]
Daniel John Debrunner commented on DERBY-3445:
----------------------------------------------
Thanks Vemund, I was able to get code coverage running very easily now using
the emma-all target.
With the previous EMMA reports I was able to click down through the HTML report
to an individual file and see which specific blocks had not been covered, I
think with coloured source code. With the report I just generated using
emma-all I was not able to see this information. The lowest level was the
coverage breakdown by method.
Anyone any idea what needs to be done to get the source code level information?
> Make it easier to use the EMMA tool to measure the code coverage of the Derby
> testing
> -------------------------------------------------------------------------------------
>
> Key: DERBY-3445
> URL: https://issues.apache.org/jira/browse/DERBY-3445
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Vemund Østgaard
> Assignee: Vemund Østgaard
> Attachments: 3445-general-diff, 3445-general-diffv2,
> 3445-singletest-codeline-jars-diff, 3445-singletest-diff,
> 3445-SysinfoLocaleTest-diff, 3445-testspecific-diff, 3445-testspecific-diffv2
>
>
> It is a bit tricky to use EMMA to measure code coverage for the derby testing.
> Modifications must be made to the source both to avoid problems with the
> SecurityManager and individual tests. It would be good if these modifcations
> could be done once and for all so that it was easier for anyone to run the
> tests with EMMA.
> It would also be good to have ant tasks that would make it even easier to run
> the tests with EMMA.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
