Retrospective and process improvement in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of a Retrospective Meeting

What is the main purpose of a retrospective meeting in a software testing team?

A To write detailed test cases for the upcoming release

B To assign new testing tasks for the next sprint

C To review completed work and identify ways to improve future testing processes

D To report bugs found during testing to the development team

💡 Hint

Think about what helps a team learn and improve after finishing work.

A retrospective meeting is held to reflect on what went well and what can be improved in the testing process. It helps the team continuously improve.

❓ assertion

intermediate

Valid Assertion for Retrospective Outcome

Which assertion correctly verifies that a retrospective meeting resulted in at least one process improvement action?

Testing Fundamentals

actions = ['Improve test case review', 'Automate regression tests']
# Write assertion here

A assert len(actions) > 0

B assert actions == []

C assert actions is None

D assert len(actions) == 0

💡 Hint

Check if the list of actions is not empty.

The assertion assert len(actions) > 0 confirms that there is at least one improvement action recorded.

🔧 Debug

advanced

Debugging a Retrospective Action Logger

The following code is intended to add a new improvement action to the list only if it is not already present. What error or issue will occur when running this code?

Testing Fundamentals

def add_action(actions, new_action):
    if new_action not in actions:
        actions.append(new_action)
    return actions

actions = ['Improve test coverage', 'Automate regression tests']
result = add_action(actions, 'Improve test coverage')
print(result)

A No error; the list remains unchanged because the action already exists

B Raises TypeError because 'actions' is not a list

C Raises SyntaxError due to missing colon

D Adds duplicate action to the list

💡 Hint

Check if the function prevents duplicates correctly.

The function checks if the new action is already in the list before adding it, so no duplicates are added and no error occurs.

❓ framework

advanced

Choosing a Retrospective Technique

Which retrospective technique focuses on identifying what went well, what didn’t, and what can be improved, using a simple three-column board?

A Fishbone Diagram

B Start-Stop-Continue

C 5 Whys Analysis

D SWOT Analysis

💡 Hint

Think of a technique with three clear categories for feedback.

The Start-Stop-Continue technique uses three columns to gather feedback on what to start doing, stop doing, and continue doing.

❓ Predict Output

expert

Output of Retrospective Feedback Aggregation

What is the output of the following code that aggregates feedback from multiple retrospective meetings?

Testing Fundamentals

feedbacks = [
    {'start': ['Write more tests'], 'stop': ['Manual regression'], 'continue': ['Daily standups']},
    {'start': ['Automate deployment'], 'stop': ['Late reporting'], 'continue': ['Daily standups']},
    {'start': ['Write more tests'], 'stop': ['Manual regression'], 'continue': ['Code reviews']}
]

aggregated = {'start': set(), 'stop': set(), 'continue': set()}
for fb in feedbacks:
    for key in aggregated:
        aggregated[key].update(fb[key])

print({k: sorted(list(v)) for k, v in aggregated.items()})

A {"start": ["Automate deployment"], "stop": ["Late reporting"], "continue": ["Code reviews"]}

B {"start": ["Write more tests"], "stop": ["Manual regression"], "continue": ["Daily standups"]}

C {"start": [], "stop": [], "continue": []}

D {"start": ["Automate deployment", "Write more tests"], "stop": ["Late reporting", "Manual regression"], "continue": ["Code reviews", "Daily standups"]}

💡 Hint

Look at how sets combine unique items from all feedback dictionaries.

The code collects unique feedback items from all meetings into sets, then sorts them into lists for output.