Information Technology Reference
In-Depth Information
and test bed creation. Some amount of database testing was also being automated.
Then, in the 1990s, when the Internet started to make its presence felt, some test-
ing tool vendors appeared on the horizon. These early tools were able to capture
user screens and user activity during transactions. Most of this automation can be
referred to as “record and play.”
In recent history Worksoft and some other vendors have introduced some tools
that capture the business logic of any application in such a way that even when
there are changes in the application, the automation code also gets changed and
thus runs without needing any maintenance of the script. This functionality is
called code-free automation. Basically these tools store information on all captured
objects during recording in a database and map this information when the test
scripts are run. It is known as application mapping.
...
Case Studies
In recent years, test automation has created a lot of excitement among customers,
and they have been looking to reap promised benefits. Of course automation brings
benefits, but uninitiated people find it difficult to understand in what way and how
many benefits can actually be realized.
Here are a few case studies for software test automation projects. In most of these
cases, the customers had wrong notions of benefits arising from automation projects
and needed a thorough explanation and convincing by the service provider.
9.3.1
Business Case 1
9. 3.1.1
Wrong Customer Expectations
It was required to execute more than 600 test scripts within a span of 3 hours. It was
required that the automation scripts should be easily maintainable and maintenance
costs should be kept to a minimum. The scripts should be executed unattended.
9. 3.1. 2
Problem Statement
Customer expectations were not met.
◾
Project was suspended due to low customer confidence.
◾
9.3.1.3 Issues Faced
Lack of customer knowledge about what testing tools can do and what we
◾
can get out of using these tools.
Wrong customer expectation about amount of time required in automating
◾
test cases. The expectation was that using automation tools testing cycles will
