Code integrity: Difference between revisions

Revision as of 09:02, 17 October 2024

Revision as of 09:05, 17 October 2024

Line 6:

==Shift-left testing and shift-left code integrity==

Companies whothat practice code integrity avoid the classic scenario where the development stage is delayed, delaying the QA stage, delaying the release stage. Products of companies that do not adopt code integrity are 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.{{citation needed|date=March 2023}}

Shift-left testing is a method to perform related testing during the initial processes of software development, since the QA department cannot measure the code's integrity even after all their tests are run. Shift-left testing and code integrity are tightly connected but integrity consists not only of the testing part of the job which is a sub-task of the larger process of shift-left code integrity. This process not only applies more unit tests along with higher code coverage, but also involves various other correctness-checking processes against relevant data.<ref>{{cite book |chapter=High Level Test Driven Development – Shift Left |doi=10.1007/978-3-319-18612-2_23 |chapter-url=https://link.springer.com/chapter/10.1007/978-3-319-18612-2_23 |access-date=15 March 2023 |title=Agile Processes in Software Engineering and Extreme Programming |series=Lecture Notes in Business Information Processing |year=2015 |last1=Bjerke-Gulstuen |first1=Kristian |last2=Larsen |first2=Emil Wiik |last3=Stålhane |first3=Tor |last4=Dingsøyr |first4=Torgeir |volume=212 |pages=239–247 |isbn=978-3-319-18611-5 }}</ref> Here are some examples:{{cn}}