You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2016/09/23 22:27:20 UTC
[jira] [Updated] (KAFKA-1722) static analysis code coverage for pci
audit needs
[ https://issues.apache.org/jira/browse/KAFKA-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson updated KAFKA-1722:
-----------------------------------
Fix Version/s: (was: 0.10.1.0)
0.10.2.0
> 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 K Singh
> Fix For: 0.10.2.0
>
> Attachments: KAFKA-1722.patch, KAFKA-1722_2015-01-29_12:33:01.patch, Sonar's summary report.png, clients coverage.png, core coverage.png
>
>
> 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)