_csharp

Example

Before starting, we'll need to download the latest ChromeDriver binary executable from here. Once we have it we'll need to tell Selenium where it is. Two ways we can do this are to:

• Add it to the System PATH
• Specify it in the Selenium setup

Let's start by including our requisite classes for our test framework (e.g., using NUnit.Framework), driving the browser with Selenium (e.g., using OpenQA.Selenium, etc.), accessing C# methods to work with the local file system (e.g., using System.IO), and start our class with some setup and teardown methods.

// filename: Chrome.cs
using NUnit.Framework;
using OpenQA.Selenium;
using OpenQA.Selenium.Chrome;
using System.IO;

public class Chrome
{
    IWebDriver Driver;
    string VendorDirectory = Directory.GetParent(
        Path.GetDirectoryName(typeof(Chrome).Assembly.Location)).
            Parent.FullName + @"\Vendor";

    [SetUp]
    public void SetUp()
    {
        Driver = new ChromeDriver(VendorDirectory);
    }

    [TearDown]
    public void TearDown()
    {
        Driver.Quit();
    }
// ...

Notice the field variable declaration for VendorDirectory. With it, we are effectively grabbing the full path of the project directory and appending the Vendor directory to it. This is then put to use when creating an instance of Chrome (e.g., Driver = new ChromeDriver(VendorDirectory);).

Now we're ready to add a test.

// filename: Chrome.cs
// ...
    [Test]
    public void PageLoads()
    {
        Driver.Navigate().GoToUrl("http://the-internet.herokuapp.com");
        Assert.That(Driver.Title.Equals("The Internet"));
    }
}

If we save this file and run the project (e.g., nunit3-console.exe .\Chrome.sln) it will launch an instance of Chrome, visit the homepage of the-internet, and assert that the page title loaded.

Expected Behavior

When you save this file and run the project (e.g., nunit3-console.exe .\Chrome.sln from the command-line) here is what will happen.

• ChromeDriver starts
• Chrome opens
• Test runs
• Chrome closes
• ChromeDriver stops

Summary

Hopefully this tip has helped you get a better handle on how WebDriver works with various browsers and saved you some time in your configuration setup. But keep in mind that no two browser drivers are alike, so be sure to check out the documentation for the browser you care about to find out it's specific requirements. For more about specific driver requirements, visit the official Selenium Quick Reference page for Installing Browser Drivers.

Happy Testing!