How To Explain Test Automation Framework To The Interviewer

Coming to the actual topic “How to explain test automation framework to the interviewer”. Here I will explain to you every component of the architecture based on the below-mentioned screenshot. Frame your answer in your own words while explaining the framework to the interviewer.

We need to specify in and out of our Test Automation Framework such as programming

language used,

Type of framework

used, Test Base Class (Initializing WebDriver, Implicit Waits), How we separate Element locators and tests (Page Objects, Page Factory), Utility functions file, Property files, TestNG annotations, How we parameterize tests using Excel files, How we capture error screenshots, Generating reports(Extent Reports), Emailing reports, Version Control System used and Continues Integration Tool used.

If you liked this video, then please subscribe to our YouTube Channel for more video tutorials.

Language: In our Selenium Project we are using Java language. Even though Selenium supports multiple languages, we are using Java language is just because most of the automation developers have knowledge on Selenium with python training.

POM: As per the Page Object Model, we have maintained a class for every web page. Each web page has a separate class and that class holds the functionality and members of that web page. Separate classes for every individual test.

Packages: We have separate packages for Pages and Tests. All the web page related classes come under Pages package and all the tests related classes come under Tests package.

For example, Home Page and Login Page have a separate classes to store element locators. For the login test there would be a separate class which calls the methods from the Home Page class and Login Page class.

I will explain based on the below-mentioned test automation framework structure.

The above screenshot illustrates a standardized maven project. As per the above maven project, all the tests are kept in the ‘src/test/java‘ and remaining files (such as config.properties, element locators (POM classes), utility files, test data, etc.,) kept under ‘src/main/java‘.

Test Base Class:

Test Base class (TestBase.java) deals with all the common functions used by all the pages. This class is responsible for loading the configurations from properties files, Initializing the WebDriver, Implicit Waits, Extent Reports, and also to create the object of FileInputStream which is responsible for pointing towards the file from which the data should be read.

Utility Class (AKA Functions Class):

Utility class (TestUtil.java) stores and handles the functions (The code which is repetitive in nature such as waits, actions, capturing screenshots, accessing excels, sending an email, etc.,) which can be commonly used across the entire framework. The reason for creating a utility class is to achieve reusability. This class extends the TestBase class to inherit the properties of TestBase in TestUtil.

Properties file:

This file (config.properties) stores the information that remains static throughout the framework such as browser-specific information, application URL, screenshots path, etc.

All the details which change as per the environment and authorization such as URL, Login Credentials are kept in the config.properties file. Keeping these details in a separate file makes easy to maintain.

Screenshots:

Screenshots will be captured and stored in a separate folder and also the screenshots of failed test cases will be added to the extent reports.

Test Data:

All the historical test data will be kept in an excel sheet (controller.xlsx). By using ‘controller.xlsx’, we pass test data and handle data-driven testing. We use Apache POI to handle excel sheets.

TestNG:

Using TestNG for Assertions, Grouping, and Parallel execution.

Here you could find TestNG Complete Tutorial and also you could find TestNG Interview Questions

Maven:

Using Maven for build, execution, and dependency purpose. Integrating the TestNG dependency in the POM.xml file and running this POM.xml file using Jenkins.

Version Control Tool:

We use Git as a repository to store our test scripts.

Jenkins:

By using Jenkins CI (Continuous Integration) Tool, we execute test cases on a daily basis and also for nightly execution based on the schedule. Test Results will be sent to the peers using Jenkins.

Extent Reports:

For the reporting purpose, we are using Extent Reports. It generates beautiful HTML reports. We use the extent reports for maintaining logs and also to include the screenshots of failed test cases in the Extent Report.

Here you could find How To Generate Extent Reports and also find How To Add Screenshots In Extent Reports.

You have to explain all these when you are asked to explain the test automation framework in the interview. If you have any other thoughts on how to explain the test automation framework, comment below in the comments section.