2.1.5 Shift Left (Copilot)

Question 1

Shift Left

Answer 1

The principle of early testing is sometimes referred to as shift left because it is an approach where testing is performed earlier in the SDLC.

Question 2

Shift Left

Answer 2

Shift left suggests that testing should be done earlier, but it does not mean that testing later in the SDLC should be neglected.

Question 3

Good Practices for Shift Left

Answer 3

Reviewing the specification from the perspective of testers to find potential defects such as ambiguities, incompleteness, and inconsistencies.

Question 4

Good Practices for Shift Left

Answer 4

Writing test cases before the code is written and having the code run in a test harness during code implementation.

Question 5

Good Practices for Shift Left

Answer 5

Using CI and CD for fast feedback and automated component tests to accompany source code when it is submitted to the code repository.

Question 6

Good Practices for Shift Left

Answer 6

Completing static analysis of source code prior to dynamic testing, or as part of an automated process.

Question 7

Good Practices for Shift Left

Answer 7

Performing non-functional testing starting at the component test level, where possible.

Question 8

Shift Left Benefits

Answer 8

Shift left might result in extra training, effort and/or costs earlier in the process but is expected to save efforts and/or costs later in the process.

Question 9

Shift Left Importance

Answer 9

It is important that stakeholders are convinced and bought into this concept.