This post was most recently updated on June 17th, 2019
What is software bug? What does software bug mean?
Software bug is flaw in coding due to which a program/s or an application fail to give the desire output. Software bug can be an error, defect, failure or fault which may cause due to software program deviate from what it supposed to behave.
Why software bug found?
There are many reasons when you found bug in a software application. Below is the list which might be some of the reasons due to which bugs may occur –
- Misunderstanding of requirement by Lead and same has been delegated to the development team
- Frequently changing requirements
- Wrong design flow prepared by designer
- Mistakes in coding
- Software is behaving what it not supposed to or not behaving what it should supposed to.
- If quality of software testing is poor
- Environment related issue because of deployment.
How to raise a bug more specifically?
When a software tester raised a bug he/she should keep some points in mind which may help developer to resolve the bug and the same bug does not occur again. The bug raising should be systematic process.
Here are some points which might help to raise a bug systematically
- Title – The title of the bug should be short and self-explanatory.
- Date – The date on which the bug has been logged
- Environment – The platform or browser and the OS user used while testing
- URL – Tester can mention the page URL where the bug found
- Description – The Description should be detail but to the point
- Steps to reproduce – The steps to reproduce the bug in detail which will help developer to understand the bug more
- Issue found – The issue found while testing and how it is not acceptable should be mentioned
- Expected result – This can be optional as if you have requirement then only you can update the expected result.
- Priority – The priority of bug which will help to developer to decide his work flow also for project manager to analyze that how many high priority bugs are raised so the medium and low.
- Assign to – The bug should be assign to respective developer for resolving the issue which help developer to know that specific module is having issue and it is assigned to him.
- State – The state of the bug should be maintain which will help testers, developers and managers to analyze that how many bugs are fixed; how many are in process and how many yet not touched.
- Reason – The reason for bug should be mentioned as it will help developer to take the precaution in future while writing the code
- Module – Tester can explain the module in which he/she is found the bug which saves the developers time
- Links – The links other than URL of the page can be maintained at one place
- Screenshot/Video – Tester can add screenshot or video of the bug which will more convenient for developer to track/understand the bug.
Why it is important to report a proper bug?
It is a great practice to report a proper bug as it will save time and money substantially. In long run of company as a team it is worth participation by reporting a bug in proper way. Most of the time the conflict issue between tester and developer is the bug is not explained well due to which it takes time to resolve. So good bug reporting will reduce the clash time and improve the quality of the application and productivity of team.
