You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2014/08/04 12:07:13 UTC
[jira] [Commented] (OLINGO-377) Improve infrastructure in FIT for
code coverage support
[ https://issues.apache.org/jira/browse/OLINGO-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084502#comment-14084502 ]
Francesco Chicchiriccò commented on OLINGO-377:
-----------------------------------------------
Hi [~mirbo],
sorry for late reply: the build on Windows is working fine since then, as said by others on the dev@ ML.
As part of the work on the temporary branch {{olingo365}} (which is going to disappear soon), I have also changed {{fit/src/main/resources/log4j.properties}} into {{fit/src/main/resources/log4j.xml}} and tuned a bit to avoid Tomcat's DEBUG statement polluting the log file: any problem with this?
> Improve infrastructure in FIT for code coverage support
> -------------------------------------------------------
>
> Key: OLINGO-377
> URL: https://issues.apache.org/jira/browse/OLINGO-377
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-server
> Affects Versions: V4 4.0.0-beta-01
> Reporter: Michael Bolz
> Assignee: Michael Bolz
> Priority: Minor
> Fix For: V4 4.0.0-beta-01
>
>
> Improve infrastructure in FIT for code coverage support.
> Currently {{maven-cobertura}} plugin can not be used to provide code coverage of full (JUnit) integration tests.
> This should be changed by e.g. running the FIT in a embedded Tomcat and/or instrument the deployed {{fit war file}} and connect cobertura to {{cargo Tomcat}} to get coverage results.
--
This message was sent by Atlassian JIRA
(v6.2#6252)