Framework Overview

Automation testing requires a well-defined approach, based on a comprehensive framework, in order to reap maximum benefits.

A framework is a hierarchical directory that encapsulates shared resources, such as a dynamic shared library functions,Object Repository,Global Variable and reference documentation in a single source folder.

There are various frameworks available for automation, such as:

• Test Script Modularity Framework

• Test Library Architecture Framework

• Data-Driven Automation Framework

• Hybrid Automation Framework

• Keyword-Driven Automation Framework

Hybrid test design and test automation Framework is the most commonly implemented framework is a combination of all of the above techniques, pulling from their strengths and trying to mitigate their weaknesses.

Key Features

In addition to standard features such as performing operations and verifications on the objects, the framework includes other sophisticated features, such as:

1. 
   
   Use of variables:
   
   
   Variables can be defined and used across the generated test script. This can be used to capture run-time values, which can be reused as input elsewhere during test execution.
2. 
   
   Conditional checking:
   
   
   Conditional constructs such as ‘if’ can be implemented using keywords to handle different
3. 
   
   Data-driven testing:
   
   
   This framework supports data-driven testing by importing data from an external resources.
4. 
   
   Re-usability:
   
   
   The Open Source Test Automation Framework is an application independent framework that deals with all possible actions and verifications that can be performed on an object. Therefore, the code for the same object can be used across different applications. Duplication of work is minimized at every level.
5. 
   
   Increased quality:
   
   
   The scripts will be of uniform quality since they make use of the same code
6. 
   
   Greater productivity:
   
   
   The Open Source Test Automation Framework provides both qualitative and quantitative benefits for automation and it is highly productive compared to any other framework. This framework also addresses the ongoing maintenance of the test scripts in a cost-effective manner
7. 
   
   Maintenance:
   
   
   Simple modifications to the application can be easily handled in the code. The changes will be done only in the source file containing the code and the scripts need not be changed. Hence it is easy to maintain the scripts and provide cost-effective solutions for the test automation.
8. 
   
   Return on investment is high:
   
   
   Although the initial effort for building the framework is high, in the long run, the return on investment will be high because of the re-usability and optimum utilization of the tool.

Results & Reporting

Actually Selenium RC does not have its own mechanism for reporting results. Rather, it allows you to build your reporting customized to your needs using features of your chosen programming language.

In Our Framework ,We generate two report they are

• TestNG Report In HTML Format
• Results In Excel File
  We have different log files like:
• client side log
• browser side log
• Results Eclipse console

Generic Test Reports in Java :

• JUnit Report
• TestNG Report
• ReportNG Report

As our Framework built on java integrated with TestNG and Selenium Test cases are developed using TestNG Annotations then no external task is required to generate test reports. The TestNG framework generates an HTML report it support extends with ReportNG.

And also we are providing results is Spreadsheets of different flows based on various conditions by using conditional constructs such as 'if'

UI Mapping or Object Repository

A UI map is a mechanism that stores all the locators for a AUT in one place for easy modification when identifiers or paths to UI elements change in the AUT. The test script then uses the UI Map for locating the elements to be tested. Basically, a UI map is a repository of test script objects that correspond to UI elements of the application being tested.
What makes a UI map helpful?
Its primary purpose for making test script management much easier. When a locator needs to be edited, there is a central location for easily finding that object, rather than having to search through test script code. Also, it allows changing the Identifier in a single place, rather than having to make the change in multiple places within a test script, or for that matter, in multiple test scripts.
To summarize, a UI map has two significant advantages.

• Using a centralized location for UI objects instead of having them scattered throughout the script. This makes script maintenance more efficient.
• Cryptic HTML Identifiers and names can be given more human-readable names improving the readability of test scripts.

There are various ways a UI Map can be implemented. Following are the few famous ways :

• Properties File In Java
• XML File
• Excel Sheet
• Java Class File(stores public String variables each variable storing a locator value)

FRAMEWORK ARCHITECTURE