You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2020/10/11 19:41:00 UTC

[jira] [Commented] (FINERACT-985) Measure integration test code coverage

    [ https://issues.apache.org/jira/browse/FINERACT-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212021#comment-17212021 ] 

Michael Vorburger commented on FINERACT-985:
--------------------------------------------

FINERACT-764 would (probably) gives us this "for free"?

> Measure integration test code coverage
> --------------------------------------
>
>                 Key: FINERACT-985
>                 URL: https://issues.apache.org/jira/browse/FINERACT-985
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Priority: Major
>
> I just realized (this wasn't clear at least to me before) that FINERACT-725 only added code coverage for unit tests. In Fineract that's certainly of some but ultimately more limited value - because the project has very few unit tests, but relies more on integration tests...
> The goal of this new issue to make it possible to have integration test coverage as well.
> Jacoco is easy to set up for unit tests, but for integration tests, we would need to instrument the WAR which the Gradle Cargo plugin deploys into Tomcat - which is a little more challenging... (or we change how we do integration tests all together).
> [~Manthan] [~ptuomola]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)