QA guide

Tony et al We have made quite a few notes as we went along of things that we'd like to add to the qa guide, I was planning to do this in small steps by sending stuff to this list to review first, but...I'm wondering if we shouldn't have a bit more of a plan than that? Perhaps at least a list of subjects that the QA guide could be extended to cover? Random thoughts for starters: What platforms should I test my test on? What should I do if I think my test might fail on another platform but I don't have access to that platform to try it out? How can I make my test case easy to read and understand if it fails? How will people tell me if my test case needs fixing? How can I tell if the function I want to test already has test cases? And if so which functionality/lines of code do the existing tests cover? Is there a time limit for running a test case - eq if I want to put a "sleep" in there would that be a problem? Can you add more? Zoe Slattery