Interested to Buy Any Domain ? << Click Here >> for more details...
When a bug posted by QA is rejected by Dev and Dev says is
not a bug. How to convince Dev that it is a valid bug?
- 11 Answers
- 20819 Views
- GE, I also Faced
- E-Mail Answers
Answer Posted / rajesht
case1: Requirement exists for the reported bug
If Dev says it is an invalid issue, then the tester need to
give him reference no of the requirement.
case2: Requirement not exists for the reported bug.
Sometimes we may encounter some issues while testing which
do not have requirements. In that case we still have right
to submit a bug with issue category as requirements. If the
developer says that it is an invalid issue then we have to
move that bug to business analyst asking his comments. Once
we receive the comments from business analyst we will move
back the bug to developers court.
| Is This Answer Correct ? | 1 Yes | 1 No |
Post New Answer View All Answers
What ishigh severity, low priority bug?
What is a top-down and bottom-up approach in testing?
What types of testing is specifically important for web testing?
I have 2 yrs 10 months experience in manual testing. there is a gap of 3 yrs in between. just 3 months before i rejoined the same company. I am looking for new & better job.What I have to enhance my career to up level, should I have to do Automation course or any other. Guide me properly.
Difference between smoke and sanity testing
Hello testers I am an Bsc Hotel mgmt Degree holders but now am doin my software testin programme, side by MCA Master degree an have 6 months exp i testing in company.. i want to change my CV according IT based. so can anyone help me with sendin any sample CV of urs.. do me this favour it wil be very helpful for me prepare CV for interviews....
Can you explain the various elements of function points ftr, ilf, eif, ei, eo, eq, and gsc?
Hi to all..Now am working at one company as Software tester..I have selected for Accenture via one consultancy.. They have told that joining date will be on 19 th july..But now they are postponed joining date..whether i can trust that or not?Can u plz tell??plzz..whether i can put my paper to releive or not? CAn u telll?
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
what is the testing approach for windows Explorer(Not IE Explorer)
iwant know IEEE formate ,how it is used and exactly where it is used? i have details it follows test plan, testcases...etc. i want real time explanation. pls any one give?
When to stop testing? (Or) how do you decide when you have tested enough?
How do you scope,organise and execute a test project.
What is Windows Test Technologies? Where i will get all information of it.
is it possible web application make it as executable file
