Answer / v.vengateshbabu

If the defect raised by me is rejected i will check the
reason why the defect was rejected. if its not valid defect
or not reproducible defect then i will agree and inform the
same to my Tl to close it otherwise simply reopen and
reassign it to corresponding developer with valid comments.

Answer / usha

if my defect report is rejected by defect tracking tean
then i will explain about that defect's seviority and
priority with test lead and if they convience me with their
explanation (regarding no need of insertion of that bug)
then i will do my remaining testing otherwise i will
convienece them with respective user problem.

Answer / kumar

Will provide the test scenario with
(1) Ddetailed replication steps (2) Environment Details
(S/W & H/W & Release/Build)

and cross check same with Test Developer / Test Lead.

Answer / friend

If the bug is valid & still it get rejected then I will try
to reproduce it & if it will be reproducible then I will
take screenshot of that for reference. Then I will ask why
the bug is rejected? & try to explain the defect's severity
and priority.

If the bug will not reproduce then I will do the remaining
testing & try to reproduce it in next build.
Correct me !

Answer / suma

It would be ideal to refer back to the requirements. if its
still not right reopen the bug adding notes referring to the
requirement and assign it to the Business to decide what
they need.

Answer / murali raju

If my Reported defect is rejected in that situation tester
is not responsible person. when he raise the bug that time
he send snapshots of the bugs to the development team as
well as team leader. so team leader will take care of it.

if you have any doubts please contact me through my mail i
will be clarify to you. muraliraju@vsnindia.com
Regarding,
Murali Raju.V

Answer / sarika

We can try to convince the Defect tracking team about the
defect you reported,or while you discuss it with the test
lead and the whole defect tracking team they convince you
with their reason for rejecting it,you can very well
continue to close the defect,else if you r still not
convinced with their explanation you still have your trump
card ie the customer ie while you detect a defect you
always send a copy to customer or client also,if u succeed
in convincing client well ...then u can very well send it
back for fixing

N.B.i expect your comments guys...

Answer / ravi76xy

The above answer is fine, But when we cannot convience the TL or the Dev Team
about the severity of the Bug it is always adviced to approach the QA for the
same.

Answer / raju

he is correct

Answer / ramya

once again i will retested the bug with same test data in peer system.if bug is reproducible then i will expain the bug with clear snapshot and reproducible steps.

How To write Wimax field testing test cases,,,,? both negitive and Positive,,,,follows rule Tringulation (Logitude and latitude)

0 Answers   Ericsson,

how will you decide defect severity & priority?

14 Answers   Hewitt,

what will you do when your reported defect rejected?

10 Answers   TCS,

what are the fields in traceablity matixes.

8 Answers   HCL,

How do we do testing if requirements are not documented properly?

2 Answers   IBM, Quality Kiosk,

What is test strategy..?

2 Answers  

Need information on Documentum4.3, any websites. What is this Documentum,how to access,features and benefits. ASAP Thx.

1 Answers   Cap Gemini,

what is the velue of, 'x'?

3 Answers  

what type of documents needed in every phase of sdlc for SQA?

2 Answers   UHG,

What do you mean to CAPA?

3 Answers   Ariel,

what type of testing process is going on your company?

8 Answers   Accenture, CTS, ISPG, Ordain Solutions,

Test Documents Reporting answers

4 Answers   ABC, Mastek,