Code integrity: Difference between revisions

Revision as of 04:19, 24 August 2018

Revision as of 15:24, 15 January 2020

Line 3:

'''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.

Companies who practice code integrity avoid the classic scenario where the development stage is delayed, delaying the QA stage, delaying the release stage. The product is released with more bugs (due to time pressure), users report tons of bugs back to the development team, and they start working on version 1.1 shortly after releasing version 1.0, just to fix bugs that could have been avoided.