| || |
Using Multiple Actions
Is it preferable to organize scripts breaking into multiple actions?
One drawback i found was - as the number of action calls increase, time taken to load the script also increases.
Advantages are - whenever there is a change in the application, we need to change only one action as the same is being called across.
Pl suggest me on the best way to organize scripts.
Re: Using Multiple Actions
IMHO there is no "one size fits all" solution. The best way to organize scripts is the one that fits your team and situation best.
It's true there is a little break point between calls to external actions, but is that such a big deal? If you run your tests unmonitored what difference would it make?
There's been a lot of discussion on QTP methodology on this forum. Different views include reusable actions and function libraries. Both work well and accomplish nearly the same thing. Take the path that fits your skills and
"There is no spoon."