1. CQAA Automation Meetup
January and February 2017

2. Why are you automating? Reduce cycle time / save time
Increase coverage
Consistency/repeatability
Cost savings
Resource reduction/re-allocation
Corporate goals/direction
Find other bugs
Reduce human error
Can’t test otherwise / manual testing not possible
Risk mitigation
Environment Health and Setup verification
Performance verification
We’re not, but are planning on it

3. What do you automate? Regression (26 respondents) UI (21 respondents)
APIs (15 respondents)
Unit Tests (10 respondents)
Business process (9 respondents)
Test data (8 respondents)
Services (8 respondents)

4. When are you automating?
During Sprints
After Sprints
Regression
Test Driven Development (TDD)

5. What tools do you use to automate?
Selenium
UFT
Cucumber
Ranorex
Qualify
Home grown
Maven
Robot
SoapUI
Rest Assured
Eggplant
Smart Bear
AutoIT
Test Complete
SpecFlow
Appium
Visual Studio / Coded UI
Postman
Lisa
OpenScript
Jenkins
Docker
Sonar

6. What are the challenges when automating?
What to automate?
Finding skilled resources
Finding working tools
Keeping up with development pace
Platform selection
Language selection
Selenium Grid on Windows servers
Selenium on multiple browsers
Windows forms with Selenium
Identify POM / recognizing objects
Script Maintenance
Failed test cases – Data setup
Test data management / access
Flaky tests or flaky environments
Performance of tests (slow)
DEV support
Licensing (red tape)
Lack of documentation
Maintenance/obsolescence
“Versionitis”
Metrics to generate/report
Controlling management expectations related to value/ROI