That second part of the request was the sticky one: just showing that a text item was there on the results page was not enough. You really had to know there was a real live link that someone could click that would take you to a specific URL.

The resulting SEO Demonstration Script is a parametric script, expressed in terms of the name of the search engine, the locations of the search-for string entry field, the location and properties of the "go-get-it" action field, and of course the input search string and required URL fragment. To make the script 100% reliable -- we don't want to have to rewrite this script if the search engine pages change -- we worked out the Search Engine Parameters for a number of different search engines.

We ran the parametric script using one of eValid's methods for multiple-script playbacks (e.g. DataSynthesis mode) with very interesting results.
>> Complete Article

• Analysis of the DOM of the page for particular properties.
• Explicit playback synchronization based on page properties.
• Use of eValid page-position-independent "index motion" commands.
• Support for AJAX operations, including synchronization.
• Use of eValid's ability handle Regular-Expression matches.
• Use of one of eValid's many page-based validation modes.

The result is our Application Support Coverage Matrix, which describes what we have done so far.
>> Complete Article

• If you run into a tricky problem testing a website, you might consider checking out the 40+ entries in our Worked Solutions Resource. You'll find a wide range of already-worked examples showing how eValid solves typical testing situations.
• Watch some of our Annotated/Animated Movies. You'll see how eValid works from the GUI level, and see how eValid deals with specific testing situations.
• For general eValid usage you may wish to check into the set of our "top 99" Power User Tips & Tricks. They cover everything from simple functional testing to detailed LoadTest experiment development.