LoganR wrote:Hey guys.
What is the best way to debug a script that seems to be failing?
Great question, thanks for posting.
The solution that we prefer is as follows:
(1) Make sure you have detailed timings turn ON.
(2) Position a view of the EventLog on your screen alongside the eValid Browser.
(3) Load up a script that has a "Delay 100000" command; this causes a fixed delay of 100 seconds.
Or you can use a Breakpoint command
(4) Start playback until this long delay command is executed.
Or the Breakpoint command.
(5) Pause the playback.
Now, using still-active eValid browser, type or mouse/click whatever you want on the browser.
Take any action you want.
You have an active browser that records in the EventLog the effect of what you are doing.
You can even see AJAX pages various components arrive and be processed in parallel/serial mode.
OR, you can advance your actual script using the Single-Step mode on the eValid browser face.
Here is a page that describes this in some detail: http://e-valid.com/Products/Documentati ... iming.html
The idea of this is that you can study the actions taken and learn from the material in the EventLog.
This will help you identify the any problems with your script.
-- eValid Support