Whenever developer will recieved the defect from the
tester,then he will go thru the defect whether it is
acceptable or not?for that he will execute that application
again,while executing if he did not found any such type of
defect(what we are rise the defect above),then he will send
that defect to the corresponding tester with status
of 'reject',as a tester what we can do?(here writing the
reproduce steps and attached screen shots has been done by
tester while sending the defect to the developer, no need
to send reproduced steps and screen shots again)
- 6 Answers
- 8746 Views
- CTS, IBM, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / kiranmayi
The tester should try to reproduce the defect again. If the
tester able to reproduce the defect then he/she should ask
the developer to try reproduce the defect in testing
environment instead of developing environment and then ask
them to fix it.
Please let me know if I am correct or wrong.
bommi_ki@yahoo.ca
| Is This Answer Correct ? | 6 Yes | 1 No |
Answer / varshab
In this case tester need to analyze bug once again.It may
possible that tester has made mistake while understanding
requirement.Wrong assumptions may lead to this
situation.Also while rejecting (will not fix) bugs developer
mention reason in bug tracking tool,tester should read that
& analyze it.If still tester is not agree then he/she can
discuss the same issue with his lead.After discussion if
tester still believe that its a bug then he can reopen that
bug & also add the descriptive report explaining how its bug.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / kirani
as the defect is rejected, once again execute the
application to check whether it is a defect or not. if at
all we find the same defect once again then check for the
requirements that are with the development department and
compare it with the requirements that are with us. may be
some times the altered requirement document will not reach
the testing department as soon as they reached the
development department.
| Is This Answer Correct ? | 2 Yes | 1 No |
Answer / remo
One solution is as kiranmayi said we have to ask him to
execute in test environment instead of development
environment
Other solution is, if it is possible to share your desktop
with developer then do so by providing the user name and
password. Now ask the developer to give a try on your
machine, if he is able to reproduce the bug then try to
find out the root cause why he was not able to reproduce on
his machine. (Reasons can be many like Bug is OS dependent,
browser dependent etc).
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / anita
Exactly Remo. Also one thing, rarely this types of bugs are
reproducable. Because this bug is for perticular OS,
browser or for that user (Email) only.
So tester can do one thing, he can provide taht email id,
password, name of OS, browser (like IE, FF, Netscape,
Saffari etc), steps to follow...etc
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / @mit
Yes,all stated answer are correct but still Developers not
accepting the bug then v should use the last and most
Effective way.
Email the same desceription to PM along with TL (both
Developers and Testing) with screen shot.
Then rest of all had done automatically.. :-)
| Is This Answer Correct ? | 0 Yes | 0 No |
what is the difference between test plan and test strategy. can anybody give me a template for test strategy
What Questions Project Manager will be aske?
How performance testing can be done manually? can anyone answer this question plz?
What is early testing?
When to stop testing? (Or) how do you decide when you have tested enough?
How do you develop a test plan and schedule? Describe bottom-up and top-down approaches.
what is fs
Explain the difference between decision coverage and condition coverage ? If possible provide few examples.
how can client know that the bug which has been corrected
what is the difference between testing methodology and testing techniques?
what is database teesting?
Does a manual test engineer indulge with SQL commands to test database.
Automation Testing 
