[
https://issues.apache.org/jira/browse/KAFKA-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281984#comment-14281984
]
Ashish Kumar Singh edited comment on KAFKA-1722 at 1/18/15 10:25 PM:
---------------------------------------------------------------------
If we are open to use something like that, then I guess
[coverall|https://coveralls.io/] is a better option. But again, the concern is
getting scala coverage. I think the best option we have as of now is to go
ahead with what I suggested before. I am sure soon gradle-scoverage will start
publishing scoverage report.
was (Author: singhashish):
If we are open to use something like that, then I guess
[coverall|https://coveralls.io/] is a better option.
> static analysis code coverage for pci audit needs
> -------------------------------------------------
>
> Key: KAFKA-1722
> URL: https://issues.apache.org/jira/browse/KAFKA-1722
> Project: Kafka
> Issue Type: Bug
> Components: security
> Reporter: Joe Stein
> Assignee: Ashish Kumar Singh
> Fix For: 0.9.0
>
>
> Code coverage is a measure used to describe the degree to which the source
> code of a product is tested. A product with high code coverage has been more
> thoroughly tested and has a lower chance of containing software bugs than a
> product with low code coverage. Apart from PCI audit needs, increasing user
> base of Kafka makes it important to increase code coverage of Kafka.
> Something just can not be improved without being measured.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
