Bugxy

Bugxy / Browser bug reporting guides

How to report a website bug with clear reproduction steps

A useful bug report gives someone else enough information to reproduce the issue and begin investigating. A screen recording shows the sequence; a few precise details explain what to look for.

Describe the problem in the title

Use the affected feature and the visible failure: “Checkout total increases after applying a coupon” is more useful than “Checkout broken.” Describe what you observed before guessing at a cause.

Include the details needed to reproduce it

  • The page or feature where the issue happens, including whether it is a test or production environment.
  • Relevant starting conditions, such as being signed in or having an item in the cart.
  • Short, numbered steps, with one action per step.
  • The expected result and the actual result, stated separately.
  • Browser and operating system details, plus whether the issue occurs every time or intermittently.
  • A recording or screenshot and any console or network evidence captured during the same attempt.

A sample checkout bug report

This is an illustrative example you can adapt to the issue you observed:

Title: Checkout total increases after applying a coupon.

Starting condition: One item in the cart on the test checkout page.

  1. Open the cart and note the displayed total.
  2. Enter a valid test coupon and select Apply.
  3. Compare the updated total with the original amount.

Expected: The total decreases by the advertised discount.

Actual: The total increases after the coupon is applied.

Evidence: Attach the recording, the browser version, and any relevant request or console error from that attempt.

Record the sequence in Chrome with Bugxy

Follow the Bugxy setup guide to install the extension, sign in, and connect Google Drive. Start recording before the action that triggers the failure, reproduce the issue once, and stop after the result is visible.

Bugxy captures screen video and browser context, including console logs, network requests, and interactions during recording. The video uploads to your connected Google Drive, and the Bugxy report keeps the captured context alongside it.

A recording supplements written steps. Add the expected result, starting conditions, and information about how often the issue happens so someone viewing the report understands the problem.

Review before sharing

Watch the recording and inspect the report before creating a share link. Check that the failure is visible and that the report does not expose confidential account details or unrelated information. Use test data where possible.

Send the report link with the title and a sentence explaining the expected outcome. Report links and recording access depend on the sharing permissions you choose; check access when handing a report to someone outside your team.