Code integrity: Difference between revisions

Revision as of 06:54, 9 September 2021

Revision as of 09:39, 3 November 2022

Line 1:

{{essay-like|date=March 2018}}

'''Code integrity''' is a measurement used in [[software testing]]. It measures the how high the [[source code]]'s quality is when it is passed on to the QA, and is affected by how extensively the code was [[unit tests|unit tested]] and [[integration test]]ed. Code integrity is a combination of code coverage and software quality, and is usually achieved by unit testing your code to reach high code coverage.

With code integrity, the developer can be sure that his/her code is written correctly when passed on to QA. This is, in fact, the expected quality level of the code. Code integrity helps companies release better products, with fewer bugs, in a shorter time.

Line 11:

'''Improve code integrity by:'''

* Unit testing of the code

* Integration testing

* Assigning a code integrity manager

Line 24:

'''Measuring code integrity:'''

To measuring code integrity, use the following formula:1 − (Non-covered bugs) / (Total bugs)

1 − (Non-covered bugs) / (Total bugs)

In words:, the 100% code integrity minus the number of bugs that weren’t covered by unit testing, divided by the total bugs found during the entire product cycle., including development, is the code not in integrity.

{{DEFAULTSORT:Code Integrity}}

[[Category:Software testing]]

== References ==

<references />

{{Software-eng-stub}}