Website UI Testing

DZone 's Guide to

Website UI Testing

Take a look at this method for creating short, quick unit tests that still accomplish their goal, for the purpose of testing your website's UI.

· DevOps Zone ·
Free Resource

Last week, I looked at testing the UI of mobile apps, this week lets look at how we could do a similar thing for websites.

Testing the user interface is not an excuse for a lack of unit tests. Testing the user interface takes longer, so for keep creating your small unit tests that can be run after every build. That said, lets look at how you create a UI test.

Create a Unit Test project as normal. Now install the following nuget packages:


I am going to be using Selenium to achieve my website testing, and I am going to concentrate on the Chrome browser. However, packages exist for other browsers, so have a look at the following, and I expect there are others as well.


Selenium started life as a plugin for Firefox to help create automated tests, however, the latest version of Firefox is not compatible with the plugin as I write this. I have not had to install any plugins or extensions to my browsers to achieve my testing.

Enough talk - lets write a test. First, we create two instance variables to store the baseURL and the driver for the browser you are using.

private string baseURL = "https://www.example.com/";
private RemoteWebDriver driver;

Next, we need to set things up for the test to run. This creates an instance of the Chrome driver, maximizes the window, and sets it to wait 30 seconds before timing out.

public void MyTestInitialize()
    driver = new ChromeDriver();

Now comes the actual test. We navigate to a URL and then compare the title of the page loaded with a known value with an Assert statement like you would find in a unit test.

public void CheckBrowserTitle()
    Assert.AreEqual("Home Page", driver.Title);

Finally, we need to tidy up after ourselves.

public void MyTestCleanup()

If you are used to writing tests you will know that the are usually constructed in three sections Arrange, Act and Assert. The Arrange is done in the initialize method, which makes the actual test much simpler, the first line does the Act and the last line does the Assert.

Now we have written a simple test lets look at something more complex.


This finds any Link on the page which is click. Be careful as the string need to be exactly what appears on screen it may well be easier to specify by id or class or something that doesn't change as often. By adding .click() on the end of this command Selenium will click on the link and you can navigate to a new page.

What about submitting form data? Well you can find the element you want to fill in and add .SendKeys("example text") or .Submit() and this will fill in and submit form data.

What about a screenshot?
Screenshot ss = driver.GetScreenshot();

I have only just started playing around with web UI tests but you can see there is a fair bit you can do.

devops, software testing, tutorial, ui testing

Published at DZone with permission of Simon Foster , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}