Shift-left testing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Shift-left testing?

Shift-left testing means starting testing activities early in the software development process, usually during requirements and design phases, to find defects sooner.

beginner

Why is Shift-left testing beneficial?

It helps catch bugs early, reduces cost and effort to fix defects, and improves software quality by preventing problems before coding is complete.

beginner

Which phase is testing moved to in Shift-left testing?

Testing is moved to earlier phases like requirements analysis and design instead of waiting until after coding is done.

intermediate

Give an example of a Shift-left testing activity.

Reviewing requirements for errors or ambiguities before coding starts is a Shift-left testing activity.

intermediate

How does Shift-left testing affect collaboration?

It encourages developers, testers, and business analysts to work together early, improving communication and shared understanding.

What does Shift-left testing primarily focus on?

A Testing only the user interface

B Starting testing early in the development process

C Skipping testing to save time

D Testing only after coding is complete

Shift-left testing means moving testing activities to earlier stages to find defects sooner.

Which phase is NOT typically involved in Shift-left testing?

A Unit testing

B Design review

C Requirements analysis

D Post-release maintenance

Shift-left testing focuses on early phases, not post-release maintenance.

What is a key benefit of Shift-left testing?

A Finding defects late in the process

B Ignoring requirements

C Reducing cost to fix bugs

D Delaying testing until deployment

Finding defects early reduces the cost and effort to fix them.

Which activity aligns with Shift-left testing?

A Code review during development

B Final system testing after deployment

C User acceptance testing only

D Skipping unit tests

Code reviews during development help catch defects early, fitting Shift-left testing.

Shift-left testing encourages collaboration between:

A Developers and testers early in the process

B Only testers after coding

C Users and marketing teams only

D Operations and support teams only

Early collaboration between developers and testers improves quality and understanding.

Explain what Shift-left testing is and why it is important.

Think about when testing happens and its benefits.

Describe some activities or practices that support Shift-left testing.

Consider what testers and developers do before coding finishes.