[
https://issues.apache.org/jira/browse/OFBIZ-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854819#action_12854819
]
Bob Morley commented on OFBIZ-3659:
-----------------------------------
Scott -- I have just left the two targets here that can be invoked manually.
After verifying and doing a check-in, can you modify the Buildbot to do an ant
download-cobertura after the svn checkout (but before the run-install).
Adrian -- I hunted around Apache Commons; but not being very familiar I was not
sure what I was looking for. I looked at IO because it had an old Cobertura
report generated from 2008; but it appears they no longer generate code
coverage that way. Commons Lang has code coverage but they use Bamboo/Clover.
The one build file that had download-dependency target (it was for junit) was
very nice, but all it really did was have their "run-tests" have dependency on
it ...
Whatever we do, if we are going to move the deployment of the jar so it is not
a pre-req for our build, we will have to refactor so we can build our Cobertura
integration pieces after the fact. This could manifest in a
"run-coverage-tests" target, or something else -- but some work would have to
be done.
> 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.
