Testing Production Issues

Say you are working on a release and productions issues occur that are in need of a fast fix, test and deployment back into the production environment.

How would you handle that

Questions by zannetti

Showing Answers 1 - 0 of 0 Answers

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.

  Was this answer useful?  Yes

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

  Was this answer useful?  Yes

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

  Was this answer useful?  Yes

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.

  Was this answer useful?  Yes

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.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions