I find posting the blame is the wrong way to think about it but to answer your question it could be a single person or everyone. I.e could of been a business spec that was not communicated to the dev team or it could be the tester that did not test a specific COS appropriately or everyone for that matter.

Whats most important to me as a QA lead is what can we do to prevent it from happening again. After every roll out we review leaked bugs and analyze what we could have done to prevent this. Our company currently separates the bugs into the following category.

• Requirements(COS)
• Unit Testing(Low level dev testing)
• Acceptance testing(Verification of COS)
• Regression testing(Post QA related functionality)
• Automated testing
• Other
• Not sure

I find currently a lot of our recent bugs have fallen into the regression section. Using this modal has really helped our team analyze our strengths and weaknesses in terms of preventing bugs being released.

I find posting the blame is the wrong way to think about it but to answer your question it could be a single person or everyone. I.e could of been a business spec that was not communicated to the dev team or it could be the tester that did not test a specific COS appropriately or everyone for that matter.

Whats most important to me as a QA lead is what can we do to prevent it from happening again. After every roll out we review leaked bugs and analyze what we could have done to prevent this. Our company currently separates the bugs into the following category.

• Requirements(COS)
• Unit Testing(Low level dev testing)
• Acceptance testing(Verification of COS)
• Regression testing(Post QA related functionality)
• Automated testing
• Other
• Not sure

I find currently a lot of our recent bugs have fallen into the regression section. Using this model has really helped our team analyze our strengths and weaknesses in terms of preventing bugs being released.