A Screenshot Is Not Evidence: New Edge Bug Reporting

Fun Doo Testers · 18 November 2026 · 3 min read

Here is a screenshot. It shows an order page with the total at zero. Is that a bug?

Maybe. Maybe the coupon really did make it free. Maybe the price was still loading. Maybe the page had already failed three steps earlier and this is just where somebody happened to notice. Maybe the tester was on a test account where everything costs nothing.

The screenshot can’t tell you. It looks like proof. It feels like proof. But it is one frame cut out of a film, and the important part of the film is usually somewhere else.

What the Picture Leaves Out

A screenshot shows what. Testing is mostly about how and why.

It doesn’t show time. You can’t tell whether the page was finished or still working.

It doesn’t show order. Bugs often come from a sequence: open this, change that, go back, try again. One picture can’t hold a sequence.

It doesn’t show what the browser was doing underneath. Modern web pages are mostly conversations with servers. The request that came back empty, the error thrown in the console, the call that took nine seconds: none of that is on the screen. Yet that is exactly where a developer will look first.

I don’t blame testers for leaning on screenshots. They are fast and everybody understands them. But we should be honest about what they are. A screenshot is a clue. A developer needs a case.

Keep the Whole Film

The fix is not to take more screenshots. The fix is to keep the film.

That is what Captain Octopus does. It’s a free Chrome extension from Pirates of Bugs. You press Start before you begin testing and Stop when you’ve seen enough. While it runs, it keeps the whole moment, not just the last frame:

  • a replay of the page, so you can watch it change, at 1x up to 8x speed
  • your steps, written out in plain English, each with its own screenshot
  • every console log, warning and error, with stack traces
  • uncaught exceptions and unhandled promise rejections
  • network requests with status, timing, headers and bodies

Now look at our zero-total page again. With a recording, the question answers itself. You can scroll back and see that the coupon request returned an error, the page carried on anyway, and the total quietly fell to zero. That is not a clue anymore. That is a bug, with its cause attached.

What I like most is that the screenshots still come along. They just stop being the whole story. Each one sits on a timeline, next to what the user did and what the browser did. That’s when a picture finally means something.

Where to Be Careful

Recording everything raises a fair question: everything including my passwords?

No, and this matters. Captain Octopus keeps all of it on your own computer. There is no account and no upload. It masks passwords, auth headers, tokens, API keys, emails and card numbers by default, and you can add your own rules. A report only goes somewhere when you export it yourself.

The other thing to be careful about is yourself. A good recording can make you lazy. It is tempting to hit Stop, export, and let the developer figure it out. Don’t. The tool keeps the evidence, but it doesn’t know what the evidence means. You still have to say what you expected, why it matters, and who it hurts. That part was always the tester’s job. It still is.

One Small Experiment

Here is what I’d suggest. Next time you find a bug, do it twice. Write it up the usual way, with your screenshot. Then record it with Captain Octopus and send that too. Ask the developer which one they used.

I think I know the answer. But don’t take my word for it. A claim like that deserves evidence too.

Captain Octopus is free, with no account needed. You can get it here: piratesofbugs.com/captain-octopus.