Skip to contentTalk to us

What does a good bug report contain?

Updated October 12, 2026

The short answer

A good bug report contains six things: a short title that names the problem and where it is, numbered steps to reproduce it, the expected result against what really happened, evidence such as a screenshot or recording, a severity level, and the environment, meaning device, browser, language and the account used. If a developer can reproduce the bug on first read without asking you anything, the report is excellent.

People also ask this as
  • what should a bug report include
  • how to write a good bug report
  • bug report template for a website
  • how do I report a bug to my developer

The six parts, with an example

PartExample
Title'Confirm order' button does nothing on mobile after choosing cash on delivery
Steps1) Add a product to the cart 2) Choose cash on delivery 3) Press confirm
Expected vs actualExpected: a confirmation page with an order number. Actual: nothing happens
EvidenceA screenshot or a short screen recording
SeverityCritical: it blocks the sale
EnvironmentAndroid phone, default browser, Arabic, a new customer account

A weak report and a strong one

Weak
  • 'The site is broken'
  • 'Payment sometimes fails'
  • Three different problems in one message
Strong
  • One problem per report
  • Steps anyone can follow
  • What you expected and what you saw, with a picture

How do you set the severity?

  • Critical: blocks a sale, loses data or exposes customer information.
  • High: a core feature is broken but a workaround exists.
  • Medium: an annoying fault that does not stop the task.
  • Low: a cosmetic note or a typo.

People also ask

How do I test my website before launch?

Test your website before launch in three passes. First, walk through the key flows end to end as if you were a customer: sign-up, ordering and a test payment. Second, open it on a real phone and in two different browsers. Third, review the text, links, forms and error messages. Write down every problem with steps to reproduce, and fix whatever stops a customer from finishing first.

Read the full answer
How do I hire and use an AI QA agent?

Hiring an AI QA agent needs no interviews: pick a tool that runs in a real browser, give it your site address, and tell it in plain words what must work, such as sign-up and completing an order. Review the test cases it proposes, run them, read the report, fix the serious bugs first, and re-test after every fix and before every new release.

Read the full answer
Can it test a site or app I did not build?

Yes. A browser-based QA agent can test any website or web app that has an address, whether a freelancer, an agency or another platform built it, because it works with what the user sees, not with the code. The condition is that the site is yours or you are allowed to test it. This is especially useful when accepting a project from an outside vendor before the final payment.

Read the full answer
AI QA agent or human tester: which should I choose?

Neither replaces the other. An agent never tires or forgets, so it repeats routine flows such as sign-up and ordering after every change, at any hour. A human tester judges taste and context, tries things nobody planned, and notices that wording is off or a step is confusing. A small team starts with an agent for the repetitive checks and brings in a person before big releases.

Read the full answer

Terms used in this answer