This is an introduction to Software test automation.

IntroductionEffective Automation

• Fundamental Approach
• Real Facts & Think Factor
• Considerations for Automation
• Automation Start-up Strategies to Avoid
• Guidelines & Approach
• Automation Methodologies
• Overview on Automation Tools
• References

Introduction

"Embarking on a successful automation test project is similar to embarking on a successful software development project

Reduced utilization of manual resources
More efficient use of scarce hardware resources
Reduced test cycle time
Reduced cost of testing, after initial cost of implementation
Improved reliability of the testing
Repeatable tests, thus overcoming boredom-induced missed bugs
Improved test coverage, since testing may be done more frequently
Development of programming skills
May allow the use of less skilled staff to do the actual testing  

Effective Automation

Reduced utilization of manual resources
More efficient use of scarce hardware resources
Reduced test cycle time
Reduced cost of testing, after initial cost of implementation
Improved reliability of the testing
Repeatable tests, thus overcoming boredom-induced missed bugs
Improved test coverage, since testing may be done more frequently
Development of programming skills
May allow the use of less skilled staff to do the actual testing

Fundamental Approach

Understand the need / requirement for automation
Point out pitfalls to avoid
Promote an evolving implementation
Begin simple and increase in complexity as the team's skills increase

Real Facts & Think factors

Real Fact
Automation is initially expensive and it may not do a better job than manual testing in some situations

Think Factors
How much will automating and running a test cost, versus running it manually?
Automated test has a limited lifetime in which it must recoup the additional cost. Will this test be reusable long enough? What factors will prevent it from being reusable?
The automated test will find bugs it was designed to test for and in addition it will find bugs that are not directly related to the test. What is the likelihood that this test will find additional bugs?

Considerations for Automation

Test cases those are long running, repetitive, and non-subjective

Projects / Products that have a working, relatively stable GUI

Projects / Products that will span multiple releases.

Guidelines & Approach

Record / Playback initially using the Testing tool