Skip to main content
QA Fundamentals

Bug Report

A document describing a software defect with enough detail for a developer to reproduce and fix it.

Full definition

A bug report is a formal document that communicates a defect to the development team. Writing clear, actionable bug reports is one of the most important skills for a QA engineer — a poorly written report wastes everyone's time.

A good bug report template:

  • Title: Short, specific (e.g., 'Login fails with special characters in password')
  • Environment: OS, browser, app version, device
  • Prerequisites: Any setup needed before reproduction
  • Steps to reproduce: Numbered, specific steps
  • Expected result: What should happen
  • Actual result: What actually happens
  • Severity/Priority: How bad is it, how urgent is the fix
  • Attachments: Screenshots, video recordings, logs

Common mistakes: vague titles ('It doesn't work'), missing steps, assuming the developer knows the context, not including environment details.

Interview tip

Many interviews include a practical task: 'Here is a feature — find bugs and write reports.' Practice this with any web app.

Learn more about bug report in practice

Manual Testing track