Why we cannot fix all the bugs?

Not all the bugs that we find are fixed. Some are deferred, postponed and others are rejected. The reasons are :
1. There is lack of time
Too many s/w features and too few people to code and test. Example tax payment date starts from a particular date.
2. It is not a bug
If specification has been mis read and report some feature as bug but actually it’s a required feature. Example – gmail has no cancel button.
3. Fixing to bug is too risky – It there is lack of time or schedule crunch is there then its quiet possible that fixing of a low priority bug may give rise to other unknown and new bugs and make the software risky. Hence its better to postponed the bug.
4. Its not worth fixing the bug
Bug that would rarely occur or appear in little used feature may be dismissed or a user can avoid that bug are often not fixed. It all depends on the risk involved.
5. Ineffective Bug reporting
He tester did not make a strong enough case that a particular bug must be fixed. As a result the bug was misunderstood as not being a bug or was deemed not imp enough to delay the product or was thought to be too risky to be fixed.
6. Delay in reporting the Bug
Earlier a bug is found more time remains in the schedule to fix the bug. Suppose several spelling mistakes were found in the help document before one month of the release date then this would be having more possibility of getting fixed but it that bug is found one day before the release of software then it might be ignores. The later a bug is found the less likely it is to fix the bug especially if it’s a minor bug..
7. Be nonjudgmental in reporting bugs
We cannot say that ur baby is ugly. A tester should be non judgmental and non personal. The bug report can be viewed as report card of programmers. Bug reports should be written against the product and not the person like u have made work the s/w terribly, u have mage wrong decisions etc. Tact and diplomacy should be there.

Comments

Post a Comment

Popular posts from this blog

What is Quality Control?

Quality Control is product oriented approach which monitors whether the software has been developed as per the requirement of the user. This process ensure “Are we building the right product?” Quality Control commences once the Coding phase of Software Development Life Cycle is complete. It starts when the actual software is ready. Testing is performed on the product that has now come into existence. Quality Control determines if the system complies with the requirements and performs functions for which it is intended and meets the organization’s goals and user needs. It is traditional and is performed at the end of the project. Quality Control determines correctness of the final software product by a development project with respect to the user needs and requirements. Quality Control alone does not ensure quality. If we want to develop a quality product then improvement measures have to taken right from the beginning of SDLC. Quality Control follows corrective approach. Quality C...
Read more

What is Quality Assurance.

Quality Assurance is the process oriented approach which monitors the entire Software Development Life Cycle to ensure that the process followed is consistent, adheres to standards, uses reliable techniques and prudent practices, and performs the selected functions in the correct manner. This process ensure “Are we building the product right?” Proper application of methods and tools, effective formal technical reviews, concrete management and measurement all lead to quality. It is a myth that Quality Assurance ends once design phase of Software Development Life Cycle ends. This is actually not true. Process of Quality Assurance commences as soon as Requirement Analysis phase of Software Development Life Cycle begins and continues upto release of the software. Software testing is also part of Quality Assurance. Quality Assurance is demonstration of consistency, completeness, and correctness of the software at each stage and between each stage of the development life cycle. Quality...
Read more

Severity and Priority of Bugs

It is not possible to fix all the bugs as there is lack of time. Hence bugs have to be assigned some category so that we are able to fix bugs with higher priority first and if time allows we can fix bugs with lower priority. There are two basis for categorization of bugs. They are know as Priority and Severity. In their bug reports the testers must mention both the categories in order to help developer to fix urgent bugs first. Severity How bad the bug is; the likelihood and the degree of impact when the user encounters a bug. Severity is always determined from the point of view of application. Categories of severity are as under : * Critical * Major * Minor * Suggestion Priority Indicates how much emphasis should be placed on fixing the bug and the urgency of fixing the bug. Priority is always determined from the point of view of the user. Categories of priority are as under : * Show Stopper/ Immediate Fix * High * Medium * Low
Read more