Which action best describes a thorough crash reporting process during testing?

• A. Restart and continue.
• B. Ignore and log later.
• C. Record basic notes.
• D. Reproduce, capture logs, crash reports, steps to reproduce, and report with frequency and conditions.

Answer: (D)

A thorough crash reporting process means capturing enough information to reproduce and diagnose every crash. When a crash happens, you should reproduce it to confirm the issue and understand what triggers it. Then collect logs and relevant data—timestamps, device or environment details, app version, and stack traces—and assemble a structured crash report. Include the exact steps to reproduce, the specific conditions under which the crash occurs, and how often it happens. This makes it possible for developers to observe, reproduce, and fix the problem efficiently, and it helps prioritize fixes based on frequency and impact.

Restarting and continuing can hide the root cause, since no details about what triggered the crash are captured. Ignoring the crash and logging information later risks losing essential data and timings, making debugging harder. Recording only basic notes omits the precise steps, data state, and environment details needed to reproduce and resolve the issue.