timez wrote:We see that eValid is not alone in the "testing space" with
Watir and Selenium and Webdriver all doing something similar
to eValid.
How is eValid different? What are some things that eValid can
do and the others can't?
That's a good question, and a timely one. We're happy to try to provide an answer!
Naturally we are tracking what is going on with Selenium, and with WATIR, and with Google's WebDriver developments.
The main difference is that eValid is a professionally supported product that has been around a lot longer than those other development threads and has had the benefit of having already solved many of the "little issues" that you see some of the development threads struggling with. There are too many of these to list, but suffice it to say, they've been resolved in eValid -- every one.
eValid's architecture delivers some powerful advantages: scalability, accuracy, reliability of playback, AJAX with DOM-based synchronizations, and general ease of use and flexibility, to mention just a few. The fact that eValid is a compiled product, built entirely in C++ on Visual Studio -- whereas the other approaches are based in JavaScript interpretations and various kinds of component lashups -- is the main underlying general advantage.
-The eValid Team
