Content deleted Content added
copy editing |
|||
Line 4:
==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 developers and 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.
Line 28:
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.
== References ==
| |||