Which approach helps reduce false positives in defect reporting?

• A. Reproduce-facing steps, confirm with multiple environments, and verify with logs and screenshots.
• B. Write vague descriptions and rely on memory.
• C. Report every minor UI glitch without reproduction.
• D. Ignore logs.

Answer: (A)

Reducing false positives in defect reporting comes from providing reproducible steps and solid evidence. When you include exact steps to reproduce, you create a dependable way to observe the issue again, rather than relying on memory or vague descriptions. Verifying the problem across multiple environments helps confirm it isn’t caused by a single configuration, browser, OS, or build, which could mislead teams into chasing a non-existent bug. Attaching logs and screenshots adds objective data: logs show precise errors and timing, while screenshots capture the UI state at the moment of failure. Together, these elements give developers a clear, verifiable picture of what went wrong, making it easier to confirm real defects, reproduce them on their end, and prioritize fixes.

Vague descriptions and reliance on memory lead to ambiguous reports that are hard to validate, so they’re prone to being treated as noise or dismissed as user error. Reporting every minor UI glitch without reproduction creates unnecessary churn without solid evidence, and ignoring logs leaves important context unseen, increasing the time spent diagnosing.