473l wrote:Does eValid have a script debugger? How do you debug scripts?
When a script is first read into eValid it is parsed into an internal format and any errors are noted to the user. The idea behind this is twofold: (1) the internal script form is very compact and thus very fast, so there is very low overhead at test playback time; and (2) eValid never tries to play back a test that has errors in it. You should think of this as a pre-compiling step.
Of course you could have a script that is syntactically perfect -- no errors in the pre-compiling stage -- that makes no sense relatiive to the web application under test. In that case you can: (1) insert
Breakpoint commands that put the playback engine in Pause state; or, (2) use the SingleStep command mode (on the browser face).
Experienced eValid users employ a combination of these to get to the right parts of a script. Usually a
Breakpoint followed by a series of SingleSteps. It's a good idea to watch the EventLog while the test is playing back, so you know what has actually happened.
eValid Support