developer says it is not defect.then as a test engineer
what u will do?
Answers were Sorted based on User's Feedback
Answer / jay
i will try to reproduce the defect by re-engineering
testcase and take the snapshots of all screen. now i will
post to developer with strong reasongs along with snap /
|Is This Answer Correct ?||6 Yes||0 No|
Answer / sriram gs
With due respect to all the above answers, at times this
situation arrives where developer says application is as
At the same time not all requirements will be documented in
BRD. As a tester when u come across a defect which is
directly not pointing to requirement but at the same time
can be critical from business point of view.
This is where the conflict can arise between dev & tester.
In this situation, tester can discuss the issue with
business analyst [who acts as bridge between project team &
client] & after clarification, project the defect to dev
team with more clarity and thereby convincing dev team in
accepting the observation.
|Is This Answer Correct ?||4 Yes||0 No|
Answer / suneel reddy
When we found bug we will review it internally
we will report the bug in bug tracking system with detail
steps including screen shots and procedure
we will also consult with the developera and shows the
we will also go through functional documents to amke sure
that it is bug
If still debate occurs we will raise it in Bug triage
|Is This Answer Correct ?||3 Yes||0 No|
Answer / muralidhar v
Before raising any bug, first try to understand and analyze
it from requirement of view.
Do not come to conclusion that it is a software bug
instantaneious if you are not getting the expected result
in the application. It can be a test case or test data bug
meaning that the application is working fine but the
expected result in the test case itself is wrong. It could
be your misinterpreation of the requirement.
Hence, analyze it and come to conclusion that it is really
a bug as it is not adhering to the requirement, RAISE it.
|Is This Answer Correct ?||2 Yes||1 No|
Answer / satya_k21
If u found a Defect, but the Developer says it is not a
defect then u can send the snap shots of the particular
scenatio from starting to ending .. by using the snap shots
the developer can understand wht test data that the tester
|Is This Answer Correct ?||2 Yes||1 No|
When a developer say it is not defect. Then, ask the
developer to give a complete and proper justification note
to that effect. Then, if found that developer has mis-
understood the requirements/reproduction steps given in bug
report then convice him about his mistake.
In short if tester is sure that it is really a defect then
challenge the developer in a healthy manner.
|Is This Answer Correct ?||3 Yes||2 No|
Answer / jagadeesh
If at all the developer not accept the bug, i think it is to fix in the next build... But before that i should not blindly accept that bug and i have to read all updated documents and also i will send reproducable document.. i give clear document and all the steps..screenshots..
|Is This Answer Correct ?||0 Yes||0 No|
Answer / parmod
First of all, we should mention the severity of the bug.
Then try to explain to developer, how much the bug effects
the functionality. No matter what the developer says, if it
is bug, report it. Isn't it simple.
|Is This Answer Correct ?||1 Yes||4 No|
What is six sigma?
What is the difference between Bugzilla and Softsmith- QAMonitor?
What do you understand by usability testing?
what r the measure bugs found in your project??? Give some example abt this.
Write the test cases for credit card accessing the money transfer
what type of questions they asked in symphony company for manual testing?
1...HOW TO RETRIEVE NUMBER FROM ALPHA NUMERIC VALUE? 2.. HOW TO CAPTURE A DYNAMIC VALUE IN WEB APPLICATION? 3.. HOW TO GET THE OUTPUT VALUE FROM ONE TRACTION AND USE THIS OUTPUT VALUE AS INPUT OF ANOTHER TRANSACTIONS? 4... HOW TO COUNT A WEB TABLE ROW? ... WHAT IS QC LIFE CYCLE? 6...WHAT IS IMPACT ANALYSIS? HOW TO DO IMPACT ANALYSIS IN PROJECT?
in an online banking software,users are connecting to bankserver by login.This login module can take below inputs for user. a/c number prefix-3 digits but doesnot start with 0&1 a/c number sufix-6 digits number password-5to 10 chars alphanumerics in lowercase areacode-3 digits number but optional purpose- cheque deposit money trasfer mini statement bills pay After filling above fields,user can click submit button to connect to bank server.prepare test scenarios for online banking s/w login.
is programming knowledge is necessary for testing
What is the difference between low and high level test cases? examples please..
What are the modules of quality center?
1. what is baseline document , can you say any two ?