Anshoo_Arora

 Profile Answers by Anshoo_Arora 

• Dec 12th, 2007

 

It "depends" on what company you work for and how they deal in such situations. There is no right or wrong answer for this. It also depends on the Severity of the bug and the functionality of the application it affects etc.

ravikrishna2007

 Profile Answers by ravikrishna2007 Questions by ravikrishna2007

• Dec 21st, 2007

 

Well- Based upon my experience, normally post production Bugs are been treated  in a different way. If the client has any budget after the product has gone live normally we perform Post production testing.

As said No product is BUG free. So its a iterative cycle.

Hope this answers ur query

Pawi_lp

 Profile Answers by Pawi_lp 

• Dec 27th, 2007

 

Reproduce the bug. When a client calls he/she just says "The system collapsed when I did this" ... but the bugs are not that simple, so the QA has to reproduce the bug, find and report it so the developers can fix them easily.

smart.test

 Profile Answers by smart.test 

• Mar 25th, 2008

 

though its normal that bugs will occur even after release, if the bug has high severity the testing team will be targeted for that for not doing testing thoroughly.

in such cases, the testing team has to make sure whether the particular scenario of the bug has been covered or not in their test cases and also the environment in which the bug has been reported is considered or not while doing testing.

because the bug after release, will have a legal value depending on the terms and conditions between the client and the company, the testing team has to make sure the bug is not due to improper test coverage during testing cycle. the company can always go for bug-fixing depending on the contract terms.

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Sep 25th, 2009

 

No need to blame, who missed the bug. Let it be fix first, after that it should be discussed in the Team meeting. Try out the steps again and execute the bug and check that the same Test case already exists and check for the result. Here we should notable the Test Environment. If the Testing Environment and Client environment is differ means Testers is not responsible for that. If it is Tester mistake means, it should be avoid on further builds.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 22nd, 2009

 

As mathan_vel states in a previous response to this question, there is no need to point fingers and place blame.  We all make mistakes and it is best to focus energy on recovery than to try to find a scapegoat.

It is the responsibility of the test team to find the source of the issue (this part is true) and to take measures to ensure it doesn't happen again.  For example, if the problem was caused by differences between the test and production environments, the test team should attempt to bring the test environment in alignment with production in order for the issue to be adequately tested.  Here are a few possible causes (not an exhaustive list):

1) Requirements were not accurate and test cases were written to pass something that should have failed.

2) Requirements were not complete and test cases did not include something that should have been tested.

2) Requirements were misinterpreted because they were written unclearly or the tester simply misunderstood them.

3) Tester didn't author test case(s) accurately or completely and therefore botched or missed some steps when testing the problematic functionality.

4) Tester was in a hurry during test execution and rushed through the test case missing some important step(s) that would have uncovered a defect. 

5) The test environment is not the same as production and this defect slipped through the cracks due to these differences.

Pawi_lp

 Profile Answers by Pawi_lp 

• Dec 23rd, 2009

 

This kind of issues should help us the testers to see how did they find the bug? Why my team didn't find it?  Then as a team leader or project manager you should analyze why quality assurance didn't find it and improve those areas; it might be because a non covered environment, or becuase testers focus on testing that there are no errors in a process but don't test it as it the final users will do, I mean, sometimes testers don't know the business logic. The reason you find, has to help you to improve the process so it doesn't happen again in the future, because if it does, then someone should be warned.

Mady

• Jun 4th, 2018

 

Please answer this question considering the conditions i mentioned below
Few more conditions in this question :-
1. Also this QA is alone testing 7 more (7 different big projects) at the same time & all of them are on high priority.
2.He need to handle the communication with all the clients on calls & emails(clients of the projects he is testing) on daily/weekly basis.
3. Same QA is doing Requirement gathering for 2 more new projects on daily basis on calls with clients, for same he needs to prepare scope documents as well without any help.
4. testing time is not anticipated/involved in the scope like for example - there is one project of 2000 hrs developer has already taken 2100 or more hours to complete his part of work (because estimation of hours is intentionally done less to grab the client even when the management knows that this will going to take at least 3000 hrs to complete) .
5. Now QA has to test the complete system find the bugs get them resolve & sent to client for approval in 16 or 32 hrs of time because deadline is already breached.
6. Also the QA has to do random testing on all of the projects as there is no time to write test cases/scenarios etc.
7. the requirements are also not clear to the team as the requirement doc was not written properly.
8. lack of resources for testing - he has a 11 year old laptop no mobiles not other screens to do different types of testing.
9. he also need to resolve the help developers with there queries as developers never read documents before working they need spoon feeding from QA for every task they have to do.
10. management knows all that but still QA is the only person who does nothing & developers & other members are the productive ones.
11. Now if client finds any bug whether it is of low severity or high QA is the person to blame , he/she is complete responsible for everything which goes bad.
12. And if all goes good & client appreciates the work only Developer is going to get all credit & bonus not QA.

Lokesh

• Jan 24th, 2019

 

First of all as soon as we received bug from production
Step1: We need to identify in which platform the bug is reproducible.( whether all and any particular platform)
Step 2 : Try to reproduce same in test environment
Step3: If its reproducible in tets environment, check that scenario was covered during our testing phase
step4: if its not covered, test coverage not done proper and make sure to work on that.
Step 5: First prority should be fixing the production issue try to get it fixed by dev team and restest in our test environment
step 6: Release the bug fix on production
step 7: Have retro meeting with in the team and add it in improvements list