
These terms are not unique to the UDF, so you will find just the general description in this section. You will encounter the following technical terms when working with the WebDriver UDF. How the browser independent and browser dependent parts fit together: That's why I think it has at least the same limitations as ChromeDriver.
WEBDRIVE LOGIN DRIVERS
One of the following Drivers needs to be installed - depending on the Browser type and version you try to automate:įollow this link to select the correct version depending on the Chrome version you run! WinHTTP UDF (AutoIt) by trancexx or autoit-winhttp (GitHub).The following UDFs need to be installed - independent of the Browser you try to automate: Supporting multiple browsers via the same code base is now possible with just a few configuration settings.

The WebDriver UDF allows to interact with any browser that supports the W3C WebDriver specifications. WebDriver can also manage testing across multiple windows, tabs and webpages in a single test session. This is different from JavaScript unit tests because WebDriver has access to functionality and information that JavaScript running in the browser doesn't, and it can more accurately simulate user events or OS-level events. WebDriver enables developers to create automated tests that simulate user interaction.
