By: Priyanka Gurumallegowda

Agenda
Software Test Automation Myths and Facts

What is Automation?
Why Automation required?

Automation Life Cycle

Evaluation of Tools Best Practices

Software Test Automation Myths and Facts

Myths:
Find more bugs- From test cases to test scripts, automation

does not add anything in the process to find more bugs. Eliminate or reduce manual testers- Elimination or reduction of manual testers is not any of the objectives of test automation

Solutions/Suggestions
Realistic expectations
Proper Planning

Good Process

Automated Testing
The principle of automated testing is that there is a

program that runs the program being tested, feeding it the proper input, and checking the output against the output that was expected.

Why is Automation Required ????

Benefits of Automation:

Saves Time Large number of test cases can be executed. Helpful in Regression Testing Decreases monotonous job Saves Labor Gives time to do other part of testing which cant be done by automated testing No manual intervention required

Evaluation of Tools
Cost of the tool
Technology is supported by the tool? Performance techniques of Tool Number of Tools under Evaluation Needs to Be Limited Vendor Tactics Need Active Management Proof of Concept

ATLM Process Hierarchy

4. Test Planning, Design & Dev elopment 3. Automated Testing Introduction Process

5. Execution and Management of Tests

Automated Testing Lif ecy cle Methodology (ATLM)

6. Test Program Rev iew & Assessment

1. Decision to Automate Test

2. Test Tool Acquisition

ATLM Process Hierarchy

Decision to Automate
Test Tool Acquisition Test Planning, Design and Development Execution and Management of Automated Test Process Evaluation and Improvement

Step by Step approach for automation

Analyze the Automation effort
Analyze the Reuse potential of Automated modules Focus Automation on Repetitive tasks Focus Automation on Data-Driven tasks Consider the Test Tools capabilities Automate Test Requirements based on risk Automate Test Design standards

Best Practice
Document the process

Manage Expectations
Use a pilot project Verify test tool compatibility

Verify test tool upgrades

Avoid incompatible test tools Baseline the system setup and configuration before

installing a new tool Avoid unnecessary software installation in an alreadybaseline testing environment

Best Practices ctd.

Understand the overall test program objectives
Remember that not everything should be automated Keep automation simple Follow test procedure design and development standards

conduct automated versus manual test analysis Conduct reuse analysis Encourage test team partnership with all teams involved in the system development cycle Keep well the communication flow

Best Practices ctd.

Ensue Schedule compatibility
Involve the customer from the beginning of SDLC Document and report defects Use an automated test expert or tool advocate to sell the

benefits of the automated tool within the project team Clarify test team assignments Suggest test tool improvements to the vendor Take advantage of the knowledge of the specialty topic experts