eValid™ -- The Web Quality Suite Browser-Based Client-Side Functional Testing and Validation Page Timing/Tuning Transaction Monitoring. WebSite Spidering & Analysis and Realistic Server Loading. © Copyright 2000-2012 by Software Research, Inc.

Summary
Applied as a Universal Web Test Agent standard eValid features can handle any kind of monitoring, testing, and web page analysis requirement, on a local or remote machine. Special eValid commands and licensing protocols enable each script-based playback to create a full range of detailed data.

As a Universal Web Test Agent eValid offers reality, generality, flexibility, trustworthiness, capacity, and reliability. eValid can analyze virtually any aspect of any web page -- intranet or extranet -- that is viewed through a browser.

Universal Web Test Agent Benefits
The main benefits of eValid's deployment as a Universal Web Test Agent include:

• Universal. Simulate any browser-based transaction of any complexity with full realism and comprehensive data collection.
• Powerful. Data collected can range from low-level HTTP/S download timing details through complex transaction results.
• Scalable. Small footprint, control of cache, and intra-agent synchronization capabilities assure high scalability.
• Realistic. Tests use the full browser capability. No approximations; nothing is left out. Tests are 100% real and indistinguishable from what a human user does. eValid generates reliable, detailed, accurate, noise-free data about each user-oriented transaction it performs.
• Free Standing and Self Contained. eValid runs as a browser on the client machine and requires no special or unusual configuration elements.
• Server Immune. Being done 100% from the client perspective eValid tests are immune to variations in the server technology used for the web page or website under test.
• Runs Anywhere. eValid playbacks run on most Windows platform, remote or local, attended or unattended.
• Uses Normal Connectivity. eValid uses normal web connectivity for public website and private intranet testing, monitoring and analysis tasks.
• Reporting. Logfiles are simple in format, easy to analyze, have comprehensive detail, and are spread-sheet and database ready.

Variable Data Focus
The information collected during each eValid script playback can record different levels of detail. Data is gathered inside the eValid browser to assure that the information corresponds exactly to customer experience.

• URL Level. URL data includes URL availability, total response time, size, creation date (age), etc.
• HTML Navigation Level. Page navigation and rendering data includes total page size, number of components, number of separate files, detailed component download times, total download time, total download + rendering time (user experience time).
• Context Level. Maintains user context including cache activity, session cookies, persistent cookies, secure session IDs, internal namespace settings.
• User Session Level. Multiple function, multi-step transactions. Accurate user timing, multiple window activity, opaque-object activity, off-browser (desktop) activity.

Variable Data Collection Detail
The amount and detail of data collected during each eValid agent playback can be varied, depending on the needs of the test. Log files are individually selectable.

• Comprehensive Event Log Data. The event log records complete information about every action taken during each playback.
• Performance Log Data. The logs include detailed page component timing data.
• Message/Error Log Data. These logs reflect only programmed playback messages, including error messages.
• Timing Log Data. These logs including only specific pre-programmed event timing results.

Operational Details
As a Universal Test Agent eValid establishes a powerful and sophisticated testing environment that has flexibility and power for any testing or monitoring situation.

• Script Creation. Test script creation is easy, fast, and efficient. Users can create and confirm scripts before submitting them for field use.
• Built-In Script Playback Constraints. Scripts can be localized or generalized, limited to maximum playback rates, and can report activity and log data to any destination.
• Ease of Operation. eValid can act from a scheduled batch command line or it can operate autonomously using AUTOPLAY control scripts.
• Scalable for Monitoring. Agent machines can support large numbers of eValid playbacks. The run-time footprint is approximately that of a browser. A typical Windows machine can handle multiple simultaneous playbacks.
• Playback From Minimized Browser. Playbacks can run minimized using the built-in Minimize command.
• Automatic Desktop Synchronization. User keyboard clicks, when required for session operation, are synchronized to be non-interfering using built-in Lock and Unlock commands.
• Windows Service Support. eValid tests can be run as Windows services for unattended operation.
• Self Reporting. The event log of activity collected during playback can be POSTed or emailed to a collection center for analysis.
• Cache, Cookie Control. Scripts can manipulate the cache and cookies via inline commands.
• Automated Housekeeping. eValid scripts can be configured to clean up after themselves.

Typical Usage.
Here is a general outline that shows how easy eValid is to work with in creating a typical test script and readying it for playback.

1. Create Script. In most cases "what you see is what you record, and that is what you play back." In very rare cases manual editing will be needed to achieve special effects.
2. Confirm Script. Confirm that the script behaves correctly, reports correctly, and does not interfere with other scripts.
3. Create Agent Work Order. The eValid agent work order information includes such details as:
   1. The script name to be run.
   2. When it is to be run in UT.
   3. How many times it is to be repeated, after how long a delay between runs.
   4. Email address for result file(s) [if not specified in the script].
4. Perform The Script. The agent machine is now "busy" doing the work order and it does not look for additional work until it has completed the current order. Launch the simple playback or load-test playback and wait for completion.
5. Transmit Test Results. The scripts themselves are assumed to forward result files during the playback process or at the end of execution.
6. Consolidate Data. The results eValid generates can be collected into an email message or sent by POSTs to a *cgi on the your website.
7. Analyze Results. Merge files, if necessary, and present results to the user.