All posts

Bug reports testers can act on: screenshots and steps

· 8 min read

"It doesn't work" is the most common bug report, and the least useful. The maker can't see your screen. They don't know your phone, your version or what you tapped. They write back with questions, you answer a day later, and the bug waits. A good report takes two extra minutes and saves days. This post shows what to put in a report, how to capture a screenshot or a recording on each device, and how to keep your private data out of it.

What makes a bug report usable

The maker needs to see the same bug on their own screen. Give them these things:

  • A clear title. One line. "Save button does nothing on the profile screen" beats "Bug".
  • Steps to reproduce. Numbered, from a clean start. Name the buttons you tapped and the text you typed.
  • Expected vs actual. What you thought would happen, and what did happen.
  • Device, OS and app version. For example "iPhone 13, iOS 18.2, v3". The same bug can happen on one phone and not another.
  • Connection. Wi-Fi, mobile data or weak signal. See testing on a slow network for why this matters.
  • A screenshot or a recording. A picture of the error, or a short video of the steps.
  • How often. Every time, one time in three, or once only? A bug that happens every time is easy to fix. A rare one needs more clues.

If you can only give three things, give the steps, what you expected and what happened. The rest helps, but those three are the core.

Screenshot or recording?

A screenshot is best for something you can see: a wrong label, a broken layout, an error message. A recording is best for something that moves or takes steps: a screen that flickers, a button that is slow, a flow that goes wrong on the third tap. When unsure, send a short recording. Keep it under a minute and stop as soon as the bug shows.

iPhone and iPad

I read Apple's pages on 11 November 2026. In Take a screenshot on your iPhone, the step for a Face ID model is "Press the side button and the volume up button at the same time." Then you "Quickly release both buttons." On a model with a Home button, you press the side button and the Home button at the same time. Screenshots are saved to your Photos app, in the Collections section, under media types.

For video, Apple's Record the screen on your iPhone, iPad, or iPod touch says to swipe down from the top-right corner of your screen to open Control Center. Tap the gray Record button and wait for the three-second countdown. If the button is not there, add it to Control Center first. To stop, tap the Screen Recording button at the top of the screen and then tap Stop, or tap the red Record button in Control Center. The recording is in Photos.

Android

Google's Android Help page on screenshots and screen recording, which I read on 11 November 2026, says to "Press the Power and Volume down buttons at the same time." If that does not work, press and hold the power button and tap Screenshot. For a recording, swipe down twice from the top of the screen, tap Screen record (you may need to swipe right to find it), choose what to record and tap Start. To stop, swipe down from the top and tap the screen recorder notification. The page says to find files in the Photos app under Collections, then On this device. Older Android versions without Photos use the Gallery app. Phone makers differ, so if the buttons do nothing, search for your phone's name and "screenshot".

Mac

Apple's Mac pages, read on 11 November 2026, give three shortcuts. In Take a screenshot on your Mac: Shift-Command-3 takes the whole screen, and Shift-Command-4 lets you drag to choose a part of the screen. Shift-Command-5 opens the Screenshot app. By default, screenshots save to your desktop.

For video, the Mac screen recording page says to open the Screenshot app by pressing Shift, Command and 5 together, which shows a toolbar with controls for still images and for video. To stop, "click the Stop button in the menu bar, or press Command-Control-Esc". By default, recordings are saved to your desktop.

Windows

Microsoft's Snipping Tool page, read on 11 November 2026, says Windows logo key + Shift + S opens the snipping overlay to capture an image. The snip is saved to your Screenshots folder. The same page says Windows logo key + Shift + R opens the overlay for a video clip. You choose the area, select Start, and select Stop when you are done. Then you can save the recording or edit it in Clipchamp. The page does not say where video files are saved, so check the save prompt.

Web apps: URL and console

For a web app, write down the exact page. Copy the URL from the address bar and paste it in the report. If the bug only shows after some steps, say so in the steps.

Browser errors are very useful to a developer. Google's Console reference for Chrome DevTools, read on 11 November 2026, says to press Control+Shift+J, or Command+Option+J on Mac, to open the Console. Reproduce the bug, then look for red error lines. To copy one, right-click it and pick one of the copy options. "Copy string contents" copies the raw text. To get everything, right-click an empty space in the Console. "Copy console" copies all current messages to the clipboard, and "Save as..." saves them to a plain-text .log file. Paste the error text into the report. A pasted error is easier to search for than a screenshot of it.

Keep private data out

Screenshots and recordings often show more than you meant to share: your name, email address, a phone number, notifications from other apps, a map location. Before you send:

  • Crop the picture to the part that shows the bug.
  • Blur or cover names, emails, addresses and anything else personal. Most phones can mark up a screenshot after you take it.
  • Check notifications. A message from a friend can slide in during a recording. Turn on Do Not Disturb first.
  • Never send a password, a code or a login token, not in text and not in a picture. If the bug needs a login, make a test account, or ask the maker for one.
  • Use a link with care. If you share a recording by link, make sure only people with the link can open it, and delete it later.

For makers: ask for it in the test task

Testers will send better reports if you ask. In the test task, add two lines: "Please attach a screenshot or a short recording if something breaks" and "Tell me your device and OS version." If you have more than one build, ask for the version too. For wording, see how to write a test task. For phones you don't own, see testing on phones you don't own.

Once reports come in, group the same bug together, and rank by how often it happens and how bad it is. The beta feedback triage post shows how to turn them into a fix list. If a report is missing something, write back with one question, not five. Thank the tester. They gave you their time.

A bug report template

Copy this, and fill it in:

Title: [one line: what breaks, and where]

Steps to reproduce:
1.
2.
3.

Expected: [what you thought would happen]
Actual: [what happened, with any error text]

Device and OS: [e.g. Pixel 7, Android 14]
App version or build: [e.g. v3]
Connection: [Wi-Fi / mobile data / weak signal]
Page URL (web apps): [paste it]
How often: [every time / sometimes / once]
Screenshot or recording: [attached, or a link]

The bug report checklist

  1. Is the title one clear line?
  2. Are the steps numbered, and can someone else follow them?
  3. Did you write what you expected and what happened?
  4. Are your device, OS and app version in the report?
  5. Did you say whether you were on Wi-Fi or mobile data?
  6. Did you say how often it happens?
  7. For a web app, did you paste the URL and any console error?
  8. Is there a screenshot or a short recording?
  9. Did you crop or blur personal data?
  10. Is there no password or code anywhere in the report?
  11. (Makers) Does your test task ask for a screenshot or recording, and for device and OS?

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps: you test someone's app, they test yours. You can post web, iOS and Android apps. A review has two public parts: a first impression, and what is missing or what to improve. There is also an optional private box called "Bugs / security" that only the maker sees. The maker then rates your review, so a clear report is worth the effort.

The review form takes text only. It has no place to upload a screenshot or a recording, and I won't pretend it does. So describe what you captured, and if you have a recording, put a link to it in the private bugs box. Paste the console error there too. The box has a limit of 2,000 characters, so keep the template short.

Try it

Next time you find a bug, fill in the template before you send anything. Then post your app on TestSwap, ask for a screenshot or recording in your test task, and review someone else's app to see how it feels from the other side. Tell me what's missing or broken (@dizid on X).