In my most popular post ‘C# and the disappearing PageFactory – My next steps in Selenium testing’ I gave Jim Evans suggested approach of using properties to return the response from your page controllers. I have never used this approach however, and before start discussing how I do build them, I thought I should explain why.
Looking at how I best learn new technologies and putting this into practice learning about C# Lazy
Last time I showed how to launch a WebDriver instance from .NET core so that we can test on any platform. When creating a framework however I like to have a factory to handle the driver creation and setup for me. I don’t wan’t to have to mess around setting things up in my Test class every time. My .NET core WebDriverFactory design criteria: It should have really simple syntax, especially for creating a ‘default’ webdriver. It should handle local…
As discussed last time, the goal is to be able to run my tests on any .net Core platform. So right from the get go, lets work out how to get a WebDriver fired up. As ever I develop on Windows and I still have Ubuntu 18.4 installed on the Windows Subsystem for Linux (WSL) with an Xming Xserver so in theory I can also test in Linux. Unfortunately, whatever happened to my network whilst I was on holiday finally…