Content deleted Content added
Add: journal, title. | Use this tool. Report bugs. | #UCB_Gadget |
SimLibrarian (talk | contribs) mNo edit summary Tags: Mobile edit Mobile app edit iOS app edit |
||
Line 1:
{{Short description|Measurement used in the software delivery lifecycle}}
'''Code integrity''' is a measurement used in the software delivery lifecycle. It measures how high the [[source code]]'s quality is when it is passed on to [[Quality assurance|QA]], and is affected by how thoroughly the code was processed by correctness-checking processes (whether manual or automatic). 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.<ref>{{cite arXiv |title=A Survey on Machine Learning Techniques for Source Code Analysis |eprint=2110.09610 |last1=Sharma |first1=Tushar |last2=Kechagia |first2=Maria |last3=Georgiou |first3=Stefanos |last4=Tiwari |first4=Rohit |last5=Vats |first5=Indira |last6=Moazen |first6=Hadi |last7=Sarro |first7=Federica |year=2021 |class=cs.SE }}</ref> 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.<ref>{{cite book |chapter=How Effective Are Code Coverage Criteria? |doi=10.1109/QRS.2015.30 |chapter-url=https://ieeexplore.ieee.org/document/7272926 |access-date=15 March 2023 |title=2015 IEEE International Conference on Software Quality, Reliability and Security |year=2015 |last1=Hemmati |first1=Hadi |pages=151–156 |isbn=978-1-4673-7989-2 |s2cid=7305779 }}</ref>
| |||