By reading the title of this post, you might be wondering
that I can only see advantages of using Run Time Viewer during script development
and what could be its disadvantages?
Though, run time viewer provides visual verification
checkpoint to determine weather your script is able to navigate through the recorded
actions successfully or not. However, this should NOT be used as a final verification
point due to below reason:
Run time viewer is not an Internet Explorer (IE). This is a utility embedded within HP LoadRunner
which has very limited functionality compare to IE in displaying advanced
technologies elements e.g. ajax, applets etc. So, in case if any of the pages
will not be displayed by Run Time Viewer, this does not mean that your script
has anything wrong or not working. To verify that, you should be replaying your
script with full extended logs enabled and review replay logs to check for any error or
warning messages.
Another issue I have seen by keeping the run time viewer
enabled during replay in my past experience (especially with Oracle NCA
protocol script ) is that, the vugen
crashes during script replay. To get rid of this issue, HP recommended to turn
it off during replay.
Important point to be considered:
It's good to use Run Time Viewer during script replay, however, do not use it as final verification to determine the script successful replay. Do check replay logs and application under test logs (if accessible) to decide that. Also, in case vugen crashes during script replay with run time viewer enabled, try to disable it to get rid of this issue.
No comments:
Post a Comment