While the scenario you shared is an unhealthy practice in some organizations. Truth to be told that for successful delivery - Quality Is Everyone's Responsibility. Team needs to stick together and ensure that any defect found should have proper root cause analysis that will help in prevention for future.
However as QA, we need to review our test plans, automation scripts and regression plans to understand how a respective scenario/issue was caught later in Production and not in earlier iterations.
Also team should establish strong coordination to ensure the impact analysis for any changes made (new code enhancements/bug fixes) are discussed with team. This will be helpful in understanding change impact and coming up with robust regression plans accordingly.
While the scenario you shared is an unhealthy practice in some organizations. Truth to be told that for successful delivery - Quality Is Everyone's Responsibility. Team needs to stick together and ensure that any defect found should have proper root cause analysis that will help in prevention for future.
However as QA, we need to review our test plans, automation scripts and regression plans to understand how a respective scenario/issue was caught later in Production and not in earlier iterations.
Also team should establish strong coordination to ensure the impact analysis for any changes made (new code enhancements/bug fixes) are discussed with team. This will be helpful in understanding change impact and coming up with robust regression plans accordingly.
Yeah totally agree.
Thanks for your comment.