Praveen

• Oct 14th, 2005

 

It is better to take the snapshot of the Bug. If it is not reproducble , then we can attach that particular report or snapshot to the development team

venkat

• Jan 23rd, 2006

 

In this case the tester has to perform the "Retesting",he has to take the snapshot of the situation and then attach the snpshot with the description of the bug.

Nilay Parikh

• Feb 14th, 2006

 

First of all check the system configuration is the same for developer's system and tester's system. If the configuration is the same, try to reproduce it in test environment, write down the steps you follow, take the snapshots for all the screens you go through and analyze the same to figure out the problem.

Abhinav Johri

• Mar 29th, 2007

 

After Taking the snap of that bug,Close that bug and give the comments the this bug can be opened if the same issue occour again in future

James

• Mar 29th, 2007

 

Most of the bugs are returned by this cause only and while testing the perticular test case we will be able to know that it is an environmental issue. at that time we can automate our steps which is nothing but recording of our steps, which we followed and we have to attach that to the defect. there are some tools for these type of recording. Whenever they are not able to reproduce the defect, we have to cancel such type of defects by the reason environment issue and we have to give the root couse

Preeti

• Apr 4th, 2007

 

We can also set up(refresh) the environment of testing side and still we see that its not reproduceable then we can clsoe the bug

praveen reddy

• Apr 13th, 2007

 

Re-test once again, conform yourself is a bug, and inform, if it is not appering in developer site then check your envernment and his are same (software, versions etc)

It is better to take the snapshot of the Bug. If it is not reproducble, then we can attach that particular report or snapshot to the development team

pavanmamilla

• Jun 5th, 2007

 

As and when you find any bug take the screen shot and while sending the bug to the developer clearly mention them, the scenario in which you got the bug and in case if you dont know the scenario mention them as i am not able to reproduce it. Sometimes its happening in QA environment.

sankarraparthi

 Profile Answers by sankarraparthi 

• Jun 6th, 2007

 

The following things can be helpful in this case

1. A screen shot of the bug if the bug is visible.
2. Check with the same scanerio in which bug has come, that is Check for the Browser and its version on Developer's side
3. Check for the route cause of the bug, that is what is the cause that this bug has come.

BIBHU PRASAD BEHERA

• Jun 12th, 2007

 

Take the snap shot and also attach the log file. Therefore developer can easily find out the root cause.

MohsinK

 Profile Answers by MohsinK 

• Jul 22nd, 2007

 

You may give the developer access to the test machine where the bug is reproduciable

Mannu

• Jul 26th, 2007

 

If any case arises, then it is better to attach the screenshot of the bug found, so that no one can raise a finger on the Tester that the bug reported is invalid.

Moreover, a tester should make a common habbit of attaching the screenshot of the bug found while repoting the bug.

Jagan Mohan Rao

• Sep 2nd, 2007

 

If your application is related to WEB application then this answer will give you a clear point about Environment type of defects.

When ever you are executing your test cases. Then some cases or in some perticular time each and every test case is failed by one constant error message.

At this time you should not open a Software defect. You have to open an Environment defect and assign to the team who support the environment defects. For these type of defects. You have to take the screen shot which helps the Developer to resurch on the error message. even if it is not getting at there end they should find the root cause of such defects. so a application supporting team will be avilable 24X7. Even though if the develore is not able to duplicate this issue then he will Return the defect by stating that not able to duplicate this issue can you check it once at your end. If you are able to duplicate this issue at your end then you have to give clear details suct as Starting point of your application to ending point of your application. and you have to reopen the defect. Then they will execute the application with the data prodused by you and try to duplicate the issue. Even though if they are not able to duplicate this issue then they will ask for IE version. At this point they can able to duplicate this issue.


Thanks & Regards,
JAgan Mohan Rao. Y

srivatsa

• Sep 2nd, 2007

 

In organisations we have a team called testing team. In that team all are doing testing the application but different pages. All pages are not given to you. First when ever you find a defect then you perform retesting weather it is reproducible or not. If it is reoproducible don't straight away submit it. You have to execute the same test case on the other system in the team to avoid environmental issues. If there also the same bug is observed, take a snapshot & send it to the dev team.