the topic is a little old, but I fear that it is still a relevant one.
If you are a tester and feel guilty for some aspect of your work or somebody wants to blame you for not testing good enough, then be aware of the following things:
1. SW development, including the quality assurance is a team sport.
So if the user finds an issue, the whole team is responsible to analyse and fix.
There are a lot of reasons why defects occour: requirements incomplete, defect in source code (typo, loops: one to many or to less), user error, interferences with other systems running at the same hardware as the SUT and so many more.
2. The customer decides, what level of quality to achieve.
He/she pays for development and testing. If there is not enough budget to deliver a product which is tested well/long enough, it is the tester’s responsibility to inform the customer about the risks and what kind of mitigation the tester would propose.
3. Learning and continuous improvement is not up for discussion
Same with skills and knowledge - if their is no budget/time/willingness to support team members incl. testers to learn what they need to do their jobs well and better, there is a higher risk for defects.
Learning and continuous improvment is not up for discussion but a duty for everybody (and supervisors should push).
4. Be aware of humans
A former Scrum master told us: “Keep in mind, that everybody is doing his/her best at every time. If you have a good day, your “best” is just great. If you have a bad day, your “best” is not that great, maybe it’s ok or even not okay.”
He made me aware of differences beetween us humans: everybody has his/her talents - and weaknesses, me too.
Means: You create a test strategy and execute it - in all conscience. Why should you feel guilty for doing your best?
5. The concept of “guilt” doesn’t fit.
Guiltiness is not helpful.
- If people feel guilty, they feel bad, too. Are they then able and motivated to do their very best?
- Guiltiness means looking backwards. This also doesn’t help to avoid defects in future, does it?
- Guiltiness and negativism are sibblings. And kids of that kind nobody wants to play with.
6. Feel uncomfortable instead of guilty and ask yourself “why”.
What are your reasons for feeling uncomfortable with the results of the teams work? What can you do to avoid the reasons?
Humans want to feel good. Feeling uncomfortable is a good motivation to change something
I think there is only one reason, why a tester should feel uncomfortable (but not guilty): In case he/she knew better but did something else: e. g. executing a more simple test case instead the neccessary one to go home in time; not reporting risks, to not be the one who brings bad news (and will be blamed for). Reasons like this.
And this is completely ok - if you learn from it