crazytester

 Profile Answers by crazytester 

• Jan 13th, 2010

 

We need to check 1st whether it was within our testing scope or not. If Yes then we have to do a RCA ( Root Cause Analysis). RCA report must be delivered to all the stake holders. 

mattd1

 Profile Answers by mattd1 

• Feb 28th, 2010

 

When a bug is found in Production Environment
1. As 'test_good' referred, you would have known by now if the failure falls within your testing scope or not. You are safe if it is outside your testing scope.

2. The RCA on the bug will most probably tell you that your test environment and your production environment are not similar. Find exactly which factor contributed to this failure.

3. Recommend you QA manager to take measures to ensure that the QA Environment is similar to the production. If this can't be done, then mention this limitation in your future test plans.

Happy testing!

sarvesh4u

 Profile Answers by sarvesh4u 

• Mar 5th, 2010

 

If Bug is find in the Production Environment then the very first step one should take is to do the RCA. Once you are known to the exact issue then you need to inform your project manager or QA manager.

The report part should include the exact impact of the bug found, also you should be ready with the proper explaination for the same. Sometime it happes that the scenario in which the bug invokes is rare so, such kind of analysis data will help you decide the release time of the fix.

vaibhavst

 Profile Answers by vaibhavst Questions by vaibhavst

• Mar 23rd, 2010

 

These are the steps that we followed when we had production bug

1. As other testers suggested we should check whether the bug falls within our testing scope or not. If yes we need to move to step 2 or else check out the traceability matrix and explain to manager that why it was not covered. (may need to explain with some proofs such as mails from clients)
2. Find the test set where we have covered the scenario under which the bug arisen
3. Check out the configuration related to the module where the production bug is found. In most of the cases it will be due to configuration changes
4.  Check out for the change in SIT and PROD operating systems & dbms versions including any upgrades or patches installed on systems etc
5. Prepare a RCA report which should contain all the factors mentioned in above steps
6. Follow up with support /Dev team to check the status on the ticket which was opened for the prod bug.

Tusharbhate1

 Profile Answers by Tusharbhate1 

• Mar 31st, 2010

 

The action taken would be differ as per the conditions.  First of all need to confirm whether the raised production bug is from your testing scope.  If yes then we need to know whether it comes under SLA (Service Level Agreement-Agreement between Client and Vendor).  Many times vendors are not owning the responsibility to test bug once product has been released into production.  These type of Bugs can termed as 'Warranty Defects".  

Yallappa

• Sep 23rd, 2012

 

we make sure that while inserting application into production server we go for user acceptance testing that is easy step to prevent the bugs in the production server.

Kumar

• Jul 14th, 2014

 

Firstly as a tester, I will reconfirm whether it’s a defect OR NOT. And also verify that in Lower Environments (SIT / UAT).
If it’s a Defect and within the scope will notify this to entire project team with the Severity / Priority.

If it’s a high Priority to the Business, will go for immediate Scrub (Piece of code) in to the Production.

If NOT will take care of that in to the Next dates / Release.

Torsten Zelger

• Nov 18th, 2014

 

Check your regression test suite whether it contains a scenario that could have detected the issue before it went to production. If yes, find out why it was not executed and give it a higher priority for the next regression test session. If the test case is missing in your test suite, add it to the suite so this issue will not happen on production.

Devina

• Jun 28th, 2015

 

If the defect that has occurred is part of test requirement than check for below points:

- Try to re-produce same defect on testing environment, to make sure we have not missed it.

- Check with the developer if they have delivered the correct code in production environment or not.

- If roll back is possible, try to roll back the new code on production environment and test the same feature on previous code, to see if this was already present in production environment.