1. Software test automation
Part 1. Introduction
Vitaliy Ganzha, 2012

2. Why to automate tests?
 Regression testing
 Volume testing
 Reduce human recourses requirements
 Reduce time-to-market (do releases more often, save time)
 Improve reliability and consistency of testing process
 Improve coverage, allow manual testers do more deep testing
of application
 Can achieve what manual testing can hardly accomplish, such
as memory leak detection under specific conditions;
concurrency testing and performance testing, and more.
 Repeatability, Reusability, Portability

3. Test Automation Myths
 Should find more bugs
 Eliminate or reduce manual testers
 Test Automation is simple, that every tester can do
 We can quickly increase testing speed
 Commercial test tools are expensive
 Automate 100% that is sure way to get ROI quickest
 Automation is a part time job

4. Some concerns
 Record/playback doesn’t work (at all!)
 Test cases based automation?!
 Does it make sense? (App, Env, Growth)
 Cost and time estimations
 ROI
 What to automate?

5. Test automation is a development!
 Test Automation should be designed,
developed and tested
 Should be planned
 Has a requirements analysis step
 It may have release cycle
 Source code should be versioned
 It’s a programming!
 Write according to standards.

6. Common types of automated testing
 Unit testing (xUnit, TestNG etc.)
 Performance testing (LoadRunner, Jmeter,
SoapUI)
 Functional System Testing (via UI, Web
Services, Data Base)

7. Tools
 There is no universal tool
 Every tool has it’s pros and cons
 Tool selection is a very important phase –can it work with AUT?
 Most commercial tools usually have more functionality (QTP
can test various GUI applications: Web, .Net, Java, VB, C/C++,
PowerBuilder, etc. vs. WATIR – Web only)
 Commercial tools has a support – it is important for big
companies

8. Questions?