RichDerr wrote:Hi.
I've been doing some research on the internet and WebDriver seems to be something that a lot of people are excited about.
Where do you eValid folks stand on this?
Thanks in advance.
Thanks for asking about this RchDerr.
The history of WebDriver goes back to 2011, when the W3C committee was formed.
They formed a committee and put together a Working Draft of a standard in mid-2012.
Here is a link:
https://www.w3.org/TR/2012/WD-webdriver-20120710/The back story is that Google, which is HUGH user of automated testing methods, as part of the GTAC series of conferences that began in 2006 began to argue for standardization between/among web testing tools.
Here is the web page for GTAC:
https://events.withgoogle.com/gtac-2017/This gives a pretty good explanation of the history and purposes of GTAC, and those notions formed the basis for the W3C standards effort.
eValid was at V6 in 2006, and at the time about 90% of the final command list was completed.
From what we have seen, all of the WebDriver commands are represented in the eValid command set, but obviously in different forms.
For example, the WebDriver action "find_element" command is performed in eValid with the command "IndexFindElement", both of which find the specific DOM element number that
matches a user-specified search criterion.
We believe it is a good thing that these kinds of basic web testing operations have been standardized -- because it is good for the software testing community and good for increased
quality in software.
-- eValid Support
