[
https://issues.apache.org/jira/browse/OFBIZ-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854800#action_12854800
]
Bob Morley commented on OFBIZ-3659:
-----------------------------------
I agree; my initial approach was to include the download in the test process.
The trouble is the cobertura jar is required to do our compile; if it is not
present then our implementation of the instrumenter is not compiled and
included in the (I think) base jar. There is another ant target for the
"reports" already existing; this bug does not do anything with that -- this is
the ability to compile with Cobertura so that when the test process executes it
can instrument and generate the code coverage metrics.
We can do some refactoring on the pluggable instrumentation implementation so
that it has a separate build process from the main build. That is to say when
you execute tests we could do an "init-tests" target that would download
cobertura and build our integration class at that time.
If you guys want me to bite off that then that is fine -- but what I would ask
is that we remove the line that calls "download-cobertura" in my patch so that
the other two targets are available to call manually.
> Download cobertura code coverage jar so it can be used to compile and execute
> tests with
> ----------------------------------------------------------------------------------------
>
> Key: OFBIZ-3659
> URL: https://issues.apache.org/jira/browse/OFBIZ-3659
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Bob Morley
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: OFBIZ-3659_AutomateDownloadOfCobertura.patch
>
>
> Framework executed around allowing use of cobertura to create code coverage
> metrics as part of the Ofbiz build process. Licensing restricts distribution
> of cobertura with Ofbiz, so we have taken the approach to attempt to download
> it before doing our build so it is available for any container that wants
> instrumentation turned on (currently only test-container). Net result is
> when we run our tests we will now get very nice code coverage metrics being
> generated.
> There is an existing target to generate the cobertura report (html) which is
> not automatically being executed. Once we get more reasonable code coverage
> via unit testing we can automatically generate this and expose it as
> appropriate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
