Quality is delighting customers
Tester is not building anything, so the quality is not actually testers' responsibility. Testers are just saying, that software works or doesn't work as expected. We can't block the release, we can't release the application. The decision is done by product manager. And quality is built by developers.
So who is responsible from quality? Everyone. If anyone passes that responsibility, the final result will be bad.
Quality is a sport of Team
That is because the the others lack to understand the importance of testing and take it as a negative activity and also an additional cost to the project! Actually such people are not clear as to what exactly do they want from testing and set up unrealistic expectations or maybe they actually hire testers for the purpose of point the finger at when ever anything goes wrong with the project without realizing that this will eventually affect their own business by creating a negative impression quality wise!
This is not a general conclusion but yes it has been seen quite often!
And as per a fellow tester; That and it's easier to blame the tester than it is to fix a broken system or process.
The only thing the tester does is provide information about the state of the software. Testers don't fix the problems they find, they don't have the authority to prevent the software from being released, and they don't create the problems.
Of course, they're often the last people to look at the software before it's released, and they're often the bearers of bad news, so it's human nature to blame them.
Yep.... teemu , i agree with you but still when anything is reported by either client or customer , manager ask first to the QA person and he has to give answer ...he is blamed for the same that's the human tendancy
Development team develop the software as per the requirement document and testing team validate the things ...
So both team are equally responsible for any good and bad news in terms of quality..