suppose u have raised one bug.u have posted to that
concerned developer..he can't accept that is a bug.what
will u do in the next stage?
Answers were Sorted based on User's Feedback
Answer / varsha b
I will try to reproduce that bug and send the reproduction
details to respective developer.If still he/she is not
accepting the bug then I will discuss the issue with my
lead .Further my lead will decide what to do in this case.
(May be my lead will arrange meeting or communicate with
developer).
| Is This Answer Correct ? | 5 Yes | 0 No |
Answer / jyotsna
If the developer won't accept our sent bug, then we show it
to our team leader or we can show it to our superior
person. so he/she will go and discuss with developer or
else they will conduct one meeting on that.
correct me if i'm wrong:)
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / michael eltham
Always report bugs properly with exact steps to reproduce,
occurrence, severity, screen shots, logs etc. Report the
bugs in the Defect tracking system. Convince the developer
about the risk and the priority. If he still does not
accept the bug - don’t release the product until the bug is
acknowledged by the Team lead. And make sure to note them
in the Release notes.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / suneel reddy
Sometimes bug not reproducible in Dev Environment
at that situation dev doesn't accept
we will give him screen shots
If still debate occurs
we raise the issue in bug traige meeting
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / raahul yaadav
we just attach a screenshot...which act as a proof and we r
on the saFER SIDE..
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / satyanarayana
In this type of situations we have to reproduce the defect
and capture the snapshots of that defect and send it to
the cocerned developer.some times due changes in the
development and testing environments also this type of
problems arises
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / venkey
first i will inform team leader.Then after team leader and
deleloper discussed
or)snapshot send to developer
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / shruti
If the developer considers the bug as low level or does not
accept it as a bug, thus pushing it into Not Accepted/Won’t
fix state. Such bugs will be assigned to the project
manager who will decide if the bug needs a fix. If it
needs, then assigns it back to the developer, and if it
doesn’t, then assigns it back to the tester who will have
to close the bug.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / venkatesh
jyothsna is correct if the team lead or project manager
doesnot accept with that bug we can directly intimate to
the client that so & so was happening
| Is This Answer Correct ? | 1 Yes | 2 No |
This is the question related to Traceability Matrix. Say we have 10 requirements for a project. If one of the testing team member misses the 9th requirement. Then how can we justify the Traceability Matrix and what is the further action to be taken. Please advice.
what is accessibility testing ? with one example
What are the things you prefer and prepare before starting testing?
What is the negative testing and example
what is meant by Priority and Severity?
What is the testing process and what testing process followed by software company?
when will tester do the smoke testing?
What are the bussiness scenories?
what is defect density ? we say it is No of defects / line of code.. what is line of code ? pls if possible give some real example
There are no requriments, coding is been developed to the project without srs,brs document how u are going to prepare test case?
Defect management
what do you mean by Develop test data through sourcing (or) handcrafting techniques