01-18-2010, 06:11 AM
Hi All,
I am currently working on Test automation of a web application. I am going with an approach where I am creating one reusable action to cater one application feature. On the other hand I am using one Test per Application module.
So far things are fine for me, but we have a third party QTP consultant with us to review our work. In our last discussion He suggested to keep one reusable action per test rather than having one test with multiple user actions. This way your tests would be easier to maintain.
This didn’t strike my mind as it will increase number of test scripts in multiplication. May cause dicrease in script execution as well
Can anyone suggest some Pros and cons of having one reusable action per test
Waiting for your valueable feedback
I am currently working on Test automation of a web application. I am going with an approach where I am creating one reusable action to cater one application feature. On the other hand I am using one Test per Application module.
So far things are fine for me, but we have a third party QTP consultant with us to review our work. In our last discussion He suggested to keep one reusable action per test rather than having one test with multiple user actions. This way your tests would be easier to maintain.
This didn’t strike my mind as it will increase number of test scripts in multiplication. May cause dicrease in script execution as well
Can anyone suggest some Pros and cons of having one reusable action per test
Waiting for your valueable feedback