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

Summary
eValid's WaitRedirect command provides an important, but sometimes troublesome, capability. This page explains the command and how to maximize script stability when WaitRedirect commands are added to an eValid script.

Nature of Command
WaitRedirect commands are put into the script during the eVlaid recording phase when eValid detects that a navigation has happened that is NOT the result of a user action. This is a correct action of the script recording process, because eValid's goal at that time is to record "what happens" as accurately as possible.

These WaitRedirect commands could be added by eValid to a script during the recording process for a number of reasons:

1. The page navigated to by the user actually does a redirection to a different page. In this case, eValid's recording may in some cases show the new page as the target of a WaitRedirect command.

2. Autonomous action within the current page, for example due to JavaScript/JScript actions, that causes a secondary navigation.

Problems & Advisory Comments
In some cases a difficulty arises during playback when, in effect, eValid has recorded "too much" information, i.e. extra WaitRedirect commands that, on playback, interfere with correct operation. In cases when WaitRedirect commands that are put into the script during the recording process are NOT needed during playback, the most-common solution is to comment out the "extra" WaitRedirect commands.

The most common error you'll see is when the WaitRedirect is executed and no navigation occurs. When this happens you'll see a "Redirection did not occur" message in the Event Log. Reliability of playback may be improved by commenting out the associated WaitRedirect command.

Additional Technical Note
Note that the complementary command used by eValid is the NO_NAV tag that is appended to a command that orginarily WOULD produce navigation, but which for some reason does not produce navigation. The NO_NAV tag prevents eValid from waiting for a navigation that will not occur, just as the WaitRedirect command assists eValid in tracking user intentions when navigations are spontaneous.