Selenium WebDriver and Automation Framework Introduction

-
Selenium WebDriver API helps us to automate browser-based applications

So why one should go for selenium web driver to automate their web application testing?

  1. Selenium is Free
  2. Support multiple languages like C#, java etc
  3. Huge community
  4. easy to use


Well that's just good part, can you tell me limitations if any

  1. Only works for browser
  2. Element identification can be a pain for some applications
  3. Sometimes some things will not work the way it is and you need to hack a bit (This is very rare and completely depends on web application one is testing)

To know more about selenium web driver refer to the official documentation

Automation Framework

 When we start automating the web application and start adding more and more scripts, we start to realize that we are repeating a lot of stuff and not reusing code, as our motive is to just automate the script.

Sooner we fell that all the heavy lifting code which we have in our test cases should be moved to some common component and wait there are many more things which come to our mind

What about the maintainance of tests?
How can I reuse the code?
How easily can a new team member add tests?

A good automation framework in place can take care of the above points

So whats an automation framework?
Automation framework is a program that helps to manage your testing activities

As discussed earlier, all the heavy lifting logic goes into the framework and tests are so simple that anyone can understand and contribute to the project.

In this part of the learning path, we are going to apply whatever we have learned so far and we will build an automation framework from scratch

Below is the simple architecture of automation framework




Here each layer interacts with the layer below it, that's is in our tests we are not going to refer selenium commands directly.
Tests will talk to the framework which in turns talks with a tool that is selenium in our case.

This way tests will look simpler and easy to extend.

In the next lecture, we will spend some time understanding some selenium commands and then we will start with framework development


Comments

Post a Comment

Popular posts from this blog

Specflow -Part3(Working with tables using Specflow.Assist.Dynamic)

-
In the previous lecture, we learned how can we work with tables to handle test data from the feature file.I will paste the feature and step definitions from earlier lecture and then we will talk about the shortcomings and how Specflow.Assist.Dynamic can help us to overcome them Feature File Feature : SpecFlowFeature2 In order to show specflow capabilities for working on tables We are going to write some scenarios here Scenario : Verify specflow can read data from table and print on console Given  I have dummy student data as below   |  StudentId  |  StudentName  |  Division     |  Age  | |  100        |  James        |  Engineering  |  30   | ...
Read more

Specflow -Part4(Specflow Scenario Outline and Feature Background )

-
In the previous lecture, we talked about how we can pass multiple data to step using tables, suppose we want to run the same scenario for a different set of data, For example, you want to test the login functionality of an application, where you test login with Administrator, Project Manager, Product Owner etc Here the steps of scenario will remain the same only the login credentials will change according to the user. We can have the same scenario run multiple times for each user you want to test with the help of scenario outline, check below Feature file Feature : SpecFlowFeature3 In order to test the login functionality for multiple users, we will demo using scneario outline Scenario Outline : Verify login for different set of users Given  User trys to login into application using  <Username>  and  ...
Read more

Specflow -Part6(Specflow Hooks)

-
Image
We may come across a scenario where we need to execute code after/before a particular event like given below We want to create some folder where we can store screenshots/ logfile before starting the test We may want to log details of the scenario in a log file after executing each step  We want to know after each step if that step was successful and if not we want to take a screenshot as an evidence We want to clean up the database before/after each scenario/feature  We  may want to open/close browser for every scenario Hooks help us to execute logic when a certain event occurs, let's check how I will start with creating a new project called SeleniumHooks and added folders where we can keep our feature, feature definitions and hooks file We will add a feature file and implement the steps Feature : SpecFlowFeature1 In order to avoid silly mistakes As a math idiot I want to be told th...
Read more