Content deleted Content added
copy editing |
copy editing |
||
Line 3:
'''Code integrity''' is a measurement used in software shipping. It measures how high the [[source code]]'s quality is when it is passed on to the QA, and is affected by how extensively (or thoroughly GZ) the code was processed by correctness-checking processes. Examples for such correctness-checking processes can be [[unit tests|unit testing]] and [[integration test]]ing, code review, test automation, AI-based code analysis etc. Code integrity is the combination of applying code correctness processes (software quality) along with metrics that measure the completeness of these correctness-checking processes, such as, for example, code coverage. While code integrity is usually achieved by unit testing the source code to reach high code coverage, it is definitely not the only way, or the best way, to achieve code integrity. In fact, code coverage, a popular metric to measure the thoroughness of unit tests, is known to have a limited correlation with the measure of real code integrity.
==Developer's confidence==
With code integrity, the developer can be sure that his/her code is written correctly when passed on to QA. Code integrity is not just about the correctness of the code, but also about developers’ confidence regarding correctness of their code. 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.
| |||