Test Automation Architecture

Nov 19
15:47

2020

jayesh jamindar

jayesh jamindar

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

A test automation architecture is the organization and abstraction of test scripts, test data, and business logic. An efficient test automation architecture is one that has all its layers loosely coupled and scalable. In this article, we'll understand the POM design pattern and its implementation. The page functions and logic are abstracted from test scripts in POM, moreover, it is easy to maintain and scale. It is the application of different tools, methods, and techniques in an efficient way to accomplish varied testing goals.

mediaimage
What is Page Object Model design pattern ?


In POM design pattern,Test Automation Architecture Articles we are treating every page as an object. Every page is an object and these objects are used in the corresponding test class.
For every web page we create a java/class file for e.g. there will be a java file for 'login' page, a separate java file for 'home' page, separate java file for 'about us' page and so on. A typical POM structure can be seen in the below image.

 

1. Declaring page elements in page class


In the page class, we declare the page elements present on that page as seen in the below image

 

2. Defining operations in page class


Also write methods/functions/operations which we want to execute on that page for e.g. java file for login page contains methods/functions related to login functionality like entering username, entering password, clicking submit button, click forgot password link etc. We just define these functions/operations in loginpage class.

The calling of these functions happens in a separate java/class file which is nothing but our test file. So in the page class we define the function, and in the test file we call those functions. In this way we separate out the test execution from the pages. As can be seen in the above image, there is a class called loginPaga.java, and another test class called testLoginpage.java. This testLoginpage.java calls the functions defined in loginPaga.java. Similarly there is homepage.java and its corresponding testHomePage.java and so on.

Another important point to remember in POM is that in a page class if suppose clicking a button is redirecting to another page then we need to return object of that page when we perform this operation. For e.g. if on the home page if clicking 'aboutus' link is redirecting to 'Aboutus' page then we have to return the object of 'Aboutus' page in the method written in homepage for clicking 'aboutus' link. The method written in homepage.java should be like this-

public aboutusPage clickonAboutUs()
{
Webdriver code;
return new aboutus;
}

 

 

This way, the constructor of resulting page gets triggered and page elements and webdriver of subMenuPage gets initialized.

 

MAKING EVERY TEST CASE INDEPENDENT


What does this mean by independent test cases? This means every test case can run independently and there is no dependency on another test case. To achieve this, you need to run preconditions of that particular test case in @BeforeMethod annotation.

3. Structure of a test class


A typical structure of a test class is as seen in the below image. There are preconditions defined under @BeforeMethod annotation. The code under @BeforeMethod annotation will run before the test case execution. This way you can execute preconditions of a test case before the actual execution of the test case. For e.g. you want to validate "My Account" section of Amazon and under my account to want to validate "your orders" etc. But before reaching "My account" section you first need to login to your amazon account.
So "login" to amazon account will be one of the preconditions of your "My Account" section test case.

The below image depicts an example of a product detail page of the Flipkart app where the test case for adding a product to cart is defined under @Test annotation. But before adding a product to the cart, the product must be first selected from the home page's main category and then final selection from sub menu page's.
So category selection from homepage and then product selection from sub menu page are two preconditions before adding a product to the cart.
So whenever we run testAddToCart test case, the preconditions will execute before the test case. These preconditions are nothing but previous or predecessor test cases that might have already executed in their respective test classes.

 

4. Execution flow of page object model


When we execute our testng.xml file where our test classes are mapped. The testng.xml triggers the respective test class defined in it. This test class creates an object of its respective page class and call methods or operations defined under the page class. Once the object of a page class is created, its constructor gets called and all the web components and web driver belonging to that page get initialized. Whenever such an operation is called from the test class which results in navigation to another page, another page's constructor gets called and web components and web driver belonging to the resulting page gets initialized. In this way a typical page object model design pattern works.

Also From This Author

Navigating the Path to a Career in Software Testing

Navigating the Path to a Career in Software Testing

Software testing is a vital component of the software development lifecycle, ensuring that applications meet quality standards and function as intended. Contrary to past perceptions of software testing as a mundane and less creative field, it has evolved into a dynamic career path, rich with opportunities for innovation and growth. With the advent of automation, software testing now requires a similar level of programming expertise as software development. A career in software testing offers a diverse range of specializations, including API, security, database, and load testing. As the gatekeepers of product quality, software testers play a crucial role in preventing costly errors, maintaining user satisfaction, and ensuring the success of a product in a highly competitive market. A well-rounded tester, akin to a full-stack developer, is highly sought after for their ability to handle both functional and non-functional testing aspects. Certifications, such as those offered by the International Software Testing Qualifications Board (ISTQB), can provide a competitive edge for those starting in the field.
Mastering Performance Testing with JMeter

Mastering Performance Testing with JMeter

Discover the essentials of performance testing with JMeter, an open-source Java tool from Apache Software Foundation. JMeter is designed to analyze and measure the performance of various applications by simulating loads on servers. It supports testing for web applications using HTTP/HTTPS, web services via SOAP and REST, databases through JDBC, and more. With its user-friendly GUI, JMeter allows testers to easily add and configure components such as Samplers, Config elements, Listeners, Controllers, and Assertions.
Elevate Your Testing Game with TestNG

Elevate Your Testing Game with TestNG

TestNG is a powerful unit testing framework that surpasses JUnit with its advanced features. When paired with Selenium, TestNG transforms the way you organize and manage your tests, offering a suite of annotations for grouping, sequencing, and parameterizing test cases. It also provides listener interfaces for event-based operations and supports parallel execution through XML configurations. This article delves into the capabilities of TestNG, providing insights into how it can streamline your testing process and enhance efficiency.