There's one more test: the embarrassment test. It's a simple test:
Will I be embarrassed if this build ships?
The embarrassment test gets to the heart of what you care about in a given release, showing the quality bar that matters to you.
For example, I'm working on a product that has simplicity of API as one of its core principles. So my embarrassment test includes looking at the API. Anything that seems sloppy, inconsistent, or kludgy is embarrassing. That's not something that would appear in a traditional release checklist, but it's something for which we will hold a release.
What's in your embarrassment test?