Has anyone here been asked to write documentation describing all the unit tests they have done on their code, for QA to review, with pass/fail signoffs on everything?
The reason I ask is because I've never been asked to do this kind of documentation, and it's not even "unit tests" they are asking about, what they really mean is some functional testing done on a web application that covers the use cases, but "not in as much detail" as the QA teams test cases. I sent QA a draft of what I think they wanted, and asked for feedback "because I've never had to write this kind of documentation and I'm not sure if this is what you want", and got back a reply, "I'm surprised that you do not understand ... I'd expect a developer to know what unit tests are and to have done this for all your code in the past" with a CC to my project manager, which was basically trying to make me look bad, and that basic kind of attitude. I replied that our definitions of "unit test" were completely different.... Wondering if there's any opinion, because I am really pissed off right now.