A quick question, tell me how eValid compares with WebDriver?
Very good question AGibbs.
eValid development began long before the WebDriver standard setting effort was begun, and was effectively the first system that created an "application programmatic interface" (an "API") for a browser.
That is, the eValid script language is effectively a complete API for the browser,just as the the WebDriver specification is.
The difference is that in the case of eValid the interface is articulated as a script language according to these principles: http://e-valid.com/Products/Documentati ... iples.html
WebDriver is more abstract in the sense that the is no specific scripting language -- the "binding" of the standard is left up to the user.
It is worth pointing out that eValid does has a C/C++ binding available in the EPI Interface, described here: http://e-valid.com/Promotion/EPI/general.html
The possibility of having a binding of eValid into another language than C/C++ is certainly available, depending on need and budget.
-- eValid Support