Bug Report

 Bug Report Document

What is Bug?

A bug is the consequence/outcome of a coding fault. A software defect is an error in coding which causes incorrect or unexpected results from a software program that does not meet actual requirements. Testers might come across such defects while executing the test cases. These defects or variations are referred to by different names in different organizations like issues, problems, bugs, or incidents.

 I f your Bug report is effective, then its chances to get fixed are higher. So fixing a bug depends upon how effectively you report it.





Effective Bug Reporting

Bug reporting is an important aspect of Software Testing. An effective Bug report communicates well with the development team and avoids confusion or miscommunication. 

Bug Report in Software Testing

-Yoger
-Cem Karmer

A Bug Report in Software Testing is a detailed document about bugs found in the software application. The bug report contains each detail about bugs like description, date when a bug was found, name of a tester who found it, name of the developer who fixed it, etc. Bug report helps to identify similar bugs in future so it can be avoided.


In Bug Report there should be some information although it's different in different organizations.

#1) Bug Number/id

#2) Bug Title

#3) Priority

#4) Platform/Environment

#5) Description

#6) Steps to Reproduce

#7) Expected and Actual Result

#8) Screenshot


  2. Bug Title - 
   It should say all about what comes in the bug. A clear bug title makes it easy to understand and the reader can know if the bug has been reported earlier or has been fixed.


Platform/Environment

The environment for every application can vary widely, but be as specific as you can. Testers should always follow the given bug report template unless otherwise specified

The OS and browser configuration is necessary for a clear bug report. It is the best way to communicate how the bug can be reproduced.

  • Device: What type of hardware are you using? Which specific model?
  • OS: Which version number of the OS has displayed the issue?
  • Account Used: This matters if testers are given test accounts by the client. it’s best to then include email + password in the issue report. When the developers get the bug they understand which account was used to discover the issue.
  • Testing App Version: Which version number of the application are you testing? Simply writing “latest version” or “App Store Version” won’t cut it, since some bugs are version-specific and it’s hard to know the app store version when searching the store at a later date – make sure your testers include this specific information.
  • Connection type (if applicable): If the application you’re testing is reliant on Internet connectivity, are you on WiFi, Ethernet, or cellular data? What is the speed of the connection?
  • Reproducibility Rate: How many times have you been able to reproduce the error, using the exact steps you’ve taken to activate the bug? It’s also useful to report how many times the bug has been reproduced vs. the number of attempts it’s taken to reproduce the issue, in case it’s an intermittent occurrence.
  •  Description

Bug description helps the developer to understand the bug. It describes the problem encountered. The poor description will create confusion and waste the time of the developers and the testers as well.

     Steps to Reproduce

We number our steps from beginning to end so developers can easily follow through by repeating the same process. We prefer to keep step numbers relatively whittled down by using the “>” symbol.

Example description for steps to reproduce a bug:

1. Go to settings > Profile (this would take user to new screen)
2. Tap on More Options > Delete Account

This way you can provide more process information that leads to the next step without having a reproduction list that appears tediously long. Remind your testers that implied steps aren’t necessary either, like “Open App” and “Login,” unless the issue relies directly upon these actions being taken.

      Severity/Priority

Sharing the severity offers a degree of impact the bug has on the functionality of the system and helps the dev team prioritize their work.

1. High/Critical: anything that impacts the normal user flow or blocks app usage
2. Medium: anything that negatively affects the user experience
3. Minor: ALL else (e.g., typos, missing icons, layout issues, etc.) 






Comments

Post a Comment

Popular posts from this blog

Exploratory testing & SBTM

Image
 Exploratory Testing  Exploratory testing is also known as ad hoc testing and was known solely by this term until the early 1990s when a group now called the “Context-Driven School” started using the term exploratory.  Cem Kaner  was the person that coined the term Exploratory Testing in his book “Testing Computer Software” and described it as: “Simultaneous test design, test execution and learning with an emphasis on learning” According to the different site, I found different definitions for exploratory testing- In exploratory testing, testers do not work on the basis of previously created test cases. They check a system without a plan in mind in order to discover bugs that users may face when navigating a website or app without a specific aim or direction in mind. Exploratory testing” – as the name suggests, is simultaneous learning, test design, and test execution process. We can say that in this testing test planning, analysis, design, and test execution, a...
Read more

Accessibility testing tool - Bootcamp

Image
                                  Wave Accessibility tool WAVE is a web accessibility evaluation tool developed by WebAIM.org. It provides visual feedback about the accessibility of your web content by injecting icons and indicators into your page. No automated tool can tell you if your page is accessible, but WAVE facilitates human evaluation and educates about accessibility issues. All analysis is done entirely within the Chrome browser allowing secure valuation of intranet, local, password protected, and other sensitive web pages. To run a WAVE report, simply click on the WAVE icon to the right of your browser address bar, or select "WAVE this page" from the context menu. Steps to verify the accessibility of the website Step #1)  Click on URL: http://wave.webaim.org/ Step #2)  Enter the  Web page address  in the  text   box  and hit enter. Example. So enter the sit...
Read more

API Tresting - DAY 1

Image
  30days of API testing challenges -  Define what API testing is, share your definition on The Club API - stands for the application programming interface. They are basically a collection of functions and procedures, which allows us to communicate two applications or libraries.   What is API Testing? API TESTING  is a software testing type that validates Application Programming Interfaces (APIs). The purpose of API Testing is to check the functionality, reliability, performance, and security of the programming interfaces.  API -Let's explain each of these terms to better understand: - " Application ": An application is a service accessible by a human or computer program. Ex: Facebook is a social network application, Spotify is an audio streaming application, PlanningPME a planning application. - " Programming ": a program is a set of computer functions written by a developer who performs tasks in his place. Ex: If I want to transform postal addresses i...
Read more