They saying goes, "Imitation is the kindest form of flattery, and the sincerest indicator of respect." We accept the compliment paid us by the W3C folks.
The new proposed standard for using a browser to drive web applications can be seen here:
WebDriver: W3C Working Draft.
This standard appears to be based on the Google-sponsored WebDriver development, under guidance for many years of Simon Stewart (who left Google to join FaceBook in January 2013), and David Burns (Mozilla).
If you compare the architecture of eValid with that of WebDriver you will see many similarities. The ability to drive a browser for certain results and under varying conditions in both systems is based on manipulation of DOM values (or, at playback time, observation of DOM values).
There are many features in eValid that are not present in WebDriver, things like Adaptive Playback and the ability to obtain detailed web page component timings (eValid's Detailed Timing), to name a couple of them. Internal synchronization and lots of test-statbilization features including a higg degree of scalability (key to doing load testing) are some others. We believe the list is long.
Even so, that WebDriver would copy the basic operation of eValid -- we are guessing from work done starting in 2005 and onward -- is good news for our users: You won't be made obsolete with eValid.
eVald Management