How to Report a Bug | spriteCloud

So how do you report a bug?

Guiding Principles

  • Be precise
  • Be clear: explain how to reproduce the problem, step by step, so others can reproduce the bug
  • Include only one problem per report

Environment

  1. The version of the software you’re testing. If not available, provide the date and time at which the bug occurred.
  2. The operating system on which you’re running the software, with version number and what service packs/updates are applied.
  3. If the software is a web application, include also the exact browser version you’re using when you encounter the bug.

Steps to Reproduce

  1. I log in with my business account.
  2. I click on the “foo” tab in the left-hand navigation.
  3. I select “bar” from the “quux” drop-down list.
  1. Report the shortest path you need to take, for easier reproduction.
  2. Mention after the steps you documented whether there are other paths that lead you to the bug. If necessary, the developer can ask you for feedback on them.

Expectations vs. Reality

Extra Information

  1. Take a screenshot of the error and attach it. A picture says more than a thousand words.
  2. If you need to use file data in your error case, make sure all those files are attached. There may be sensitive information in the files; if so, try reproducing the error with a file that does not contain sensitive data.
  3. Report anything else that’s unusual. Does the error only occur on certain days or at certain times? Is there something else that you’re always doing when the bug occurs?
  4. Are there any error messages or error information outside of the app you’re using? Do you have a crash report? Add all of that.

Structured English/Gherkin

Given I logged in with my business account 
When I click on the "foo" tab in the left-hand navigation
And I select "bar" from the "quux" drop-down list
Then the main document view should show the "quux" data
And the main document view should not show an endless loading animation
  1. Use Given to list preconditions.
  2. Use When to list all actions you take.
  3. Use Then to list your expectations and the outcome.
  4. Finally, use And whenever a precondition, action or expectation/outcome consists of multiple parts.

Final Thoughts

--

--

--

We’re spriteCloud, a community of software quality assurance and cybersecurity testers located in Amsterdam. Put quality first!

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Being Strong Has Nothing to Do With Who Lives or Dies

Introduction to OpenCascade and CAD modelling kernels

Beginner’s Understanding of Patterns Related to Microservices

TRON 2021 Global DeFi Hackathon Developer Contest Application Guide

How to ‘Hackathon’ when you don’t ‘do’ code

Veritas CPS Değişim Çalışması

The Scrum Mythbusters Exercise

In Search Of … WebAssembly

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
spriteCloud

spriteCloud

We’re spriteCloud, a community of software quality assurance and cybersecurity testers located in Amsterdam. Put quality first!

More from Medium

4 Phases of Enterprise Application Testing to Expect for Easier Planning

Two-Factor Authentication using Face Recognition

What Is Oracle Functional Testing?

#7 How we work — Functional Testing