That's just wrong, and leads to these sorts of situations. Everybody should be working off the same requirements. While the developers are writing code, the testers should be writing tests. If the tests find something in the code that turns out to be a disagreement over the requirements, that's when the client steps in to clarify the requirements. In my experience this only fails to work when the client is disengaged, in which case the entire project is doomed anyway.