What is Bug/Defect?
Bug: A bug is defined as an error that was found before the application goes into production. A bug gives a subliminal impression which crawled into the developer’s code quite independently of the software developer.
Defect: A defect is defined as an error that was found after the application goes into production. It presents cold harsh reality which the engineer, analyst or designer actually get something wrong.
Tips for Bug Tracking
Create Small Tasks:
When the number of tasks is large, it is hard to track the bugs. The tasks grow when they are shared among members of the team without much intention. The tasks should be small and not include multiple tasks in them. The larger tasks should split into smaller tasks, which helps the team members to review them easily.
Group tasks:
Categorize the similar tasks into groups. The tasks can be easily tracked and it is easier for finding them for each member of the team. It is wise to separate the tasks by type.
Draft the reproducing steps:
Write down certain steps to reproduce bugs for developers, and avoid the steps which are large in number. Have smaller number of steps which is easier for identifying a but for a developer.
Task flow:
The tasks must always revert to the person who created it or required for reviewing it. If it is a bug, it should be reverted to the tester. The tester can close the bug, since he/she is the one who saw the bug first and can be sure for fixing it. A task should ‘never’ be closed by another person other than the one who created it.
Less means more
Try to hide the tasks which are currently not having priority. Focusing on the important tasks, get the team to overview better.
Tips to write good bug tracking report
1. Title should be clear:
A good title is a must, which the essence of the bug report be well grasped by the developer.
2. One but per report:
A bug report should have only one bug and not more or no less. In case more bugs are placed, some of the bugs may be overlooked.
3. Minimum, quantifiable steps to reproduce the problem:
This is a very important tip. Developers need to get the problem in the shortest possible time. So the tester needs to help them for doing just that task. Testers need to have few rounds of testing and be able to produce the problems using minimum steps.
4. Expected and observed results:
A bug report should always contain the expected and the observed result. The developer does not think that the bug is a real bug. Testers should take the responsibility to explain the developers that went wrong.
5. The build that the problem occurs:
It is common the daily builds. If the exact problematic build is not specified by the tester, it is hard for developers to resolve an already-solved problem.
6. Pictures:
‘A picture is worth a thousand words’! Certain times, the words do not flow. If such situations, it is better to have a clear picture that perfectly illustrates the problem.
Explain the different types of Bugs
The different bugs are:
1. Show-stopper / critical bugs: The core dumps, products abnormally shuts down and no work around will be found out, like OS automatic freezing.
2. Major Bugs: The work around is found, but the implementation can be done, like performance degradency.
3. Medium Bugs: These bugs include database errors, link errors, low response time
4. Low/minor Bugs: These bugs are typos, simple GUI errors.
What is the difference between New and Open bug?
New: In finding an issue in testing, all relevant checks are performed, like whether is was occurring in the previous release. If the issue is so, reopening the bug and creating new defect is done by changing the status of that defect to ‘new’.
Open: When a new bug is opened, development or project manager revises it, followed by assigning the task to the developer, and changes the status from ‘new’ to ‘open’.
Difference between Defect and Failure
a. Defect: Defect is defined as a wrong requirement.
b. Failure: Variation in the result produced by the software from its expected result.
What is the process of bug cycle?
The following steps involved in the bug cycle process:
1. Bug investigation – when the tester find the bug
2. Bug assignment – when the tester assigns the bug to the developer
3. Bug fixing – when the bug is fixed by the developer
4. Bug retesting – when the developer fixes the bug and given to the tester
5. Bug closing and reopening – when the tester retested and the status is changed to ‘closed’.
What is the process of bug cycle?
What do you mean by "Reproducing a bug"?
When a bug is found in a module, it must have followed a series of steps. The steps must be noted down by the tester in order to replicate the bug again. Reproducing a bug means following the same steps to find the bug.
Defect Severity & Priority with example:
Defect Severity determines the defect's effect on the application where as Defect Priority determines the defect urgency of repair.
Severity is given by Testers and Priority by Developers
1. High Severity & Low Priority : For example an application which generates some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. If there is a fault while calculating yearly report. This is a high severity fault but low priority because this fault can be fixed in the next release as a change request.
2. High Severity & High Priority : In the above example if there is a fault while calculating weekly report. This is a high severity and high priority fault because this fault will block the functionality of the application immediately within a week. It should be fixed urgently.
3. Low Severity & High Priority : If there is a spelling mistake or content issue on the homepage of a website which has daily hits of lakhs. In this case, though this fault is not affecting the website or other functionalities but considering the status and popularity of the website in the competitive market it is a high priority fault.
4. Low Severity & Low Priority : If there is a spelling mistake on the pages which has very less hits throughout the month on any website. This fault can be considered as low severity and low priority.
Bug: A bug is defined as an error that was found before the application goes into production. A bug gives a subliminal impression which crawled into the developer’s code quite independently of the software developer.
Defect: A defect is defined as an error that was found after the application goes into production. It presents cold harsh reality which the engineer, analyst or designer actually get something wrong.
Tips for Bug Tracking
Create Small Tasks:
When the number of tasks is large, it is hard to track the bugs. The tasks grow when they are shared among members of the team without much intention. The tasks should be small and not include multiple tasks in them. The larger tasks should split into smaller tasks, which helps the team members to review them easily.
Group tasks:
Categorize the similar tasks into groups. The tasks can be easily tracked and it is easier for finding them for each member of the team. It is wise to separate the tasks by type.
Draft the reproducing steps:
Write down certain steps to reproduce bugs for developers, and avoid the steps which are large in number. Have smaller number of steps which is easier for identifying a but for a developer.
Task flow:
The tasks must always revert to the person who created it or required for reviewing it. If it is a bug, it should be reverted to the tester. The tester can close the bug, since he/she is the one who saw the bug first and can be sure for fixing it. A task should ‘never’ be closed by another person other than the one who created it.
Less means more
Try to hide the tasks which are currently not having priority. Focusing on the important tasks, get the team to overview better.
Tips to write good bug tracking report
1. Title should be clear:
A good title is a must, which the essence of the bug report be well grasped by the developer.
2. One but per report:
A bug report should have only one bug and not more or no less. In case more bugs are placed, some of the bugs may be overlooked.
3. Minimum, quantifiable steps to reproduce the problem:
This is a very important tip. Developers need to get the problem in the shortest possible time. So the tester needs to help them for doing just that task. Testers need to have few rounds of testing and be able to produce the problems using minimum steps.
4. Expected and observed results:
A bug report should always contain the expected and the observed result. The developer does not think that the bug is a real bug. Testers should take the responsibility to explain the developers that went wrong.
5. The build that the problem occurs:
It is common the daily builds. If the exact problematic build is not specified by the tester, it is hard for developers to resolve an already-solved problem.
6. Pictures:
‘A picture is worth a thousand words’! Certain times, the words do not flow. If such situations, it is better to have a clear picture that perfectly illustrates the problem.
Explain the different types of Bugs
The different bugs are:
1. Show-stopper / critical bugs: The core dumps, products abnormally shuts down and no work around will be found out, like OS automatic freezing.
2. Major Bugs: The work around is found, but the implementation can be done, like performance degradency.
3. Medium Bugs: These bugs include database errors, link errors, low response time
4. Low/minor Bugs: These bugs are typos, simple GUI errors.
What is the difference between New and Open bug?
New: In finding an issue in testing, all relevant checks are performed, like whether is was occurring in the previous release. If the issue is so, reopening the bug and creating new defect is done by changing the status of that defect to ‘new’.
Open: When a new bug is opened, development or project manager revises it, followed by assigning the task to the developer, and changes the status from ‘new’ to ‘open’.
Difference between Defect and Failure
a. Defect: Defect is defined as a wrong requirement.
b. Failure: Variation in the result produced by the software from its expected result.
What is the process of bug cycle?
The following steps involved in the bug cycle process:
1. Bug investigation – when the tester find the bug
2. Bug assignment – when the tester assigns the bug to the developer
3. Bug fixing – when the bug is fixed by the developer
4. Bug retesting – when the developer fixes the bug and given to the tester
5. Bug closing and reopening – when the tester retested and the status is changed to ‘closed’.
What is the process of bug cycle?
- A bug when found by the tester is marked as NEW.
- This bug is checked for its validity by the test lead to mark it as OPEN.
- The bug is then ASSIGNED to the developer.
- The developer on fixing the bug gives it to the tester for regression testing.
- The tester may either REOPEN or CLOSE the bug.
What do you mean by "Reproducing a bug"?
When a bug is found in a module, it must have followed a series of steps. The steps must be noted down by the tester in order to replicate the bug again. Reproducing a bug means following the same steps to find the bug.
Defect Severity & Priority with example:
Defect Severity determines the defect's effect on the application where as Defect Priority determines the defect urgency of repair.
Severity is given by Testers and Priority by Developers
1. High Severity & Low Priority : For example an application which generates some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. If there is a fault while calculating yearly report. This is a high severity fault but low priority because this fault can be fixed in the next release as a change request.
2. High Severity & High Priority : In the above example if there is a fault while calculating weekly report. This is a high severity and high priority fault because this fault will block the functionality of the application immediately within a week. It should be fixed urgently.
3. Low Severity & High Priority : If there is a spelling mistake or content issue on the homepage of a website which has daily hits of lakhs. In this case, though this fault is not affecting the website or other functionalities but considering the status and popularity of the website in the competitive market it is a high priority fault.
4. Low Severity & Low Priority : If there is a spelling mistake on the pages which has very less hits throughout the month on any website. This fault can be considered as low severity and low priority.
Technology develops products to make work easier for people and to make life simple. We should also consider some point’s like- It should be Flexible Type of Software, Recording the History, Customizing the Fields, Permission Levels etc. Thanks for sharing.
ReplyDeleteBug Defect Tracking
Mailers servers email leads marketing email sender tools cpanels We are really grateful for your blog post. You will find a lot of approaches after visiting your post. I was exactly searching for. Thanks for such post and please keep it up. Great work.
ReplyDeleteFerum shop Free cracked account giveaway loaded bitcoin Awesome article, it was exceptionally helpful! I simply began in this and I'm becoming more acquainted with it better! Cheers, keep doing awesome!
ReplyDeleteHow to activate unicc account http uniccshop cz I admire this article for the well-researched content and excellent wording. I got so involved in this material that I couldn’t stop reading. I am impressed with your work and skill. Thank you so much.
ReplyDeleteI think this is an informative post and it is very useful and knowledgeable. therefore, I would like to thank you for the efforts you have made in writing this article. Fleet management software
ReplyDeleteWorkflow automation software I think this is an informative post and it is very useful and knowledgeable. therefore, I would like to thank you for the efforts you have made in writing this article.
ReplyDeleteWow! Such an amazing and helpful post this is. I really really love it. It's so good and so awesome. I am just amazed. I hope that you continue to do your work like this in the future also z code system discount
ReplyDeleteI am happy to find this post Very useful for me, as it contains lot of information. I Always prefer to read The Quality and glad I found this thing in you post. Thanks zcode system discount
ReplyDeleteI think this is an informative post and it is very useful and knowledgeable. therefore, I would like to thank you for the efforts you have made in writing this article. virenschutz 2016
ReplyDeleteI think this is an informative post and it is very useful and knowledgeable. therefore, I would like to thank you for the efforts you have made in writing this article. linkedin automation software
ReplyDeleteI think this is an informative post and it is very useful and knowledgeable. therefore, I would like to thank you for the efforts you have made in writing this article. windows visual studio
ReplyDeleteığdır
ReplyDeletemaraş
afyon
bandırma
hakkari
RFDBE