I am having some difficulty with our dev team here concerning the info they give to me when it comes to testing. I have decided that I will create some sort of handover doc to ensure I receive all the relevant info. Has anyone had any experience of doing this previously? If so, did it work?
Convince your management that this is necessary to do your job correctly and cite a few instances when this has caused errors to be released or other major problems. It will carry a lot more power if it comes down from above. What you're talking about is important to implement. Every place I've worked has had this and it works well once everyone realizes its part of their job to follow it.
As suggested management buy-in is important. You could have a list like
1. Technical specification document
2. Functional specification document
3. Code promotion document (with configuration management elements)
4. Unit Test Results
5. Code review document
You should be super thrilled if you get even half of the above. I guess some kind of requirement specifications is a must though.
Another idea would be to write up actual defects against missing or incorrect subject matter in the documentation. Of course, doing this of your own initiative is likely to have 80% of the developers screaming at you.