Which practice should you follow to capture screenshots and illustrate findings while testing?

• A. Start writing the report as you conduct testing
• B. Wait until after testing
• C. Prepare the report only after client asks
• D. Not write anything until review

Answer: (A)

Capturing evidence as you test keeps context intact and creates a verifiable trail. When you take screenshots and log findings in real time, you link each issue to exact commands, outputs, and the system state at that moment, with timestamps and environment details. This makes the final report accurate, reproducible, and easier to audit, and it also smooths the transition into the reporting phase by spreading the workload.

If you wait until after testing, details tend to blur or be forgotten, making reproducibility harder. Delaying documentation until after client requests or review can slow things down and reduce the credibility of the evidence. Documenting as you go helps ensure you have concrete, well-supported findings ready to illustrate in the final report.