Shift-left testing: Difference between revisions

Revision as of 04:06, 22 June 2020

Revision as of 23:05, 25 July 2020

Line 7:

Shift-left testing is important because it helps to prevent the following types of harm due to late testing:

* Testers may be less involved in initial planning, often resulting in insufficient resources being allocated to testing.

* ManyDefects in requirements, architecture, and design defectsremain areundiscovered not uncovered and fixed until afterwhile significant effort has beenis wasted on theirimplementating implementationthem.

* [[Debugging]] (including identifying, localizing, fixing, and regression testing defects) becomes harder as more software is produced and integrated.

* [[Encapsulation (object-oriented programming)|Encapsulation]] makes it harder to performimpedes [[white-box testing]], and to achieve high levels ofreducing [[code coverage]] during testing.{{Citation needed|date=October 2017}}

* There is less time to fix defects found by testing, thereby increasing the likelihood that they will be postponed until later increments or versions of the system,. which This creates a “bow wave” of [[technical debt]] that can sink projects if it grows too large.

== Types of shift-left testing ==