Answer Posted / sonal.pagare
It is common practice for software to be released with
known bugs that are considered non-critical, that is, that
do not affect most users' main experience with the product.
Most big software projects maintain two lists of "known
bugs"— those known to the software team, and those to be
told to users. The second list informs users about bugs
that are not fixed in the current release, or not fixed at
all, and a workaround may be offered.
There are various reasons for not fixing bugs:
• The developers often don't have time or it is not
economical to fix all non-severe bugs.
• The bug could be fixed in a new version or patch
that is not yet released.
• The changes to the code required to fix the bug
could be large, expensive, or delay finishing the project.
• Even seemingly simple fixes bring the chance of
introducing new unknown bugs into the system. At the end of
a test/fix cycle some managers may only allow the most
critical bugs to be fixed.
• Users may be relying on the undocumented, buggy
behavior, especially if scripts or macros rely on a
behavior; it may introduce a breaking change.
• It's "not a bug". A misunderstanding has arisen
between expected and provided behavior
Given the above, it is often considered impossible to write
completely bug-free software of any real complexity.
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
What are cookies?
can you show me the test cases on registration form
What is the difference between qa, qc, and testing?
In how many ways you perform batchtesting ?
test cases for Insurance Processing System ?
Can anyone please tell in detail about the Rally tool and how a tester is going to use it.
What are the Major Functionality for a ATM machine ??
what is the technical challange you faced in your module.please ans me the question i just want example can me any example please very important
Need to know about Quality Center in brief
There is only requirements document. You have 10 days and 8 resources to release the system.At the end of the 8th day u tell ur TL that system is ready for release. How will you proceed with the testing process or in other words what all approach you will follow once you get requirements
Explain the defect life cycle.
what are the types of Bug?
What are bug leakage and bug release?
What is actually a rule based testing
please give information about ERP Projects and how V-model use in project
