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!
Title
The title is too generic and does not clearly describe the bug.
The title does not contain enough information to understand the issue or distinguish it from other bug reports.
The title is unclear or confusing for the reader.
When writing a bug title, make sure the reader can understand the general idea of the issue without opening the report. A good title contains the necessary information to understand the bug and distinguish it from other bug reports. The necessary information includes what happened, where the bug occurred, and when, how, or under which conditions it was triggered.
Examples:
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.
URL
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.
Steps
The first step does not contain the URL for website tests.
There are missing steps.
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.
Please note that steps are only actions performed until the bug happens, and the last step should contain the action triggering the bug.
Let's see an example:
Bad:
User clicked on Crowdtesting
Scroll down - click on about us - click become a tester
Go down, click register
Correct:
Go to https://test.io/
Click on Crowdtesting in the Navigation
Scroll down to the Footer and click the About Us link under the "Company"
Click on the 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.
Example:
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.
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.
Example:
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.
Attachments
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.