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
i need manual testing interview questions for 2+ experience plzz help me..
Tell me example for Risk,Mitigation,Assumption?
write test case for gmail sign up page?
Write all combinations of test cases for calculater on + symbel
What kind of input do we need from the end user to begin proper testing?
what types of bugs will we find out in banking projects
How we can test Cookies Manually?
i want information about API testing and i want info like how process can be done in company? i want added info like coding ,debugging, desing in c.v ? what should add in c.v for eg banking domin? pls any answer my question?
What is client server application testing?
Are there more defects in the design phase or in the coding phase?
How does a coverage tool work?
can you tell me how to write test cases for payments, receipts, inward clearing, outward clearing, A/c statements ?
what are all the things we will include in " what to be tested and what not to be tested" in Test Plan
What is 'Account Conditioning'?
Why is it impossible to test a program thoroughly or in other terms 100% bug-free?
