Answer / smaranika

Hi,

Well there are situations in which the bug may not be
reproducible in the development machine (due to envirnoment
issues,etc) and so the Developer rejects the Bug. In such a
case a tester can share his testing envirnoment details
with the developer where the developer can repro the issue.

Once the developer sees himself the issue he can further
debug to find the reason why bug is coming on Testing
envirnoment.And i am sure he will work on this and get it
fixed.

Thanks
Smaranika

Answer / rajvelur

Here in the above situation if the developer Rejects the bug
then when we have to send them the steps, describing how we
got the bugs and also attach the screen shots of the bug we got.

Answer / satya

Hi there are some chanses that the bug can not produce at
Developer place. These may be due to the wrong steps
followed by the developer as the Tester described or may be
due to the Environment change bw dev and tester or May b
the Developer intentionally makes it CNR or so...

In this case, the Tester need to take the Step by step
Screen shots or atleast the screen shot of the Bug and can
send it to the developer with involving Higher Management
(TL, PM, QM) to prove ur bug is a BUG.

It is sure that u'll prove ur bug still if developer not
intended to fix, you can recomment dev to make the status
of the bug to NIF (No Intension to Fix).

Answer / ankush gupta

Tester should follow this approach to convince the
Developer for a Valid Bug:-

1)To provide Steps to reproduce the bug, if always
reproducible

2)To provide screenshots of the errors etc, if there

3)To reproduce and show the Bug to Developer on Test
Machine, if not reproduced on Dev Environment

4)To ask the Developer to try reproducing the Bug on
Tester's Machine

5)If Bug is valid and reproduced easily on tester's machine
and developer is still not accepting the bug, tester should
report this to TL/PM for its Fix

Answer / rudraneel

The question is not very clear itself.Though I am trying to
answer this.

When developer receives one bug from tester and if he/she
starts working on that bug changing the STATUS of the bug
as IN PROGRESS.After that the bug is sent back to the
tester and if tester doesn't find any bug then the bug is
CLOSED.And is developer gets one bug and while executing
the bug he/she does not find any bug then developer changes
the STATUS of the bug as REJECTED and sent back to the
tester,tester again check,and if there is no bug then the
STATUS will be changed to CLOSED.

Answer / venkata narayana n

Hi Rudraneel i am very happy to your response,but i am not
asking about bug life cycle,you can go thru question again
and reply me once.Once again i will repeat the question
again...........

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)

Answer / jai

1)Tester verifies the bug and marked the bug reproducible
or closed
2)Tester assign the bug to TL (if reproducible)

I request member to comment sincerely on this as this is a
live situation and no body gives proper solution to it.

Answer / jyoti

Ya i agree with smaranika. some bugs we cant produce on
developer envirnoment whatever we got on testing
envirnoment.In this case we have to call that perticular
developer and showed him on tester machine and then also he
is not accepting then inform to ur TL or PM and prove that
it is a valid bug

Answer / ganesh

IF bug is reproducible then as a tester u suppose to call
that developer and execute that bug. U can refer retest
concept for this problem In front of developer.

Answer / sai

Some times testers may get issues in testing environment then he will report that bug.Than developer open that bug first he will test that bug. Some times for same functionality in the test environment it will show bug but in the dev envirment it may not be a issue .In this situation tester has to call the developer to his desk again test the same test case and explain him what type of issue he is facing. (some times same test case fails in the testing environment but in dev env it may not show any bugs)

How many test scripts can you prepare per a day?

5 Answers   AppLabs,

What is the smoke testing and sanity testing..?what is the difference?

10 Answers   TCS,

Explain Equivalence Partitioning ?

2 Answers   Crea,

test templet for GUI UNIT testing?

0 Answers   Crea,

Define Stability, Scalability and reliability with example ?

0 Answers  

write the maximum possibilities test scenarios/ test cases for Google home page - Screen has following: Google Text field, Buttons are - "Google Search" and "I'm Feeling Lucky".

2 Answers   Amazon,

If a bug is not reproduced what will be the next action of the tester?

6 Answers  

What's the difference between alpha and beta testing?

0 Answers  

I was asked with 4+ expeirence - How did you involve in implementing QA Standards and guide lines in ur project.

1 Answers   IBM,

write 3 test cases on ATM for security purpose

8 Answers   Zycus Infotech,

Can anyone tell me the correct difference between compatibilty testing & configuration testing

2 Answers  

Is system testing part of Functional testing or functional testing part of system testing?

4 Answers   Oracle,