Testing in Scrum sprints in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

When should testing activities ideally start in a Scrum sprint?

In Scrum, when is the best time to begin testing during a sprint?

A Continuously from the start of the sprint alongside development.

B After the sprint review meeting is done.

C Testing is done only in a separate sprint after development finishes.

D Only after the development team completes all coding tasks.

💡 Hint

Think about how Scrum encourages collaboration and quick feedback.

Testing should start early and continue throughout the sprint to catch issues quickly and support continuous delivery.

🧠 Conceptual

intermediate

What is the role of the Definition of Done (DoD) in Scrum testing?

How does the Definition of Done (DoD) relate to testing in Scrum sprints?

A It defines the criteria that must be met, including testing, before a product increment is complete.

B It replaces the need for any testing documentation.

C It schedules when testers should start their work.

D It lists the testing tools to be used in the sprint.

💡 Hint

Consider what 'done' means for a product increment in Scrum.

The DoD includes testing criteria to ensure the product increment is fully tested and ready before it is considered complete.

❓ framework

advanced

Which Scrum event is best suited for discussing testing progress and issues?

During which Scrum event should the team discuss testing progress, blockers, and quality concerns?

A Sprint Planning

B Sprint Retrospective

C Sprint Review

D Daily Scrum (Daily Standup)

💡 Hint

Think about the daily meeting where the team shares updates and obstacles.

The Daily Scrum is the event where team members share progress and blockers, including those related to testing.

❓ assertion

advanced

What is the expected outcome if testing is delayed until the end of a Scrum sprint?

What is the most likely result if testing is postponed until the last days of a sprint?

A Faster delivery because testing is done all at once.

B Increased risk of bugs and reduced time to fix them before sprint ends.

C Better quality because testers have more time to focus.

D No impact on sprint goals or quality.

💡 Hint

Consider how late testing affects bug discovery and fixing time.

Delaying testing increases the chance of finding bugs late, leaving little time to fix them and risking sprint goals.

🔧 Debug

expert

Identify the main testing-related issue in this Scrum sprint scenario

A Scrum team completed development and testing tasks in the sprint backlog. However, during the sprint review, many defects were found by stakeholders. What is the most likely cause?

A The team did not include testing tasks in the sprint backlog.

B Testing was done only by developers without involving testers or automation.

C Testing was not integrated continuously and was rushed at the end of the sprint.

D The product owner did not attend the sprint review.

💡 Hint

Think about how testing timing and integration affect defect detection.

Rushing testing at the end reduces thoroughness and misses defects, causing many issues to appear during review.

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