(One intermediate revision by the same user not shown)
Line 32:
==Shift-left code integrity enablement==
This concept is based on the fact that developers would be able to make full use of the technological advantage if they have the relevant testing tools available to them from the start. As the newer software become more and more complex and as they includeincludes more dependencies, including the right side of the [[V-model]] in developers' roles will help the them to assume control of the unit testing & integration processes.<ref name="wim">{{cite web |author1=Gadi Zimerman |title=Tests are not enough -– Why code integrity matters? |url=https://www.codium.ai/postblog/tests-are-not-enough-why-code-integrity-matters |access-date=1516 March 2023 |date=2811 FebruaryNovember 20232022}}</ref><ref>{{cite journal |author1=Rook, Paul, E. Rook |title=Controlling software projects |journal=IEEE Software Engineering Journal |date=1986 |volume=1 |issue=1 |page=7-16 |url=https://digital-library.theiet.org/content/journals/10.1049/sej.1986.0003 |access-date=15 March 2023}}</ref> The result will be a more innovative approach to get this done and to get this done, allowingallow developers to bring up complete environments in many software companies. This trend is expected to continue because in many cases it is impossible to perform unit/integration testing without the full system’s context.<ref>{{cite web |title=Effect of Using Continuous Integration (CI) and Continuous Delivery (CD) Deployment in DevOps to reduce the Gap between Developer and Operation |url=https://ieeexplore.ieee.org/abstract/document/9994139 |access-date=15 March 2023}}</ref>
