If I was not limited with the budget for the development, I’d better use paid tools, because the development is always easier with paid software. Unfortunately, I didn’t have any budget and therefore I had to use the only free software. The positive side is that customers always love to save money and always encourage you to utilize tools free of charge.
Here is the list of tools necessary for the development:
For the purpose, it is sufficient to have a free version of VS. But I found out, it must be only Visual Studio 2013 for Desktop, since I’m about to do a little trick to be able to debug tests with NUnit tool, and this will need to create a console application. Last, the VS 2013 for Desktop have been seen here:
Selenium Webdriver library, IEDriverServer (for testing with IE browser). Both are located here. For testing with Chrome browser, I downloaded ChromeDriver –
Install Visual Studio. Install NUnit. Default settings are sufficient. Unpack selenium-dotnet-version_number archive. Inside the archive, you can find two folders: [net35] and [net40]. They are different versions of Selenium Webdriver libraries written respectively utilizing.Net 3.5 and Net 4.0. Choose the library for use in your future framework and put it in a separate place. Also, you can find the WebDriver.chm file in the archive. This is short (but very useful) manual on Selenium WebDriver tool. I strongly recommend exploring it.
Download appropriate version of IEServerWebdriver or ChromeDriver if necessary. Unpack it. You will find the only file that is executable in both archives. This is a program that will launch your Internet Explorer (or Chrome) browser and will translate commands between Selenium WebDriver tool and IE/Chrome browser.