Test Configuration with .NET Core and NUnit 3
Exploring how to set Nunit test configuration from .runsettings files and the local file system in >NET core test projects
Exploring how to set Nunit test configuration from .runsettings files and the local file system in >NET core test projects
After last time I can feel that I am getting close to being able to inject a configuration for my tests. Next I want to be able to use a configuration file to set the particular configuration that I want to use for any particular test run. So how do we go about doing that in .NET Core? The next steps are: Refactor calls with many arguments to take a standard WebDriver configuration object. Allow different ways to collect and…
Having got to version 2.0.0 of my WebDriverFactory with working system tests and CI builds it was time to extend things a little. This could be considered YAGNI (You Aren’t Gonna Need It) but I quite like to have a Manager class that deals with getting and closing down WebDriver instances. The idea is that the Manager knows the specifics of the driver that I want to use, and will return a given instance, or a new instance on request….
Since my last post I have managed to take my prototype Webdriver factory for .NET Core projects and package it up on nuget.org. This was not as simple a process as I expected, and has required a lot of additional thought and testing. I learnt a number of things along the way that I would want to be aware of if starting again: I try to fill my blog with posts about things I wish I had known, so this…
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…