Testing in Scrum sprints in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of testing within a Scrum sprint?

The main goal is to ensure that the product increment developed during the sprint meets the agreed requirements and is free of critical defects before the sprint ends.

beginner

When should testing activities start in a Scrum sprint?

Testing should start as early as possible in the sprint, ideally alongside development, to catch defects early and support continuous feedback.

intermediate

How does the Scrum team ensure quality during the sprint?

The Scrum team collaborates closely, with developers and testers working together, using practices like test automation, continuous integration, and regular reviews to maintain quality.

intermediate

What is the Definition of Done (DoD) in Scrum and how does it relate to testing?

The Definition of Done is a checklist that the team agrees on to declare a product increment complete. It usually includes passing all tests, code reviews, and documentation, ensuring testing is part of completion.

intermediate

Why is regression testing important in Scrum sprints?

Regression testing ensures that new changes do not break existing functionality. It is important in Scrum because frequent changes happen every sprint, and regression tests help maintain stability.

When should testing ideally begin in a Scrum sprint?

A At the end of the sprint

B After the sprint review

C Only during the sprint retrospective

D As early as possible during the sprint

Testing should start early in the sprint to find defects quickly and support continuous feedback.

What does the Definition of Done usually include regarding testing?

A All tests are passed and code is reviewed

B Only code is written

C Documentation is skipped

D Testing is optional

The Definition of Done includes passing all tests and code reviews to ensure quality.

Why is regression testing important in Scrum sprints?

A To ensure new changes do not break existing features

B To avoid testing altogether

C To delay the release

D To test new features only

Regression testing checks that existing features still work after new changes.

Who is responsible for testing in a Scrum team?

A Only testers

B The whole Scrum team including developers and testers

C Only the Scrum Master

D Only the Product Owner

Testing is a shared responsibility of the entire Scrum team.

What is a common practice to support testing in Scrum sprints?

A Ignoring defects until the release

B Manual testing only at the end

C Test automation and continuous integration

D Skipping testing to save time

Test automation and continuous integration help catch defects early and maintain quality.

Explain how testing fits into the Scrum sprint process.

Think about when and why testing happens during the sprint.

Describe the role of the Definition of Done in Scrum testing.

Consider how the team decides when work is complete.

Practice

1. In Scrum sprints, when is testing typically performed?

easy

A. Before the sprint starts

B. Only after the entire project is completed

C. During the sprint alongside development

D. Only during the sprint review meeting

Solution

1. Step 1: Understand Scrum sprint workflow

   Scrum promotes continuous integration and testing within each sprint to catch issues early.

2. Step 2: Identify testing timing

   Testing is done during the sprint, not after, to ensure quality and quick feedback.

3. Final Answer:

   During the sprint alongside development -> Option C

4. Quick Check:

   Testing inside sprint = During the sprint alongside development [OK]

Hint: Testing happens during sprint, not after [OK]

Common Mistakes:

• Thinking testing is only after project completion
• Assuming testing is before sprint starts
• Confusing sprint review with testing phase

2. Which of the following is the correct way to describe the role of testers in Scrum sprints?

easy

A. Testers collaborate closely with developers and product owners

B. Testers work independently after developers finish coding

C. Testers only write test cases but do not execute them

D. Testers are not involved until the sprint retrospective

Solution

1. Step 1: Review Scrum team collaboration

   Scrum encourages cross-functional teams where testers, developers, and product owners work together.

2. Step 2: Identify tester involvement

   Testers actively collaborate during the sprint, not isolated or delayed.

3. Final Answer:

   Testers collaborate closely with developers and product owners -> Option A

4. Quick Check:

   Tester collaboration = Testers collaborate closely with developers and product owners [OK]

Hint: Testers collaborate closely in Scrum teams [OK]

Common Mistakes:

• Believing testers work only after coding is done
• Thinking testers only write but don't run tests
• Assuming testers join only at sprint end

3. Consider this scenario in a Scrum sprint:
Bug found during testing on day 3 is fixed on day 4.
Testing continues on day 5 with the fix verified.
What is the main benefit of this approach?

medium

A. Delays the sprint completion

B. Keeps the product healthy by fixing bugs quickly

C. Increases the number of bugs

D. Reduces collaboration between team members

Solution

1. Step 1: Analyze bug fixing timing

   Fixing bugs quickly within the sprint prevents accumulation of defects.

2. Step 2: Understand impact on product health

   Quick fixes keep the product stable and maintain quality throughout development.

3. Final Answer:

   Keeps the product healthy by fixing bugs quickly -> Option B

4. Quick Check:

   Quick bug fixes = Keeps the product healthy by fixing bugs quickly [OK]

Hint: Fix bugs fast to keep product healthy [OK]

Common Mistakes:

• Thinking quick fixes delay sprint
• Assuming bug fixes increase bugs
• Believing quick fixes reduce teamwork

4. A Scrum team notices that bugs are piling up and not fixed during the sprint. What is the most likely cause?

medium

A. Testers are fixing bugs immediately as they find them

B. Sprint backlog is updated regularly

C. Developers and testers collaborate closely

D. Testing is done only after the sprint ends

Solution

1. Step 1: Identify testing timing problem

   If testing happens only after sprint ends, bugs accumulate without timely fixes.

2. Step 2: Understand impact on bug backlog

   Delayed testing causes bug pile-up, harming sprint goals and product quality.

3. Final Answer:

   Testing is done only after the sprint ends -> Option D

4. Quick Check:

   Delayed testing = Testing is done only after the sprint ends [OK]

Hint: Bugs pile up if testing delayed after sprint [OK]

Common Mistakes:

• Assuming immediate bug fixing causes pile-up
• Thinking collaboration causes bugs to pile
• Believing backlog updates cause bug accumulation

5. During a Scrum sprint, the team wants to improve product quality by integrating testing and development. Which practice best supports this goal?

hard

A. Developers and testers collaborate daily to fix bugs quickly

B. Testers write test cases after the sprint is complete

C. Testing is postponed until the sprint review

D. Product owner tests the product alone at the end

Solution

1. Step 1: Identify collaboration benefits in Scrum

   Daily collaboration between developers and testers helps catch and fix bugs early.

2. Step 2: Evaluate timing of testing activities

   Integrating testing during the sprint ensures continuous quality improvement.

3. Final Answer:

   Developers and testers collaborate daily to fix bugs quickly -> Option A

4. Quick Check:

   Daily collaboration = Developers and testers collaborate daily to fix bugs quickly [OK]

Hint: Daily dev-tester collaboration improves quality [OK]

Common Mistakes:

• Delaying test case writing until sprint end
• Postponing testing to sprint review
• Relying only on product owner for testing