How to understand when a project needs automation

1
Ivanna Kyryk Program Manager at QATestLab James
Briers Co-Founder and Delivery Director at
Intelligent DS
How to understand when a project needs automation
2
Agenda
Purposes of test automation Prerequisites for
automation Start of automation Test Automation
Pyramide Reasons of automation fail
3
Purposes of test automation

• To improve the effectiveness of testing
• To accelerate testing
• To make testing transparent
• To reduce expenses on testing

4
(No Transcript)
5
Aspects to consider
Project size
Team size
Generation of test data
Release frequency
Support of old versions
6
How to start automation?

• Define what to automate
• Determine ways of automation
• Select means for automation

7
What to automate?

• Frequently used functionality
• Repetitive actions
• Tests with multiple data sets
• Tests for different software and hardware
  configurations
• Time-consuming tests
• Calculating algorithms, etc.

8
What NOT to automate?

• Newly created tests
• Ad Hoc tests
• Projects with fast-changing requirements
• Unstable functionality

9
Test Automation Pyramid
10
How to select automation tool?

• Do not use beta versions and unstable tools
• Tools should correspond to the specifics of your
  software
• Use feature-rich tools with trial period
• Verify tool integrability
• Choose a tool with wide support and documentation

11
Why automation may fail

• Incompetent team of automation engineers
• Implementation without proper planning
• Too late start of test automation
• Prejudice that manual testing is cheaper
• Unstable environment and frequent changes

12
Test automation will ensure high ROI, accelerate
software delivery and improve software quality
only if it is applied to the proper project.
13
Contacts
E-mail contact_at_qa-testlab.com
Twitter QATestLab
Phone [phone] Address 154a,
Borschagivska str., 03056, Kiev, Ukraine
Web-site qatestlab.com
SkypeID sales.qatestlab
14
Thanks