NuGet package restoring ready, and no need to commit any WebDriver binary files into source code control repository. These NuGet packages will download Selenium WebDrivers (Chrome, Firefox, Internet Explorer, and PhantomJS) into your Unit Test Project.Įach WebDriver binary file does not appear in Solution Explorer, but it is copied to bin folder from package folder when the build process. To perform this check, TestingBot has created a custom tb:fileExists command which can be used with the JavascriptExecutor provided by Selenium WebDriver.NuGet packages for WebDriver - Chrome, Firefox, Internet Explorer, PhantomJS This is a repurposed repo of nupkg-selenium-webdriver-chromedriver by jsakamoto that handles downloading Chrome, Firefox, Internet Explorer WebDrivers, and PhantomJS instead Once you've downloaded a file during your test automation, you might want to check if it was downloaded correctly (does it exist on the disk?). Using System using OpenQA.Selenium using using using System.IO using System.Threading namespace SeleniumTest Verify that the file was downloaded successfully In the example below, we'll first show you how to instruct the remote TestingBot browser to download a file on the TestingBot virtual machine. If you do not specify a specific filename, TestingBot will automatically select the most recent downloaded file.ĭownload files on remote desktop instances during your testĪs part of your test automation flow, you might want to test download functionality of your webapp.

Retrieve the contents of the downloaded fileĪll functions below can be used with a fileName argument, or without an argument.

Retrieve (meta) properties from the downloaded file.

Verify that the file was downloaded successfully.

Download files on remote desktop instances during your test.

TestingBot provides custom Selenium WebDriver commands to verify if a file was downloaded during a test automation session.

Selenium chrome webdriver download