Date post: | 18-Jul-2015 |
Category: |
Software |
Upload: | hong-zhang-pmp |
View: | 53 times |
Download: | 0 times |
Welcome!
Capital Region
Test Automation MeetupJanuary, 28th, 2015
Brief Introduction
My company:
• #1 SAAS solution for IT Service Provider
• Product available in 7 languages
• Product used in 90+ countries
• Best places to work 10 years in a row
Myself:
• Test Automation Team Lead
• 8+ years of experiences in testing & automation
• Experienced in automating Web, Windows, Mobile, API…
• Commercial, Open-source & build-in-house tools
Feedbacks from last meeting
11
10
9
5
3
0
2
4
6
8
10
12
Process Tips& Tricks
StartingAutomation
Tips
APIAutomation
Selenium MobileAutomation
10 tips for
starting test automation
#1: Define a test strategy
#1: Define a test strategy
Analyze your AUT (platforms, devices,
frequency of test, etc)
Focus on things matter most
Review historical data of critical customer reported bugs
Select a test automation suite
#2: Get support from upper management
#2: Get support from upper management
Get approval for resources
Get support from Dev team
Get support from Infrastructure team
Understand what automation takes
#3: Get the resources
#3: Get the resources
Get the right people
• Internal transfer VS new hire
• Veteran VS college graduate
Get the right tool
• Open source VS commercial tools
• Develop tools VS purchase a tool
#4: Set the right expectations
#4: Set the right expectations
Run automation by a few button clicks
Automate 2,000 test cases
Reduce customer reported bugs by 50%
Improve code test coverage to 80%
Which one is right for your company?
#5: Set a good process
#5: Set a good process
Who creates the manual test cases to be
automated?
Test case standards
Test case review process
Test case update process
#6: Plan your automation
#6: Plan your automation
Start from something small
Perfection game
Celebration is important
#7: Measure ROI
#7: Measure ROI
Labor – FTE
Time – TTM
Quality:
• Bugs found by automation
• Bugs found by customer
#8: Follow software engineering disciplines
#8: Follow software engineering disciplines
Review standards from your Dev team
Follow code standard (naming conventions, comment,
etc)
Code reviews
DRY
Test your code (force your test to fail)
Always refactor your code
#9: Stay current
#9: Stay current
Booming industry
Fast evolving automation technologies
Self-motivated and fast-learning ability is key
Knowledge share
#10: Support our community
#10: Support our community
The most difficult part of test automation?
A good community is a place people can:
• Ask for help
• Provide help
• Share resources (ideas, opportunities)
• Have fun
We need speakers for future meetup events
Thanks to our sponsors
Thank you!
www.meetup.com/AutomationRocks
Share, Learn, Have fun