User requirements in testing

Imagine a situation: you are a QA engineer. Amount of bugs raises in every release. Product requirements can be uncovered only by someone in a smoking room or on the kitchen... And now imagine another situation: the whole team understands what, why and when the client wants.

How to get to this another situation? To change the job - the first and the total way that comes into your mind. I thought like this as well earlier, but! Few years ago there was a moment when I tried to test requirements and then formalize this process. There is quite little open information about requirements testing. I will try to tell, why requirements testing is needed, what to start with and what are the first steps of implentation the process.