What steps you would take when client identifies a production issue? How will you react after production failure? What steps you consider after production failure? You would’ve faced above questions during your technical interview. In this blog post, we will discuss about how to address this questions, so that you can score more points and impress your interviewer.
It is bad luck, and risk when your client identifies the failure in the production environment. Also, you would have expected a role change or for good hike/appraisal ratings, but due to this miss in the defect identification, things FOR you might change. Do not panic. You can handle this situation without any hassles.
Steps to take after production failure – Software Testing Interview Question and Answer
Once the production issue is identified, first step is to validate the failure. Address below questions carefully:
- Are you able to reproduce the failure? During defect/failure reproduction capture a video recording.
- Are you able to reproduce the failure under defined environment/configuration specifications? Like supported Internet browsers, OS versions, Service packs etc.
If you are able to produce the defect, then validate the following, else submit the recorded video to the client.
- Is the scenario/failure in-scope?
If yes, check the following things, else no need to worry, simply inform the client.
- Are you able to reproduce the defect in the QA/Staging/Pre-Prod/UAT environments?
If yes, then the things will be critical, else inform the client about defect reproduction in all the testing environments
- Now check with your developer about the code build details.
- Build should be identical in all the environments.
- Validate the test data, test steps, expected and actual results, prerequisites, conditions, and other dependent interfaces, third party APIs (if any)
In this stage, you will likely be able to identify the root cause of the failures. Most probably, developers might have missed files to deploy in the server unless there is an mistake from testers side.
If I missed anything, please let me know in the comments. Happy testing!
Thanks for visiting QAInsights! Check out our new portal Testifications.com to get updates on Software Testing related certifications. We’re always posting interesting articles on QAInsights. I request you to subscribe so you don’t miss out anything.
Searching for QA Jobs Openings, check it at www.QAJobOpenings.com
Want to start a blog like this, please visit SpidyDomain to buy cheap web hosting and register domain.
Image courtesy of Stuart Miles at FreeDigitalPhotos.net
- Unboxing Apache JMeter 4.0 - February 13, 2018
- Swagger Inspector and Swagger Hub Hands-on - January 25, 2018
- Speedometer 2.0 Testing - January 17, 2018
- Performance Analysis of Rajini Makkal Mandram Website - January 8, 2018
- Must Have Tools For Technical Founders - November 9, 2017