Quick takeaways

What you will learn

  • Use build a screenshot naming convention as a practical workflow, not just a documentation task.
  • Pair every report with annotated screenshot evidence, environment details, and exact reproduction steps.
  • Keep sensitive test data local by default, then export only the polished evidence your team needs.

Guide format

In this guide

1Pain point testers face 2Step-by-step workflow 3Bug Shot example 4Template or checklist 5Internal links to related QA guides

Problem

Why this matters for qa leads

How to Build a Screenshot Naming Convention is not just a writing exercise. It is a repeatable evidence workflow. When testers capture the right screenshot, write the right title, and include the right environment details, developers spend less time asking follow-up questions and more time fixing the issue.

For qa leads, the biggest pain is usually not finding the bug. The pain is packaging the bug so another person can reproduce it without being present in the same test session. Bug Shot is designed around that exact handoff.

Step by step

A practical Bug Shot workflow

  1. Capture the screen when the defect is visible.
  2. Add an arrow, box, label, or step number to show what failed.
  3. Use the device footer for browser, OS, viewport, and environment details.
  4. Redact private values before the screenshot leaves your machine.
  5. Export PNG, JPG, or Markdown-ready details for Jira and team chat.

Copy-ready structure

Template for the report

How to Build a Screenshot Naming Convention Severity: High or Medium depending on user impact Environment: Browser, OS, device, viewport, build, and test data Steps: Write each action in the same order a developer should retry it Expected: The correct product behavior Actual: The observed failure with screenshot evidence attached

Final QA pass

Checklist before filing

  • Capture the failing state before changing data or refreshing the page.
  • Record browser, OS, device, viewport, build, and environment context.
  • Mark the exact UI element or message connected to build a screenshot naming convention.
  • Redact customer names, tokens, emails, and payment details before sharing.
  • Attach the final screenshot to Jira with expected result, actual result, and reproduction steps.

Tool workflow

How Bug Shot helps

Bug Shot keeps the work local-first and ad-free. The desktop app focuses on screenshot capture, annotation, redaction, resizing, and export. The Chrome and Firefox extensions add browser-context capture. The AI workflow is optional and bring-your-own-key, so teams can decide what stays local and what goes through an approved provider.