Why Are Test
Automation Frameworks Needed?
Test automation
frameworks improve test automation efficiency,
scalability and greatly reduce the test
maintenance overhead by enabling reuse and
sharing of automation scripts and the flexible
sharing of test
data.
This approach
has a compelling ROI, because you can implement
more frequent test cycles at a lower
cost.
When implemented
correctly, automated test tools deliver on
their promise of more thorough and efficient
testing, achieved with less manual effort.
However, implementing a significant suite of
automated tests is a task comparable to a
significant software development
project.
On the other hand, it is
entirely possible to quickly develop a
(smallish) set of tests using automation tools
from vendors such as HP/Mercury, or IBM
Rational, in exactly the same way it is
possible to quickly build a software program
using an IDE and/or a compiler.
However, with larger scale
projects the same challenge exists with
developing tests as it does with developing
software. The primary challenge is to architect
a framework for a suite of tests that is
efficient, scalable and maintainable.
In addition, many clients
want a less technical, user interface to the
test environment, so that business users are
able to execute tests in a context they are
familiar with, such as a spreadsheet, or simple
GUI.
Another factor is the
availability of business users with domain
knowledge. It is important that business users
validate the business process flows of a new or
changed system are correct and complete.
However, obtaining
sufficient time from these business users is
always challenging because of their BAU
commtments, especially if a succession of
releases or upgrades have to be tested.
The key objectives of an
automation framework therefore are:
-
To enable reuse and sharing of
automation scripts to improve
efficiency and scalability.
-
To reduce the test maintenance
overhead.
-
To provide a non-technical user
interface for business user
testers.
-
To capture and leverage the domain
knowledge of business users into a
set of regression tests that can be
executed repeatedly without needing
the business users to be present.
Without a suitable
architecture and framework, many test teams hit
a ‘wall’ where the effort to change and
maintain their portfolio of tests becomes so
large that this consumes the bulk of their
available time. The end result is that test
coverage growth stops, or reverses under the
weight of this maintenance effort.
This is IBM’s to Choosing a
Test Automation Framework where Hybrid is
mentioned. We should include it on our page why
frameworks are needed.
Additional Material
This is IBM’s Guide to
Choosing a Test Automation Framework
http://www.ibm.com/developerworks/rational/library/591.html
This article discusses
situations where automation has failed because
of a lack of suitable frameworks. http://www.kaner.com/lawst1.htm
Footnote:
The whitepaper by Carl Nagle
Test-Automation-Frameworks
is often considered to be a seminal work on
this subject. TestPro has taken these ideas
and extended them to optimise the benefits
you can achieve from automation frameworks,
using advances in tools and technology since
the paper was written.
|
