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
This page describes the NAV and NO_NAV command tags in eValid. These definitions apply:

1. NAV means to wait for navigation to complete. eValid's internal "navigation complete" logic is activated. This tag may need to be appended to a command that needs to activate the "navigation complete" logic. Some eValid commands are recorded with no NAV tag, and do automatically wait for navigation to complete.
2. NO_NAV means to NOT wait for navigation to complete. eValid's internal "navigation complete" logic is suppressed. Only a few commands accept this extra tag.
3. If a command that ordinarily waits for navigation should NOT, then you need to append NO_NAV to turn the "navigation complete" logic OFF.
4. If a command ordinarily would NOT wait for navigation, but you want it to, you append the NAV command to turn ON the standard eValid waiting sequence.

Action Descriptions
This table describes what is going on with these commands. Some commands have mandatory navigation which can be blocked with a NO_NAV, and other commands have optional NAV's appended when navigation happens in the recording process.

NAV, NO_NAV Creation and Processing
Class	Type of Action	NAV	NO_NAV
Recording	Mandatory Navigation Logic Implied	Group A: Navigation Commands These commands imply that a navigation is to happen.	None
	NAV Tag Added Automatically by eValid During Recording When Needed	These commands may have a NAV tag added to them automatically when eValid senses that a navigation has happened: Group B: Element Mouseover Commands Group C: Click Commands Group D: Keyboard/Desktop Commands Note: Sometimes (~2% of cases) a NAV is added in error, a fact only known after a test playback causes a "Navigation Time Out".	None
Playback	After Editing of Script to ADD the Tag	These commands process the NAV tag when present: Group B: Element Mouseover Commands Group C: Click Commands Group D: Keyboard/Desktop Commands Group E: Index Motion Commands	ONLY these commands process the NO_NAV tag when present: FollowLink IndexFollowLink A NO_NAV on other commands would produce a syntax error.

Command Group Definitions

• Group A: Navigation Commands
  InitLink, FollowLink, GotoLink, Redirect

• Group B: Element Mouseover Commands
  ElementClick, ElementMouseOut, ElementMouseOver, ElementBlur, ElementFocus, ElementMouseDown, ElementMouseUp, ElementDblClick

• Group C: Click Commands
  InputImageClick, ButtonClick, SubmitClick

• Group D: Keyboard/Desktop Commands
  EnterKey, KeySys, clLClick, xyLClick clLDrag, xyLDrag

• Group E: Index Motion Commands
  IndexInputValue, IndexElementClick, IndexElementEvent, IndexElementMouseOver, IndexElementMouseDown, IndexElementMouseUp, IndexElementMouseOut

Application Notes
We know from experience that in some cases eValid's ability to sense navigation causes NAV tags to be added inappropriately, and we know that in some cases (mainly those involving certain -- but not all -- AJAX/JavaScript support libraries) it is necessary to add NO_NAV tags.

It appears that there is about a 1% recording failure rate, requiring correction by adding or deleting NAVs, or by adding or deleting NO_NAVs. We believe that this rate is acceptable in practice; and we also accept the reality that a 0% failure rate is unattainable with present technology.

In practice you will know that a NO_NAV is inappropriate when the command that contains the tag experiences a "Navigation did not occur" message in the EventLog even though navigation actions may already have been taken.

In such a case, the user will need to manually add NO_NAV tag to prevent the command from setting up an unnecessary "wait until navigation is complete" operation.