Writing the Framework

It is in this part of the series that  you will start actually writing code.  If you are somewhat new to coding in C# and using Selenium, I recommend writing out all the code snippets from scratch rather than copying and pasting them, for some of the following reasons;

• As you start writing code, you will start picking up on patterns in the code, which will help you pick up things quicker
• As you write out the code and try to reference certain libraries, if you are using ReSharper then Visual Studio IDE will autosuggest libraries to reference and use as you type out your code 😀

Utils.Selenium namespace

Editing the ‘Driver.cs’ class file

1. Open up the ‘Driver.cs’ class file in the ‘Utils.Selenium’ folder and edit the class file to match like below, which creates a public WebDriver instance that returns DriverController when initiated, which can then have its functionality used in test methods (e.g. maximising the browser() window or implicit/explicit waits etc)…

   using System;
   using System.Diagnostics;
   using System.IO;
   using OpenQA.Selenium;
   using OpenQA.Selenium.Chrome;
   using OpenQA.Selenium.Firefox;
   
   namespace ProductAutomation.Utils.Selenium
   {
       public static class Driver
       {
           [ThreadStatic]
           public static IWebDriver CurrentDriver;
   
           public static void InitChrome()
           {
               CurrentDriver = new ChromeDriver(Path.GetFullPath(@"../../../../" + "_drivers"));
           }
   
           public static void InitFirefox()
           {      
               CurrentDriver = new FirefoxDriver(Path.GetFullPath(@"../../../../" + "_drivers"));
           }
       }
   }

Editing the ‘Settings.cs’ class file

1. Open up the ‘Settings.cs’ class file in the ‘Utils.Selenium’ namespace and edit the class file to match like below.  We will be using the Settings file to store public static variables that we will want to be using in our project.  For the purposes of this course, I will be explaining how to automate a simple Google search, therefore I will set my baseUrl to google.com…

   namespace ProductAutomation.Utils.Selenium 
   { 
       public class Settings 
       { 
           public static string baseUrl = "https://start.duckduckgo.com"; 
       } 
   }

Utils.Hooks namespace

Editing the ‘SpecFlowHooks.cs’ class file

1. Open up the ‘SpecFlowHooks.cs’ class file in the ‘Utils.Hooks’ namespace and edit the class file to match like below, which contains all our SpecFlow hooks for things we want to happen before and/or after an individual SpecFlow scenario is run, dependant of the tags we use above a scenario (e.g. “Chrome”, “Firefox” or “Debug”)…

   using System.Linq;
   using ProductAutomation.Utils.Selenium;
   using TechTalk.SpecFlow;
   
   namespace ProductAutomation.Utils.Hooks
   {
       [Binding]
       internal static class SpecFlowHooks
       {
           [Before]
           [Scope(Tag = "Chrome")]
           internal static void StartChromeDriver()
           {
               Driver.InitChrome();
           }
   
           [Before]
           [Scope(Tag = "Firefox")]
           internal static void StartFirefoxDriver()
           {
               Driver.InitFirefox();
           }
   
           [After]
           internal static void StopWebDriver()
           {
               Driver.CurrentDriver.Quit();
           }
       }
   }

   The above stops the WebDriver after the scenario has finished running if the tag associated with it is “Chrome” or “Firefox”, but if it is “Debug” then it does not stop the WebDriver, so that the point of failure can be viewed and debugged accordingly

Editing the ‘TestRunHooks.cs’ class file

1. Open up the ‘TestRunHooks.cs’ class file and edit the file to match like below, which again prevents the WebDriver from stopping when the tag “Debug” is used…

   using ProductAutomation.Utils.Selenium;
   using TechTalk.SpecFlow;
   
   namespace ProductAutomation.Utils.Hooks
   {
       internal static class TestRunHooks
       {
           [AfterTestRun]
           internal static void AfterTestRun()
           {
               Driver.CurrentDriver.Quit();
           }
       }
   }

Pages namespace

Editing the ‘BasePage.cs’ class file

1. Open up the ‘BasePage.cs’ class file in the ‘Pages’ namespace and edit the class file to match like below.  The ‘BasePage’ class is where we will later put all our test methods for our BaseScenarios, as well as any methods that exist and/or can be shared across more than one specific page class (e.g. main navigation, validate a given pageUrl etc)…

   using OpenQA.Selenium;
   using ProductAutomation.Utils.Selenium;
   
   namespace ProductAutomation.Pages
   {
       public class BasePage
       {
           public IWebDriver driver = Driver.CurrentDriver;
       }
   }

Steps namespace (Step Definitions)

Editing the ‘BaseSteps.cs’ class file

1. Open up the ‘BaseSteps.cs’ class file in the ‘Steps’ namespace and edit it to match like below…

   using TechTalk.SpecFlow;
   
   namespace ProductAutomation.Steps.BaseSteps
   {
       [Binding]
       public class BaseSteps
       {
           
       }
   }

2. Do similar for the other Step Definition class files

The core framework is now setup! In the next part, we will see how to create our Base Scenarios.

Copyright secured by Digiprove © 2018

Liked it? Take a second to support Thomas on Patreon!