Skip to main content

How to write a detailed Bug report?

Welcome to Software Testing Techie Blog!



Bug report sounds familiar, right? As testers, we all create one or more than one bug report in our everyday work but what mostly matters is how detailed do we create them? What details we put in and how other teams get benefit out of it.

BUG!!

I am going to share an example related to detailed bug report and how it affects the quality. Detailed bug report is one of the best gift you can give to your and also to development team.

Let's see how:

A detailed bug report should have 4 major things namely severity, steps to reproduce, expected result and actual result. There could be other fields depending on what defect tracking tool you are using for example, testing estimate, test cases reviewer etc.

Consider an easy example where user logs into a website and found that home screen is distorted. So Let's define all above 4 major areas:

1. Severity: Since it is related to Home screen which is the most important part of any application and can lead to bad user experience so severity should be set as "High or Highest".
2. Steps to reproduce: This is the area where you need to have a balance of words. It should not be so verbose that people get annoyed reading the whole thing and should not be incomplete at the same time. For the above example, steps to reproduced would be:


It is short and simple plus covers all the steps. Now the 3rd detail which is expected result.
3. Expected result: This is the field where you have to refer the requirement document (If there is an id for it) and give them the exact line number where it is mentioned that "how home screen should look". For example in above example, we can state that "Text of the Home Screen and Icons should be properly displayed", notice that expected result contains "should or must" since they are related to the requirements and should be followed by exact words defined in the requirements.
4. Actual result: This is the area where you have to exactly defined what you see. For our example, you can state that "All the Texts and Icons present on Home Screen are distorted". And also, you can attach a screenshot showing the real issue for reference. Visuals are more understandable than theory.

If the bug report is not detailed then development team might find it difficult to understand the bug and hence the quality of the fix will be affected. When all the steps are clearly defined, screenshots or other reference documents are attached and expected result is clear, bug can't stay for longer :)
Labels:

Comments

Post a Comment

Share your feedback

Popular posts from this blog

Remove Blanks from Excel Sheet when Excel doesn't recognize field as blank

This is one of the tricks which always helped me in removing the blank fields from an Excel sheet especially when the values are copied from other sources. I have added screenshots of a sample data to show you all the actions step by step. Here are the steps to remove blanks by using one of the special functions in excel: 1. Select your data-set (Select the column which has blank values) 2. Press F5 3. Select "Special". You will see below screen: 4.Select Blanks and click Ok as shown 5. All the blank fields are now selected, you can proceed and delete all of them by selecting "delete" from the home menu.   Here is the final result: I hope this was helpful. Share this with your colleagues and friends to help them out.
Post a Comment
Read more

Benefits of Early and Frequent Feedback in Agile development

One of the reasons why Agile is preferred over traditional development method is "Early and Frequent Customer Feedback". This is not only helps customer to get what he wants but also helps development team to understand the requirement better. There is no room for misunderstandings and delays. so no BAD CUSTOMER SERVICE! In this post, I am going to discuss about some of the major benefits of early and frequent feedback in Agile. One way to get the early feedback is "CI" or Continuous Integration. There are many tools available in the market like Jenkins which help in running automated tests when a change is introduced in the build and give the feedback on the build performance or quality. Below are some of the advantages of early and frequent feedback: Early and regular feedback helps in clearing out the misunderstanding of the requirements. Unlike in traditional method, fixing the issues or requirements change is a lot less expensive. Customer get to see the...
Post a Comment
Read more

Role of a Tester in an Agile Team

Tester in agile is no different from that of traditional tester but in agile, he has to play multiple roles apart from just testing the software. In this post, we are going to discuss about the role of a tester in a project following a scrum life cycle. To make a project successful, testing plays a vital role. In agile, the main idea is whole team approach where testers, developers and business representatives work together as a team. Below are some of the main roles or best practices followed by team members in an agile (Scrum) environment: Cross-Functional: Every team has team members with a specific skill set which they bring to the table. The team work together on Test strategy, Test plan, Test execution and evaluation. Quality is a shared responsibility.  Self-Organizing : There are no leads in Agile. Team is self organized, meaning every team member knows and understands his responsibility and work accordingly.  Co-located : In most of the cases, testers, de...
Post a Comment
Read more