Maintianace of Test Cases,Test Script and Test Result
I have got number of modules to test.And Test Plan(Containing Test Cases in XL format)for each module.If I want to maintain the Test Cases,Test Script and Test Result using Test Manager.
1.What is the Standard practice of writing the test scripts?Are the test scripts divided into (according) to Test Cases?or a single Test Script should be written for each module?In case if i write a script for each Test Case, i will have to record all the steps right from start application in every script.And in case if i write a single script for the whole module.How should i corelate the test script with the test case and the test case Result?
Re: Maintianace of Test Cases,Test Script and Test Result
1- the standered pratice is to have 1-0-1 relationship between test case and test script.
2- It depends upon what is your module... if it includes many test cases.. writing a single test script is pain and also maintaince will be bit difficult for the script. Also you will face difficulty in analysis of Test results and logs.
As even one test case failure will be reflected as failure of whole test script.. inturn it will be reflected as failure of whole module.
so if you write one script per test case you will be able to see in Test case pan of log pass/fail status for ecah test case and in detail pan you will get script wise explanation...
You can have small routines for starting application and login and logout and you can call in all your test cases...
there are few advanatge of this approcah |-
1)- you need not to worry about many appliaction state as each test case will start at single point. So if in a suite run any test case fail...
you can have easy cleanup before starting of next test case...
2)- Each test case will be independent to other test case and can be run independently
3)- You can pick any test case and form the suite
while if start application and other initial steps takes lot of time and after login if you can execute many test cases you can have a seperate test script for starting of application and login... and after that from the main screen you can start your other test cases...
but in this case while restoring the base state you need to take care for next test case, after a failure. Your initial test script should run again.
You can extend this idea to break your test cases in small test cases if you believe in context driven test cases.