[
https://issues.apache.org/jira/browse/DERBY-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575131#action_12575131
]
Vemund Østgaard commented on DERBY-3445:
----------------------------------------
Thanks again Dan for following up on this. Some answers to your comments:
- I'll fix the <emma-clean> target so it doesn't fail if there is no folder
there.
- The difference in output when running the <junit-jdbc4> target is (I'm
guessing) because I didn't set emma.verbosity.level=silent for this target, as
there was no tests that failed because of emma output. This property is set for
the <junit-core> target, so no output from emma there.
- You should have been able to click down to the source code level, at least
that worked when I tested this out in my sandbox. The <emma-report> target sets
this:
<sourcepath>
<pathelement path="${derby.client.src.dir}" />
<pathelement path="${derby.demo.src.dir}" />
<pathelement path="${derby.drda.src.dir}" />
<pathelement path="${derby.engine.src.dir}" />
<pathelement path="${derby.shared.src.dir}" />
<pathelement path="${derby.storeless.src.dir}" />
<pathelement path="${derby.tools.src.dir}" />
</sourcepath>
which is supposed to take care of that. Hmm, what is written during the
<emma-report> target in your run? When I run <emma-all> I see a lot of output
as emma scans through my source and creates the reports.
> 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.
