I'm am rather new to QA and would like any and all comments on what I've put together this afternoon. Our company is in the middle of an aquisition and I want to put together test cases/procedures that I've used so they are useful for the new company. I never had a consistent way of documenting test cases and would like to create some doc to do so. The TP1.01.doc file uses a template that I downloaded from a post in this forum. Am I using this template correctly? As you can see in the .txt file, I am planning on creating at least 44 of these Testing Procedure documents. Realistically, I will need around 60 of these docs to cover our entire product sufficiently. I am wondering if I am going about this in the wrong way so that I needn't waste my time. If so, any suggestions as to what I should do to get organized? Again, my entire purpose is to get all of my test cases down on paper in one place so they will not be forgotton and so that the new QA department will have something to work with.
Yes, I want to put references to the requirements, but the old company never had an official requirements document! The reason I am putting so much effort into these is because they are actually taking me over to the new company.
Congrats, jeni, it's excellent that you won't be finding yourself out of work!
Having the reference for the requirements or use cases is probably good, based on the lack of documentation currently. It shows that you would like to provide that kind of traceability, but it's not currently available.
Again, I think that if you continue to create your cases in the level of detail you are here (assuming they're correct for your environment, which we can't know! ), you will be providing a very comprehensive set of documentation that also shows your committment to the product and the new company.
Good luck when things change over! Takeovers can be difficult to get through, but you'll make it!
"They thought blueprints were too sad, so they made them yellow.."