The tests should always follow the requirements first and code second, if they fail you should look at the system requirements and deduce whether the tests are

The tests should always follow the requirements first and code second, if they fail you should look at the system requirements and deduce whether the tests are bad or the code is actually failing. If the tests are bad, re-write them to fit the requirements, if the code is bad... don't push your new code. It's very hard to figure out what the author really is unhappy with.