Testing in Scrum sprints in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the Scrum event where testing is planned.

Testing Fundamentals

def scrum_event():
    return "[1]"

Drag options to blanks, or click blank then click option'

ASprint Planning

BDaily Standup

CSprint Review

DSprint Retrospective

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Daily Standup because it happens daily but it is for quick updates, not planning.

The Sprint Planning meeting is where the team plans the work, including testing tasks, for the upcoming sprint.

2fill in blank

medium

Complete the code to show the Scrum role responsible for ensuring testing is done.

Testing Fundamentals

def scrum_role():
    return "[1]"

Drag options to blanks, or click blank then click option'

AProduct Owner

BDevelopment Team

CScrum Master

DStakeholder

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Scrum Master because they facilitate but do not do the testing.

The Development Team is responsible for delivering the product increment, including performing testing during the sprint.

3fill in blank

hard

Fix the error in the code to correctly represent when testing feedback is shared.

Testing Fundamentals

def feedback_event():
    return "[1]"

Drag options to blanks, or click blank then click option'

ADaily Standup

BSprint Retrospective

CSprint Review

DSprint Planning

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Sprint Retrospective which focuses on process improvement, not product feedback.

The Sprint Review is when the team shows the work done and gathers feedback, including testing results.

4fill in blank

hard

Fill both blanks to complete the sentence about testing in Scrum sprints.

Testing Fundamentals

Testing is integrated into the [1] and results are discussed during the [2].

Drag options to blanks, or click blank then click option'

ASprint

BSprint Review

CSprint Retrospective

DBacklog Refinement

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up Sprint Review and Sprint Retrospective.

Testing happens during the Sprint, and the results are shared in the Sprint Review meeting.

5fill in blank

hard

Fill all three blanks to describe the testing process in Scrum sprints.

Testing Fundamentals

During a [1], the [2] plans testing tasks, and the [3] performs the tests.

Drag options to blanks, or click blank then click option'

ASprint Planning

BDevelopment Team

CSprint

DProduct Owner

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing the roles of Product Owner and Development Team.

In Sprint Planning, the Product Owner helps prioritize testing tasks, and the Development Team performs the tests during the Sprint.

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