eValid™ -- Automated Web Quality Solution Browser-Based, Client-Side, Functional Testing & Validation, Load & Performance Tuning, Page Timing, Website Analysis, and Rich Internet Application Monitoring.

If You Got An Error
This page describes some common problems that will cause a script to produce an error. Please check the playback EventLog -- it is the report by eValid of everything that happened in playback and often will prove invaluable in isolating a problem.

• Changed State
  Did you record a login and forget to also record the logout? eValid may remember your login and the playback if you are already logged in may fail.

• Login With Autocomplete
  Sometimes the built-in autocomplete will fill in your account name for you, based on prior history, but you can't be sure that will always be there (remember you may have issued a DeleteCookies command), so it is good practice to type in each account name in full.

• Changed Page
  If one or more pages you visited during the recording has changed substantially -- so much so that the Adaptive Playback feature is unable to compensate -- you may see a test failure.

• Multiple Playbacks
  There are two unitary resources on your machine: the Cache and the Desktop. If two (or more) eValid copies are running they could conflict with each other in terms of what is put into (and found from) the Cache, and actions that interact directly with the desktop.

• Pages Not Available
  Sometimes pages that are critical for your test really are not available all the time. If you know a page availability is questionable it may be wise to avoid it because inevitably this will cause playback failures.

• Dynamic Frame Paths
  If the fames on a page arrived in different order, and they are referenced by the original (at recording time) arrival, then playback may fail. If there are complex frames inside frames it is generally better to record these interactions with natural frame names (i.e. not with "ordinal frame numbers").

• AJAX Synchronization
  Typical AJAX applications may require augmented synchronization steps because the AJAX part (that is, JavaScript programs running autonomously) may not fully synchronize with eValid's built in synchronization modes. You may wish to consult the Synchronization Mode Summary page.

• Alternative Recording Mode Needed
  When you are making a recording it is a good idea to watch the script window as eValid creates the script. If you take an action that does NOT result in something appearing in the script window, then you may need to use Application Mode, Desktop Mode, or Modal Dialog Mode, etc.

• Page Focus Not Reliable
  What you see on the screen may not be 100% consistent with what eValid sees. For example, you may think that a window is in focus, or you may have issued a command to bring a window into focus, but whether it is or not is a function of internal state changes. Changes in focus are more reliable when accompanied with Wait 100 commands to give the operating system time (and eValid) to "catch up with your intentions."

• Adaptive Playback Flying Blind
  If you have references to DOM elements but do not have unique ID's (or other unique DOM attribute) don't be surprised if Adaptive Playback behaves in an unusual way. For example, if you have three identically named buttons on a page and you clicked on the third on, if they move around eValid will click on the first one that it finds (usually the first occuring one).