Shift-left testing: Difference between revisions

Revision as of 22:11, 24 September 2020

Revision as of 11:45, 20 October 2020

Line 34:

=== Model-based shift-left testing ===

The previous forms all concentrated on testing earlier in the development cycle. However, they all test ''after'' software exists and seek to uncover only implementation defects. Model testing theory argues that 45% to 65% of defects are introduced before implementation, during requirements gathering, architecture, and design.<ref>{{cite web|url=http://www.iiste.org/Journals/index.php/CEIS/article/viewFile/3533/3581 |title=Quality Flaws: Issues and Challenges in Software Development |author1=P Mohan |author2=A Udaya Shankar |author3=K JayaSriDevi |lastname-authorlist-ampstyle=yesamp | date=2012 |accessdate=27 March 2015}}</ref>

Model-based testing moves testing to the left side of the Vs, by testing requirements, architecture, and design models. This shift begins testing almost immediately, instead of waiting a long time (traditional testing), medium time (incremental testing), or short time (Agile/DevOps) for software to become available to the right side of the Vs. This trend is just beginning.