SELENIUM: Architecture of Automation Solution

Till now we have learnt about many things related to building a good automation framework. We added few tests too to our framework to see how it works. We also learnt few important things to remember for a good and robust framework.

But before we progress ahead with some other stuff, lets just see which type of architecture we are using for our automation solution. It is very important to know this so as to make sure that we are building the framework robust and non-brutal and know about what and how things should work.

Keeping this in mind, I think this is right time to know about this.So, below is diagram showing the basic architecture that we are using in this course.

If you see this diagram then you can understand that in our architecture our tests will be utilizing the framework that we are creating, our framework in turn will be utilizing the selenium and in the end selenium will be the only thing that will be directly interacting with the browser. Hence, it is be noted from this architecture that our tests never interacts directly with browser and they do not directly interact with selenium.

Whatever we do in tests basically comes from the functionality that we implement in our framework. This is very important to make sure that our tests are durable and not brutle. This is because whenever there is any change in our application, selenium is not going to be changed, it will remain same but our framework is going to changed in order to implement the changed functionality and finally the tests will remain the same as mostly these will be relying on the framework.

Hence we are creating different abstraction levels here and we make it work in a way that anything at higher level communicates with one level below it only. Hence tests only talks to framework, framework only talks to selenium and selenium only talks to browser.

This is the most important thing as many automation solution in which this type of abstraction is missing, fails or becomes so complex or time consuming process whenever there comes any changes in application.

Thanks for reading this post. See you in next post. Cya.

<< Previous 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