Documenting automated test scripts
We are getting ready to implement Rational Functional Tester (with Test Manager) in our testing environment. We currently maintain and manually execute a compliment of approximately 600 scenarios, which are housed in excel spreadsheets. Each worksheet is a scenario (script). I am finding that, with many tools, but with Rational especially, the documenting features they provide are somewhat lacking. Test Manager has severe character limitations in its text fields, which is making it difficult for us to input all the information that we are used to seeing in one of our paper scripts. As well, I find that Test Manager somewhat limits what information can go where. We normally have a section at the top of each paper-based script with the script name, the business 'module' it belongs to, the tester that wrote it and the date updated, the scenario details, the expected results and any baseline data we're looking for. Then we have columns for navigation, page name (we test a web-based app), field/object name and action performed upon it and finally the expected result for each step. I am not seeing a way to fit all of this nicely into the tool.
So this brings me to my question - how do you all deal with maintaining documentation to support your automated scripts? We need to be able to hand the scenario details to a business analyst or inexperienced tester or user and be clear enough in the details that they can manually execute a scenario and validate the results. This also helps new testers debug automated scripts (difficult to do if you aren't familiar with what the script is attempting to do within the application).
I'm open to any suggestions - currently we are just writing the path to the documentation in test manager's comments, and maintaining the paper scripts separately, but in future this will probably lead to the automated scripts becoming out of synch with the manual paper-based scenarios and I'm hoping to avoid this if possible!
Thanks very much in advance!
Re: Documenting automated test scripts
the same holds true with any other development project.
always comment your code.
also, try rational requisite pro to map test cases to requirements to scripts as well.
hope this helps.