Skip to main content
All CollectionsGetting StartedOnboarding
Common mistakes in Bug Reports
Common mistakes in Bug Reports

Learn what the most common mistakes in Bug Reports are.

Nikola Jonic avatar
Written by Nikola Jonic
Updated over a week ago

Title, URL, Steps, Actual result, Expected result, Attachments, and Used environment are the parts of our Bug Report feature. In this article, you will find the most common mistakes in all sections of the Bug Report form and learn how to avoid them. So let's start!


  • The title is too simple and does not precisely describe the bug.

  • It does not contain the parts: What? Where? When?

  • The title is too confusing for the reader.

When you write a bug title, you need to ensure that you write it in a way so that the reader can immediately understand what the bug is without opening it. Your title should answer the following questions: What is the bug? Where did it happen? When did it happen?

Bad: Become a Tester button does not work.
Correct: There is no reaction after the user clicks on the "Become A Tester" button in the Navigation.

Bad: Data Privacy link is opening a 404 page.

Correct: When the user clicks the "Data Privacy" link in the Footer, an Error 404 page will be opened.

So, in your title, always include the elements: What? Where?, and When?


  • The wrong URL was added when testing a website.

When you add a URL in the URL field, please make sure that you add a URL from a place where the bug happens. So please, always visit the page where the bug happens, copy the URL and paste it into the URL field.


  • The first step does not contain the URL for website tests.

  • There are missing steps.

  • Steps contain "Observe".

  • The information used for testing is not given, like email addresses, passwords, dates and similar.

The most common mistake in the steps is that the first step doesn't contain the website URL of the website under testing. Please always add a URL in the first step when testing a website. Also, other common mistakes are that some steps are missing or some irrelevant steps are mentioned, such as "Observe".

Please note that steps are only actions performed until the bug happens, and the last step should contain the action triggering the bug. So let's see now an example:


  1. User clicked on Crowdtesting

  2. Scroll down - click on about us

  3. Click become a tester at top

  4. Observe


  1. Click on Crowdtesting in Navigation

  2. Scroll down to the Footer and click the About Us link under the "Company"

  3. Click on Become a Tester button in the Navigation

So, as you can see, you always need to be precise and detailed in your steps and only describe the actions performed until the bug happens. Also, you can use the Markdown to make your steps more straightforward.

Actual result

  • The actual result is not describing the bug correctly.

  • The actual result contains too little information about the bug.

  • The actual result contains information about what should be instead of what the bug is.

You must describe the bug in detail when you write the actual result. You need to write precisely what the bug is and when it happens. Also, you must include all other relevant information, such as error messages, etc.

Bad: Become a Tester button does not show implemented functionality.

Correct: No reaction will occur after opening the Test IO website and clicking on the "Become a Tester" button in the Navigation. The user will stay on the same page, and no redirection will occur.

Please always be detailed in your Result description and provide as much relevant information as possible. This will significantly help customers and increase your bug report's chances of being accepted.

Expected result

  • The description is not detailed enough.

  • The description is just the opposite of the Actual result.

  • The description is just the same as the bug report title.

In Expected result, you should write precisely your expectation that the bug did not occur, and here, you need to be detailed. And also, please keep in mind that your Expected result should not be the opposite of your Actual result.

Bad: Become a Tester button redirects to the new page.

Correct: When the user clicks the "Become a Tester" button in Navigation, a new page containing information on how to become a tester on the Test IO platform should be opened.

So, as we already said above, please always be detailed and precise in your Expected result. Write precisely what your expectation is.


For the common mistakes in the attachments, please look at our Common mistakes in Attachments Academy article.

Used environment

  • The wrong device/browser was selected in the bug report.

Please always select the corresponding device and browser so that it matches your screencast/screenshot. After submitting a bug report, you can change this information before the report is reviewed by the team lead. If the wrong device or browser was selected, your report will be rejected.

Did this answer your question?