Shresh

 Profile Answers by Shresh 

• Aug 11th, 2008

 

First of all, priorities and the severities should be set then developer would resolve it and tester would test it as per the prority and the severity of bugs.

Sushma Mosali

 Profile Answers by Sushma Mosali 

• Aug 12th, 2008

 

Though you are working on release the production issues come in first priority.

With production issue, first you check with version on which it was tested before release, so that we can be sure whether its an environment issue.

Raise a DR(Development Request) and then once its fixed and deployed to the QA env test that and then update the status.

Thanks
Sushma

Sushma Mosali

 Profile Answers by Sushma Mosali 

• Aug 13th, 2008

 

Though you are working on release the production issues come in first priority. With production issue, first you check with version on which it was tested before release, so that we can be sure whether its an environment issue. Raise a DR(Development Request) and then once its fixed and deployed to the QA env test that and then update the status. Thanks Sushma

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Apr 2nd, 2009

 

I note down the issue in the Bug Tracking System and mentioned the Severity & Priority level for the arised bug and make note on the causes happened(might be a Show Stopper). i informed about this bug immediately to my TL and request the Dev to fix the bug as early.

ashishks

 Profile Answers by ashishks 

• Sep 9th, 2009

 

Once you find any defect on production, log a defect immediately having "HIGH" priority.
Once developer fixes the defect test same issue and do sanity/regression testing depend on the time available.