Who decides whether a bug will be accepted or not? – The team leader, the customer?

No! The quality of your bug is crucial! If you do not submit your bug correctly, often we cannot reproduce the bug and have to reject it. In order to get payed, you should really submit your bugs meticulously.

That’s how it works:  

A Bug needs a meaningful titel. The first thing, the team leader and the customers sees, is the bug titel, so choose it wisely. It should not be too long, but precisely describe your bug in a few words, so that we instantly know what kind of bug you found. To guarantee that, each title should cover the following: type of bug and where it appeared.

The URL you insert should be the one you find in the browser, while your on the site with the bug. You simply have to copy and paste it then.

Very important are the steps taken to understand the bug. Those who work sloppy here, risk to lose their bug, because it is not reproduceable.

When naming the steps taken, always start with same step: “Go to the homepage.” It should be possible to find the bug starting from the homepage.

The more steps you name, the easier it will be to reproduce the bug and the more positive you can be that the team leader and customer will find your bug. But cut it short.

You can state the expected, as well as the actual result in a few short sentences. In this part you can explain your bug more in detail.

The label function is used to group the bug. You can find a list of label functions in an other blog entry. As all bugs are different, you can also insert new label functions.

You will be asked to categorize you bug. The categories are: Critical, High and Low. Please keep in mind that critical means that the bug needs to be fixed immediately. Find more information in the blog entry “Bug Categories”.

Finally name the browser you used and do not forget to upload a screenshot!