Exploratory Testing Defect Investigation and Reporting 2

Question 1

What is 'severity' in the context of defect reporting?

Accepted Answer

The impact of the defect on the system's functionality or users

Answer

Severity measures how much the defect impacts the system — from minor visual glitches to complete system crashes.

Question 2

How does 'priority' differ from 'severity' in a defect report?

Accepted Answer

Priority is about when the bug should be fixed; severity is about how bad the impact is

Answer

Severity describes the technical impact; priority reflects business urgency — a low-severity bug may be high priority if it affects the product's image.

Question 3

What evidence should an exploratory tester typically attach to a defect report?

Accepted Answer

Screenshots, screen recordings, and relevant log files

Answer

Visual evidence (screenshots, recordings) and logs give developers the context they need to understand and reproduce the defect.

Question 4

What is 'regression' in the context of defect management?

Accepted Answer

A defect that was previously fixed but reappeared in a later build

Answer

A regression is when a previously working feature breaks again, typically due to a new code change.

Question 5

Which of the following best demonstrates effective 'actual vs. expected' documentation in a bug report?

Accepted Answer

Actual: Application crashes when saving with empty name field. Expected: Validation message appears.

Answer

Precise actual vs. expected descriptions give developers clear criteria to reproduce the failure and know what correct behavior looks like.

Exploratory Testing Practice Test

Exploratory Testing Practice Test

Exploratory Testing Defect Investigation and Reporting 2