| || |
How do you write test scripts
We write test scripts using MS Word and have multiple test scripts for different areas of our applications.
For one of our applications we have over 20 test scripts we have to run every time which were getting a bit fed up of.
So what i would like to know is how other people manage and write there test scripts?
Anyone have any suggestions please let me know
If the time, energy, and money required to write and maintain the scripts exceeds the risk value of the defect(s) you are trying to prevent, you should really consider an alternative.
Since you're using word, have you considered using screenshots to document the test case instead of manually typing in the steps? At one of my previous projects, the client had well-documented operations guides. Instead of replicating that effort, we referenced sections of these documents from our test scripts.
I'm not sure what you mean here. Why are you "fed up"?
Originally Posted by Glover
If for some reason you feel you have "too many scripts", then consider:
- Are there any scripts which are no longer needed?
- Are there any scripts which aren't needed every time?
- Can you reduce the frequency with which you need to "run" them?
- Can some of the scripts be re-written to be shorter?
- Can someone else "run the scripts"?
- Can you get more people to help?
- Can you automate some or all, and run them overnight, unattended?
Sounds like you would be able to combine a lot of those scripts, maybe cut some parts out that are duplicated. Sounds like you do a lot of regression based on your statement above. Maybe you are running scripts all the time that don't need to be run all the time?? Just a thought.
I'm a believer is using a TCM (Test Case Management System)
Have all your test cases in a system that's driven by databases. Then track the following.
* count of number of times the test case has run. (actually this is usually done automatically)
* number of times a defect has been filed that's related to this test case. (Modern TCMs with bug tracking integration will probably do this already)
And 1 more custom field for ranking the test case. (if the TCM doesn't support ranking)
As you do your test, start using these the 2 fields to prioritize the test cases (reprioritize once a release cycle as part of the post mortem activities). (I recommend a formula of 10 x Number of Defects per release cycle + Number of times run as a way to prioritize test cases) The test cases that drift to the top you automate, put it into CI and forget about them. The test cases that drift to the bottom will get de-prioritized and eventually deprecated.
Last edited by dlai; 01-24-2013 at 08:29 AM.
how do you write test scripts . refer this link it will help you http://gojko.net/FitNesse/book/ch05.html
Not useful at all, unless the original poster decides to use FitNesse.
Originally Posted by muthu_qpt