Interested to Buy Any Domain ? << Click Here >> for more details...
What might be the reasons for changing the status of a bug
to " NOT A BUG " ?
- 13 Answers
- 20145 Views
- Accenture, I also Faced
- E-Mail Answers
Answer Posted / m.srikanth
In three situations we will change the status of a bug to
"Not A Bug".
1.Hold:- Whenever the developer is confused to accept or
reject its as a bug. Then he or she put its on a hold.
2.As per Design: Whenever the developer is done some changes
to the application, its were aware of test engineer and test
engineer raises its as bug and developer explains its was
done as per design released latestly.
3.Tester Error: Whenever Developer's lead or Developer
confirms its as a tester error in findout the bug.
In this scenario's the developer changes status as bug to
"Not a Bug".
| Is This Answer Correct ? | 5 Yes | 0 No |
Post New Answer View All Answers
What is a top-down and bottom-up approach in testing?
what are the Cs in testing
How many types of api testing are there?
. Is any graph is used for code coverage analysis?
How can you do the scalability testing?
What do you do (with the project staff) when the schedule fails?
Hi Can any one tell wht type of questions will be asked in project manager round...urgent plz...
what are the risk factors in the project? what is the base for testplan and entry criteria ,exit criteria for test plan?
What are the main key components in web applications and client and server applications?
As you are working with cmmi level 5 company ,can you tell me what processes you r following as QA engineer?
what is the difference between Risk based and Requirement based testing???
Explain thread testing.
what is the difference between test case and result matrix
What is difference between web site testing, desktop application testing and wireless application testing? what is the difference in testing strategy to test them?
What is coverage and what are the different types of coverage techniques?
