What screenshots should a QA defect report include?

Before and after the action, an "expected" capture if one exists, and the browser console. Put the environment details in the ticket text.

How do I capture a validation message that disappears?

Trigger the capture from the keyboard the moment it appears, with a tool that does not send a click to the page. Have the shortcut ready before performing the action.

Should I attach the HTML of the page to a layout bug?

Yes. A self-contained HTML snapshot lets the developer inspect the real elements and styles rather than guessing from pixels.

← Back to blog

Screenshots for QA and Testing: Evidence That Holds Up

September 24, 2026

A tester’s screenshot has a specific job: to let someone who was not there reproduce and confirm the problem. That is a higher bar than "look at this". It needs the state, the input, the result, and the environment.

The evidence set

Before -- the screen and inputs immediately prior to the action.
After -- the result, with the wrong part boxed and labelled "actual".
Expected -- a capture of the correct behaviour if one exists elsewhere, labelled "expected".
Console -- the browser console with any errors, from DevTools.
Environment -- browser and version, viewport width, account role; in the ticket text, not the image.

Capturing states that vanish

Validation messages, toasts and loading states disappear on the next click. Have the capture shortcut under your fingers before triggering the action, and fire it from the keyboard the moment the state appears. Demorta’s Ctrl+Shift+8 then Enter captures the visible page without sending anything to it, so a transient state is not dismissed by the capture itself. Try the free screenshot tool.

Attach the page, for layout defects

A screenshot of a misaligned element tells a developer what it looks like; a snapshot of the page as HTML tells them why. Save as HTML in the Demorta bar produces one self-contained file with the real markup and inlined styles. Attach it next to the screenshot for anything visual.

Privacy in test evidence

Test against seeded data so there is nothing to hide. When a defect only reproduces on a real account, pixelate the identifying parts before attaching; bug trackers are read by contractors and integrations as well as the team.

Frequently asked questions

What screenshots should a QA defect report include?: Before and after the action, an "expected" capture if one exists, and the browser console. Put the environment details in the ticket text.
How do I capture a validation message that disappears?: Trigger the capture from the keyboard the moment it appears, with a tool that does not send a click to the page. Have the shortcut ready before performing the action.
Should I attach the HTML of the page to a layout bug?: Yes. A self-contained HTML snapshot lets the developer inspect the real elements and styles rather than guessing from pixels.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →