For Impetus’ White Papers archive, visit- http://www.impetus.com/whitepaper
This white paper presents an overview of iLeap, which increases developer/tester productivity by providing a robust and easy-to-use framework.
Handwritten Text Recognition for manuscripts and early printed texts
iLeap- Test Automation Framework- Impetus White Paper
1. iLeap – The Test Automation
Framework
W H I T E P A P E R
Abstract
The automation framework is a set of assumptions, concepts,
best practices, and tools that provide support for automated
software testing. It also defines a structured approach towards
test automation. iLeap is an effort to utilize the existing
functionality of any functional testing tool and provide a
platform to do test automation in a simple and easy way.
This white paper presents an overview of iLeap, which increases
developer/tester productivity by providing a robust and easy-to-
use framework. Consequently, it encapsulates most of the
process internals of how to execute the test suite and enables
the developer/tester, to remain focused on designing the test
suite.
Impetus Technologies, Inc.
www.impetus.com
2. iLeap – The test automation framework
2
Table of Contents
Introduction...........................................................................................................3
iLeap workflow.......................................................................................................4
The iLeap architecture...........................................................................................5
Benefits..................................................................................................................8
Summary................................................................................................................9
3. iLeap – The test automation framework
3
Introduction
The ever increasing complexity and scale of IT applications has made quality and
reliability of paramount importance. However, delivering the same through
testing is becoming a challenge. Testing plays a major role in ensuring that
enterprise applications meet those standards. Testing is the main validation
activity used by the software development industry, and there is an urgent need
to improve its effectiveness with respect to cost. Software test automation has
the capability to increase the overall test coverage, while also improving
software quality.
Some of the common challenges faced in test automation are:
• Low or inappropriate test coverage: The Functional automation suite
only covers UI based test cases
• Negative Return on Investment (ROI): Schedules and budgets
overshoot with time
• High maintenance: There are frequent product changes, enhancement,
and new feature requirements
• Huge learning curve: Learning is required to create and maintain test
cases
To address all the above issues, Impetus has come up with iLeap, an
architectural blueprint of automation testing. It guides you to apply best
practices in automation testing and enables you to enjoy the benefits of the
functional testing tool.
iLeap is designed keeping in mind the Hybrid approach and supports functional
decomposition. It is a keyword-driven, and data-driven methodology, with the
highest potential for long-term success as testing is driven using tables with pre-
defined keywords and used in conjunction with data-driven testing. The test
steps can be developed earlier and maintained with just minor updates, even
when the application changes significantly. This approach is highly maintainable
and easier for non-programmers to work with. Our solution for test automation
meets all the demands of modern test systems. It consists of adaptable, object-
oriented components that ensure quick-and-easy implementation of
customized solutions.
4. iLeap – The test automation framework
4
iLeap workflow
The seven steps indicated below, define the complete workflow of the iLeap2.0
approach:
1. Identify automation candidates and develop the automation suite in
the Test Case Management (TCM) tool. iLeap enables the Functional
Testing tool to consume the test suites directly from the TCM tool.
2. Create the Object Repository in a format compatible with the
functional testing tool. iLeap reads the Object Repository from the
same location as defined by any Functional Testing Tool (FTT).
3. Create test steps for the automated test scripts using the Functional
testing tool’s tabular format. iLeap integrates its customized libraries
with the tool’s tabular view to use the same for creating keyword driven
test steps.
4. Create test data. iLeap enables you to either use the test data from the
tool’s data repository or from any database that the application
supports.
5. iLeap – The test automation framework
5
5. Define the execution strategy. iLeap consumes the test suites directly
from the TCM tool. Based on the execution requirement, it generates
the execution strategy based on suites defined in TCM.
6. Configure the test environment and other pre-requisites, before
executing the test scripts. iLeap enables you to define and run your test
suites on remote machines and monitor them from a single master
location.
7. Result reporting. Once the execution is complete, iLeap updates the
results in TCM. It also maintains the in-memory database so that the
results can be exported in supported formats like XML to enable user to
use it per his/her requirements.
The iLeap architecture
This paper describes the hybrid framework architecture. When used as a best
practice, this architecture ensures that the advantages of the multiple tools can
be leveraged. The architecture was chosen as it catered to most of the core
requirements, such as a hybrid driven framework addressing concurrent test
script execution, multiple browser support, extensible, easy-to-use, data driven
testing, and execution of test scripts with good reporting. The basic components
of the iLeap framework consist of the configuration and environment settings,
execution strategy, test case sequence (keyword driven), function library, object
repository, test data, and result reporting.
6. iLeap – The test automation framework
6
• Configuration and environment settings
This component will initialize and load the parameters required for the
test script execution. The user has the flexibility to update the
configuration settings, as well as select and execute tests by customizing
the parameters. Some of these parameters are: Base URL of the AUT,
type of browser, result path settings, generates automation suite, etc.
• Execution strategy
The execution strategy helps in the generation of the automation suite
in accordance with the testing needs. iLeap creates and stores the
automation suites as defined in the Test Case Management Tool (TCM)
and executes the desired suite. The execution strategy clearly separates
test case design and test framework execution. iLeap provides an easy
way to organize test cases and test data. The test execution engine
executes the test suites. The test design is performed based on
keywords, web objects, and test data.
7. iLeap – The test automation framework
7
• Test case sequence (keyword driven)
This component defines the actual test steps for the test scripts that are
planned to be executed. The test design is performed, based on
keywords, web objects, and test data. Keyword test cases are a
sequence of keywords designed to test or exercise one or more aspects
of the application. This is an effective standalone test design paradigm.
Using iLeap, it will also be able to use the record feature of the FTT so
that the creation of test case sequences becomes much easier.
• Function library
This is the core component of iLeap and is a library containing an
enriched set of generic and reusable methods to be used throughout
the Framework. The functional library contains the user defined
functions, which make your tests look shorter, easier to maintain, read
and design.
• The object repository
The automation framework identifies objects in your application based
on a set of test object properties. It stores the object data it learns in
the object repository. This component stores object/control's
information, such as locator values, etc., to enable their recognition
during test automation. Locator values of objects are stored and user
defined names can be given to the objects along with their description.
• Test data
Test data is data which has been specifically identified for use in tests. It
is essential to have well organized reference data which can be used as
a consistent source for refreshing the test environment on a need-to
basis. The data in every critical application should be sufficient to
validate all the functionalities. Also, care must be taken to validate end-
to end data. This component stores the set of data that is needed to
perform the operations on the application. This component enables
iLeap to utilize the test data that is either manually fed into the
functional testing tool's repository format or generated using the data
generator tool. The data can also be read from any database. The test
data may be produced by the tester, or by a program or function that
aids the tester.
• Result reporting
8. iLeap – The test automation framework
8
This component ensures that the test execution results are
automatically updated in the TCM tool after each run. It will also
maintain an in-memory database for the results, so that they can be
exported in the form of XML.
Benefits
The test automation framework allows teams to gain the benefits of keyword-
driven testing and double their test coverage, decrease testing time, improve
product quality, and cut costs. It allows members of a testing team to focus on
what they do best, and also allows non-technical testers and business analysts
to write automated tests. Although this approach has the largest front-end
investment, it has a very high ROI as it is the most fully automated testing
solution available. Some of the benefits of the iLeap framework are:
Reduced time-to-market and improved product quality
Automation with minimal coding knowledge
A component-based test framework that can bundle test cases together
based on modules
An easier test automation process
Keyword re-use across multiple test cases
Lowered maintenance costs
Easier customizability for all types of web application