A test automation framework is a set of assumptions,
concepts, and practices that provide support for automated
software testing. This article describes and demonstrates
five basic frameworks.

Basing an automated testing effort on using only a capture
tool such as IBM Rational® Robot to record and play back
test cases has its drawbacks. Running complex and powerful
tests is time consuming and expensive when using only a
capture tool. Because these tests are created ad hoc, their
functionality can be difficult to track and reproduce, and
they can be costly to maintain.

A better choice for an automated testing team that's just
getting started might be to use a test automation framework,
defined as a set of assumptions, concepts, and practices
that constitute a work platform or support for automated
testing. In this article I'll attempt to shed a little light
on a handful of the test automation frameworks I'm familiar
with -- specifically, test script modularity, test library
architecture, keyword-driven/table-driven testing,
data-driven testing, and hybrid test automation. I won't
evaluate which framework is better or worse but will just
offer a description and a demonstration of each and, where
appropriate, some tips on how to implement it in the IBM
Rational toolset.

classicatios mails me uvvsuresh@gmail.com