[
https://issues.apache.org/jira/browse/DERBY-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574553#action_12574553
]
vemund edited comment on DERBY-3445 at 3/3/08 7:34 AM:
----------------------------------------------------------------
Thank you Dyre!
I've started on a wiki page here:
http://wiki.apache.org/db-derby/CodeCoverageWithEMMA
Hopefully that has enough information for you to use the emma targets.
The junit-single target works the same way as the junit-all and
junit-system-mini targets. They all require you to set the classpath to point
to your Derby classes or jars. If you are using ant 1.6.5 you must also have
junit.jar and ant-junit.jar in your classpath. I don't have this problem with
ant 1.7.
To configure the classpath when running junit targets I have been using the
property derby.junit.classpath. I guess you can just set your CLASSPATH env var
as well, or use the -lib option for ant, I haven't tried.
When you use the emma targets (emma-single and emma-all) you don't have to
worry about the classpath, this is overridden by the emma targets. You have to
download emma.jar and emma_ant.jar (in addition to junit.jar) and place them
under tools/java/ in your sandbox. You must build your jars as usual, either
sane or insane, and then you can use the emma targets.
was (Author: vemund):
Thank you Dyre!
I've started on a wiki page here:
http://wiki.apache.org/db-derby/CodeCoverageWithEMMA
Hopefully that has enough information for you to use the emma targets.
The junit-single target works the same way as the junit-all and junit-simple
targets. They all require you to set the classpath to point to your Derby
classes or jars. If you are using ant 1.6.5 you must also have junit.jar and
ant-junit.jar in your classpath. I don't have this problem with ant 1.7.
To configure the classpath when running junit targets I have been using the
property derby.junit.classpath. I guess you can just set your CLASSPATH env var
as well, or use the -lib option for ant, I haven't tried.
When you use the emma targets (emma-single and emma-all) you don't have to
worry about the classpath, this is overridden by the emma targets. You have to
download emma.jar and emma_ant.jar (in addition to junit.jar) and place them
under tools/java/ in your sandbox. You must build your jars as usual, either
sane or insane, and then you can use the emma targets.
> 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-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.
