Automation Framework Interview Questions and Answers

A framework is a set of structure of the entire automation suit. It is also a guideline, if followed can result in a structure which is easy to maintain and enhance. These guidelines include:

• Coding standards
• Handling the test data
• Maintaining and handling the elements (object repository in QTP)
• Handling of environment files and properties file
• Reporting of data
• Handling logs

A set of guidelines, assumptions and process developed by experts in order to perform a task(s) in an effective, efficient and optimized way.

In a test automation project, we do perform different tasks by using different types of files. To organize and manage all the files and to finish all the tasks in a systematic approach we use a framework.

There are different types of test automation frameworks and the most common ones are:

• Modular testing framework
• Data driven testing framework
• Library Architecture Testing Framework
• Keyword driven testing framework
• Hybrid testing framework
• Behavior driven development framework

The characteristics are:

• Modular: The framework should be adaptable to change. Testers should be able to modify the scripts as per the environment or login information change
• Reusable: The commonly used methods or utilities should be written in a common file which is accessible to all the scripts.
• Consistent: The suite should be written in a consistent format by following all the accepted coding practices.
• Independent: The scripts should be written in such a way that they are independent of each other. In case one test fails, it should not holdback remaining test cases (unless it is a login page)
• Logger: It is good to have implemented the logging feature in the framework. This would help in case our scripts run for longer hours (say nightly mode), if the script fails at any point of time, having the log file will help us to detect the location and the type of error.
• Reporting: It is good to have reporting feature automatically embedded into the framework. Once the scripting is done, we can have the results and reports sent via an email.
• Integration: Automation framework should be such that it is easy to integrate it with other application like continuous integration or triggering the automated script as soon as the build is deployed.

• Saves time and money. Automation testing is faster in execution
• Reusability of code. Create one time and execute multiple times with less or no maintenance
• Easy reporting. It generates automatic reports after test execution
• Easy for compatibility testing. It enables parallel execution in combination of different OS and browser environments
• Low cost maintenance. It is cheaper compared to manual testing in a long run
• Automated testing is more reliable
• Automated testing is more powerful and versatile
• It is mostly used for regression testing. Supports execution of repeated test cases
• Minimal manual intervention. Test scripts can be run unattended
• Maximum coverage. It helps to increase the test coverage

Using pom.xml file we can execute test suites in maven. We can maintain jar files well structured.

Pros:

• Easy to create and takes less time
• Scripting knowledge is optional
• Recommended for small scale projects
• Recommended for dynamically changing requirements

Cons:

• No centralized maintenance of test objects
• Low in performance due to duplicate objects
• Less or no concentration on complex functionality testing
• Less or no concentration on data driven testing
• No centralized maintenance of resources

Pros:

• Centralized maintenance of resources
• High in performance
• Modifications are easy
• Concentration on complex functionality testing

Cons:

• Scripting knowledge is mandatory
• Less or no concentration on data driven testing
• Takes more time to create

Pros:

• Positive and negative testing can be performed
• Checking the reliability of system (AUT)

Cons:

• Maintaining resources is difficult?
• Less or no concentration on complex functionality testing

Pros:

• Scope is very high as we mix different approaches.
• Flexible for performing all types of tasks.

Cons:

• Organizing and managing resources are difficult
• Complex architecture.
• Low in performance.

Automation testing is the process of testing the software using an automation tool to find the defects. In this process, executing the test scripts and generating the results are performed automatically by automation tools. Some most popular tools to do automation testing are HP QTP/UFT, Selenium Web Driver, etc.

Before picking up the test cases to automate, I do check whether the application is stable or not. So based on this, I don’t pickup test cases when the AUT changes frequently and the test cases which I run rarely and run only one time. When I do usability and exploratory testing.

An Application Map Provides Named References for GUI Components. Application Maps are nothing but Object Repository.

Tasks to be performed:

Analyzing the application in terms of Object Identification:

We have to analyze the AUT in terms of Object Identification.

Basically, QTP is an Object based test tool, here first we have to confirm

If the QTP is recognizing all the objects in our application or not.

To do this, we can follow one or more below given methods.

Record and playback some End to End Scenarios.

1. Using Object Spy
2. Using Object Repository Manager

 We can segregate Software Objects in 3 categories…

1. Static Objects(Properties information is constant)
2. Dynamic Objects(Properties info changes dynamically)
3. Duplicate Objects (Having Similar property info.)

Note: We can handle dynamic Objects using Regular expressions and handle duplicate

Objects using “Index” property.

• Selecting Areas/Test Cases for Automation

Overview: 100% test automation is not possible; we can go for maximum automation.

Generally we select below type of Tests for Automation:

1. Tests that we have to execute on every build (Ex: Sanity Tests)
2.  Tests that we have to execute on every modified build (Ex: Regression Tests
3. Tests that we have to execute with multiple sets of test data.(Ex: Data Driven Tests
4. Tests having complex functionality
5. Planning (Effort estimation, Schedule, Work allocation and Automation Framework implementation)

Overview: After selecting some areas for Automation, we have to estimate the efforts      in terms of Scope of the Project, time and resources(Environmental and Human)To estimate efforts, we can follow an one of the below given methods:

1. Using Expert based techniques.
2. Experienced based techniques.

    Function point analysis.

1. Identifying End to End Scenarios.
2. Identifying verification points.
3. Identifying General and Alternate Flows.

   Identifying the modularity.

 Identifying the complex functionality.

• Creating Generic and project specific functions.
• Creating required Automation resources (Functions, Object repository Files, Environment variable files—etc)
• Creating Tests (Using Object Repository or Descriptive Programming)
• Enhancing Tests (Inserting Checkpoints, Output Values, Transaction points, Flow Control Statements, Synchronization, Parameterization.etc)
• Debugging and running tests (Individual test execution, Test Batch execution.etc)
• Defining and exporting test results
• Analyzing results
• Defect Reporting using Our Company defect management system.
• Modifying resources and tests (if required)
• Performing Re and regression testing
• Maintaining Automation Resources

Using testng.xml we can create suite files, groups, methods and also listeners. We can mark tests for parallel execution. We can trigger testng.xml file from the command prompt or through Jenkins.