Well, these thoughts are obvious when we think about something as ubiquitous as quality. Nevertheless, during the course of my working career I've found that quality is much more than these simple statements. Yes, of course, good quality code with less/no bugs should be part of the quality but its not the only thing that defines what quality is... Unfortunately, many people including Quality Managers are not aware of it.
What qualifies a piece of software being 'High Quality'? Generally people define them as piece of software where test case pass % is 95+ and tools which are used to evaluate the code is not complaining.
Though these are important aspects of delivering a good software but have we ever thought what will happen if we miss writing a part of software / test itself. After all test cases are also written by people in the organizations who write code. No tool or pass percentage will complain about that.
So here is how I'll define quality "Quality is perceived software functionality as compared to what was expected out of it"
Yeah...you read it right...this is what quality is and its more of a perception than what you software is actually capable of doing. You may have delivered the excellent quality code with 99% pass rate, it may still not be sufficient to fulfill customer expectations.
What I'd like to emphasize over here is that the quality matrix of an organization which is mainly constituted by data generate out of test reports are not the only indication of quality.
Just look around any popular open source as well as proprietor software like Linux, Jira, office etc. All these are very popular software but at any point of time they have hundreds if not thousands of open bugs, still they are popular and people are happy using them and rate those software's as high on quality.
Quality cannot and should not be only determined from the bug report but should be determined by whether or not it solves the intended problem of the user in a best possible way. People will happily live with few bugs if they like your product and if it satisfies their requirements.
Think about iPad's and iPhone's, their software are neither bug free nor having more advanced functionality than others, still people love them for the ease of use and do recommend them
Finally, no matter how you test your software, its the end user who decides whether or not its of good quality. Unfortunately we don't even know what benchmark he/she will use to decide on the quality of your product.
To conclude..don't only consider matrix generated from silos of four walls within your organization. They are helpful but not everything.