SELENIUM: Technology Stack

Before we start this automation framework course, we should know what actually we are going to use for this so that we can have all those ready beforehand.

This is the post, where you can find the technologies used for this whole process.

Further, in this blog, I will be writing the course to create an automation framework so I will be focusing more on webdriver component of selenium and less on other components like selenium ide, RC etc. I can cover these under "Interesting facts" topic later during the course. I will also try to cover some of the other interesting topics in this which cannot be covered in course.

So, let's go through the technologies which I will be using during this course.

I will be using Selenium webdriver as automation tool for building framework, C# as a programing language, MSTest testing framework for writing tests and visual studio as development tool.

So, it is assumed that you have at least basic knowledge of these technologies. In case you know nothing about these, you don't have to bother, Just click on the respective links and get at least basic knowledge or you can also find other links if you find better content there to get a start.

In next post we will learn and see a basic view of selenium and its webdriver architecture.

Thanks for reading this post and see you in next post. Cya!

Next post >>

Comments

"Hello Selenium"

Now, as we have already setup the required environment, let's just start with a hello world test with selenium. In this let's just write a basic test to make sure that our environment is working properly. For this hello selenium test we will be automating below test: Navigate to " https:// www.google.com " Write "Hello selenium" in search box Press search button Below are the code snippets: Test class UnitTest1 containing required test. Here in this class, at the top I have used two statements i.e. using Microsoft.VisualStudio.TestTools.UnitTesting; using TestFramework; First using statement is required in for writing unit tests and second using statement is required so that we can access methods from class under TestFramework namespace. There is [TestClass] attribute used with this class. This is required so that tests written in this class can be recognized. If you miss this attribute then your tests are not going ...

SELENIUM: Using Nested Classes

In this post I will be using nested class pattern to make few things easier. e.g. If you see in our test application there is a navigation bar on left side containing various menus i.e. Posts, Pages etc. Further each main menu contains sub-menu e.g. Posts menu contains sub-menues as "All Posts", "Add New", "Categories" and "Tags". In this type of situations, it is good to use nested classes to make things more readable and easy to use. E.g. Suppose I want to access "All Posts" navigation then I would want this to be done like this. " LeftNavigation.Posts.AllPosts.Select(); " i.e. I would want that there would be a class called "LeftNavigation" and when I press '.' (dot) it shows all the main menues in this navigation e.g. "All Posts", "Pages" etc. then I choose " LeftNavigation.Posts " and again when press '.' it shows all the sub-menues inside this Posts menu...

SELENIUM: Adding Next Test With Proper Test Structure-1

As I mentioned in my previous post that now its time to refactor our tests a little bit so that each test is written with proper test structure as required. After refactoring tests we will add one more test to our framework with proper test structure. So, lets do it now. Refactoring tests Till now we have added two tests to our framework i.e. And Let's refactor these tests first before adding more tests to this framework. In each method let's log some message so that we come to know how the execution was done. # AssemblyInitialize method: In this method let's put code to initialize the log so that it can be used throughout the assembly. Before moving to next method let's talk about other refactoring made in this test project. #1: All static classes are made non-static so that we can created instances of page objects instead of directly using them. So, now on we cannot use class directly. Instead we will...

Dig into Selenium

Search This Blog