Today I was reading an interesting internet article by Andy Jordan called Quality, Not Testing. Not in the least because of the comments added to it.
As Jordan writes, quality and testing "are ... very closely tied together" and as such, I would say, we tend to use them synonymous to each other. But they are clearly not, is Jordan's plea. Needless to say I fully agree with him. You can argue about the details of his article (see the comments!), but the basic thread is right in the bulls eye and gives us the opportunity to evaluate the way most of IT projects tend to position quality and testing. In most cases unconsciously.
Have a look at this blog post of mine ... [:O]
Just read the article by Andy Jordan. ;-)
One give-away: "Testing really is nothing more than determining whether the quality standard has been achieved."
I think testing and quality work side by side and these are two essential things. You have written well but I am not sure what you want to say.