| || |
Best Practices on Script Recording and Re-using
Are there any Best Practices for recording Load Runner testscripts and re-using them.
I want to avoid the monotony the script designer has to undergo for recording same workflows again and again, for various upcoming version of software. The point is although the workflow is same there are chances of URL action getting added or removed in news versions.
Can it be automated to certain extent,
1) Can the web_reg_save_param search etc, can this be put in header files or probably like Tag Libraries as in Java. ?, so that the changed can be made at one place and in actual script we need to just call a respective tag or function
2) Can verification points be defined as templates and put automatically for respective URL's
I would like to know the best practices that would have us to reuse script or if re-using is not feasible then atleast the re-recording and customization process should be made easier.
Your inputs will be really valueable.
Re: Best Practices on Script Recording and Re-using
If you know that you will have to re-record scripts you can looked into enabling correlation in your recording options. You can set rules to pick up and do correlations that you used before for you when recording the script the next time. There should be plenty of literature on it once you see it in the recording options.