Bug report writing in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key elements in a bug report

Which of the following is NOT a necessary element to include in a clear and effective bug report?

A Personal opinion about the developer

B Expected and actual results

C Steps to reproduce the bug

D Environment details like browser or OS version

💡 Hint

Think about what information helps fix the bug versus what is irrelevant or unprofessional.

A good bug report focuses on facts and reproducible details. Personal opinions about developers do not help solve the issue.

❓ assertion

intermediate

Correct priority assignment in bug reports

You find a bug that causes the application to crash every time a user tries to save data. What is the correct priority level to assign in the bug report?

A Low priority

B No priority needed

C Medium priority

D High priority

💡 Hint

Consider how severely the bug affects the user experience and application functionality.

A bug causing application crashes on a common action should be assigned high priority to fix quickly.

🔧 Debug

advanced

Identifying missing information in a bug report

Review the following bug report excerpt and identify what critical information is missing:

Title: Login button not working
Description: Clicking the login button does nothing.
Steps: 1. Open app 2. Enter username and password 3. Click login button
Expected: User should be logged in
Actual: Nothing happens

A The time of day the test was done

B The version of the app or browser used

C The color of the login button

D The username and password used

💡 Hint

Think about what environment details help developers reproduce the bug.

Knowing the app or browser version is essential to reproduce and fix the bug. User credentials should not be shared for privacy. Button color and test time are irrelevant.

❓ framework

advanced

Using bug tracking tools effectively

Which feature of a bug tracking tool helps avoid duplicate bug reports and improves team communication?

A Automatically closing bugs after 24 hours

B Hiding bug reports from testers

C Linking related bugs and adding comments

D Assigning bugs to multiple developers simultaneously

💡 Hint

Think about how teams keep track of similar issues and share updates.

Linking related bugs and adding comments helps avoid duplicates and keeps everyone informed. Assigning to multiple developers or hiding reports causes confusion. Auto-closing bugs too soon risks losing important issues.

❓ Predict Output

expert

Output of bug report status transitions

Consider this simplified bug report status flow code snippet:

status = "Open"

match status:
    case "Open":
        status = "In Progress"
    case "In Progress":
        status = "Resolved"
    case "Resolved":
        status = "Closed"
    case _:
        status = "Unknown"

print(status)

What will be printed when this code runs?

A In Progress

B Resolved

C Open

D Closed

💡 Hint

Look at the initial status and which case matches first.

The initial status is 'Open'. The match-case changes it to 'In Progress'. So the printed output is 'In Progress'.