SELENIUM: Some Useful Facts

Before we start designing a framework, there are few facts that we should always remember. It is not important what you have designed, it is more important that how good your product is.

Also, this kind of analysis should always be done in the beginning so that you don't have to devote extra time and efforts for it later. It is always good to fix something in beginning than worrying about it later when it has become a big issue and become difficult to locate the issue. It's not like that we won't be able to fix it, we will definitely fix it but with more cost and efforts.

Let's go through few of these facts.

Layers in Framework

You should always keep in mind the layers that should be there in the framework you are designing. Layers to be created generally varies application to application that you are creating but most of the frameworks contains below layers often.

In above picture, there is workflow layer at the top. Workflows can be think of as something which is bigger than pages and can utilize multiple pages when executed. E.g. if we think about invoicing system then "Send invoice to erp system" might be considered as a workflow as in order to perform this action one has to first create an invoice, approve and then send it.

Then there is a page layer below workflow. Workflows are going to be dependent on pages. I won't be explaining here about pages as we already have discussed about this in my previous post "Page Object Model".

Below pages layer there is a layer for common things like navigation or others which is common to all pages. Hence, multiple pages can share a navigation and in this way you don't have to define same methods multiple times at multiple places. So, it is a good practice to have common things separately. We will be going through this in more details in my later posts when we actually define these kind of things.

Below that there is selenium where our framework is going to interact with.

Easy to Use

Framework that we are creating should always be designed in such a way that it is easy to use. It's been seen that lots of products just goes into trash in-spite of having good content just due to the fact that it was not easy to use. Hence you end up waste your precious time building a framework which won't be used at all. So, keep it in mind always.

"If tests are not easy to run, they won't be run at all"

In my next post we will add our first test with correponding code to our framework.

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

Next post >>

<< Previous post

Comments

Logging in Selenium

Any application is incomplete until it's activities are traceable. Here comes the use of logging. By logging important actions you can later on track anything you want especially when there are some error situations. It becomes easy to debug the issues if logs are generated properly. Similarly, it is very important that our automation framework generates logs so that whenever any test fails, we can track the issue by tracing it's logs. In this post, I will be explaining you how we can log using log4net in selenium. Before using methods of this library we need to configure this to our application. Let's do this first then. Configuring log4net in selenium: First of all you need to download this library so that this can be used. You can read about log4net and then download it from this link and save the dll file after extracting it to folder that is under your project folder. After downloading this library you need to add references of this in you project. To do ...

"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 ...

About Selenium

Let's start with a basic information about Selenium . Selenium: It is basically a tool or framework that is used to automate web browsers. By using selenium you can automate a lots of web browsers like Firefox, IE, Chrome etc. It is possibly most widely used open source solution. Sel enium is basically a set of different tools with different purpose and role . E.g. Selenium IDE Selenium 1 (Selenium RC) Selenium 2 ( Selenium Webdriver) Selenium-Grid Sel enium webdriver is the one which we will be using during this course. It supports fol lowing bro wsers: Google Chrome Internet Explorer Firefox Safari Opera HtmlUnit phantomjs Android iOS So, it is the one that allows you to automate these web browsers. If we talk little bit technically, then it is basically an API for web browsers. Using this you can program web browsers in a way that you want them to do. If you want to learn more about selenium then you can go through this link . Archite...

Dig into Selenium

Search This Blog