eValid™ -- The WebSite Quality Authority Browser-Based Client-Side WebSite Mapping & Analysis, Functional Testing and Validation, Server Loading, Page Timing/Tuning, and Quality Monitoring. © Copyright 2000-2011 by Software Research, Inc.

Introduction
The question is often asked: How do you really evaluate eValid There are two levels for this: Technology and Utility.

• Technology Level: How eValid is Put Together
  1. eValid Represents A Paradigm Shift

     It is a "different kind of thinking" to put the web test functionality into a browser.

     Difficult as it turns out to be to do, many advantages accrue JUST from the fact that, as a browser, eValid doesn't have to worry about a lot of things that are a heavy weight for other architectures to carry.

  2. Occam's Razor Applies to eValid

     "All other things being equal, the simplest solution is the best."

     It's true in eValid's case: What is simplest appearing really IS the best!

     The eValid architecture eliminates 99% of the complexity surrounding doing web application testing by hiding it inside the browser.

     eValid delegates most of the hard work to the browser, which does the work accurately and efficiently. eValid mainly keeps track of what was done and the results produced.

  3. Moving Up A Level Simplifies Life

     The older technologies rely on HTTP/S protocol capture or on desktop interaction. eValid jumps UP one level, where the questions are simpler: go to this page, go to that page, click here, click there.

     It's the moving up one level of abstraction that does the trick.

     It turns out that moving up that one level eliminates (hides) all of the complexity from the lower level, and lets eValid focus on the real actions needed, not be overwhelmed with the details.

  4. eValid Is a Killer App

     The technology change eValid represents makes it a "killer app" for QTP, FT, MS/Test, LoadRunner, VSTS, e-Tester, etc.

• Utility Level: How eValid Behaves In Practical Use

  1. Script Simplicity

     What is very simple for eValid, for other test engine architectures is very complex.

     A 10-line eValid script, recorded in a few minutes, may be the equal of a 500-line hand-coded script that takes many hours or even several days to develop.

  2. Recording Speed

     99% of scripts can be recorded from the eValid GUI, right out of the box.

     That translates to a big productivity gain, reducing the cost of creating tests.

     (Scripts can be still be edited and customized if that's a requirement.)

  3. Universal Solution

     eValid can test Web 2.0, AJAX, dynamic pages, and the full gamut of modern web pages that have many kinds of problematic, hard-to-test behaviors.

     Being an actual browser, issues of synchronization, dynamic content, JavaScript execution, and AJAX operation are absorbed inside the eValid solution.