Key Factors To Ensure Test Automation Framework Success
1 like3,440 views
This document discusses key factors for ensuring the success of a test automation framework (TAF). It outlines various elements that should be considered when setting up a TAF, including supporting different application types like web, mobile, and APIs. Important TAF features that are described include being keyword/data-driven, handling test flows and errors, and generating execution and historical reports. The document also provides recommendations for integrating the TAF with continuous integration systems for scheduling tests, notifications, load balancing and distributed execution to save time.
Key Factors To Ensure Test Automation Framework Success
- 1. Key Factors To Ensure Test Automation Framework Success NOVEMBER | 2015 THIEP TRUONG
- 2. My Background • Thiep, Truong Xuan – QA Architect at KMS Technology VN • 3 yrs+ experience in software development • 10 yrs+ experience in software testing • BS in Mathematics and Computer Sciences, major: Abstract Analysis • Hobbies: Martial Art, Foosball, Motorcycle, etc. • Contact: • Personal email: truongxuanthiep@gmail.com • Skype: truongxuanthiep • Mobile: 0902 862 622 2
- 3. AGENDA • Test Automation Framework (TAF) • Application Support • Key Features • Summary • Q&A 3
- 4. 4 Key Elements To Setup A Solid TAF
- 5. Test Automation Framework • Needs • Intermediate & Advanced Users • Architecture: File system & Database • Application Support: Web, API, Mobile, etc. • Features: keyword/data driven, distributed execution, etc. 5 http://www.zenqconnect.com/services/TestAutomation.aspx
- 7. Web Application Testing • Libraries selection • Across browsers (desktop only) • M dot sites (mobile only) 7 http://static.thetechjournal.net/wp- content/uploads/2011/05/online-tools.jpg
- 8. Mobile Native Apps • Libraries selection • User defined controls • MDM integration 8 http://kochartech.com/blog/2013/05/13/mobile-device-management-cloud- or-on-premise/
- 9. Web Services • Libraries selection • Algorithms to extract/validate data from responses • Security 9 http://di-side.com/it/di-side/services/web-solutions/rest-webservice-symfony/
- 10. DB Accessing • Libraries selection • Format, store and manage result sets 10
- 11. 11 Key Features
- 12. Object Inspectors • Desktop browsers • Mobile browsers • Mobile native applications 12
- 13. Keyword, Data Driven • Built-in keywords • User defined keywords • Data: location, formats • Data population, looping and filtering 13 http://www.ranorex.com/blog/keyword-driven-test-automation-framework
- 14. Flow Controls • Controlling test steps • Error handling • Condition & loop expressions • Invoke test script 14
- 15. 15 Key Indicator For Execution & Historical Reports
- 16. Execution & Historical Reports • Needs • Information • Rerun Failed Cases • Bug tracking system integration 16
- 17. Import & Export • Test script/suite/project/workspace • Executable exported files 17
- 18. 18 Why & How To Automatically Execute A Test Suite
- 19. Scheduling • Automatically detect changes and start running your test suite • OS native scheduling tools • Leverage CI systems like Jenkins 19
- 20. 20 Why & How To Setup The Notification
- 21. Notification • We will be automatically informed when running a test suite is completed • Leverage CI systems like Jenkins • Implement a feature for email notification 21
- 22. 22 How To Save Execution Time Of Your Test Suite
- 23. Distributed Execution • Selenium Grid • Suggested solution 23 http://www.codeproject.com/Articles/9415/Distributed-Command-Pattern-an-extension-of-comman
- 24. 24 Why & How To Setup Test Load Balancer
- 25. Load Balancing • Save execution time and leverage all idle systems • Suggested solution (for DB only) 25
- 26. CI Integration • Scheduling & Notification • Command line mode 26
- 27. Code Generation • Needs • Scripting mode 27
- 28. Summary • TAF supports applying automation testing • TAF’s users define how a TAF looks like • Application types: Web/API/Mobile, etc. • File system versus Database • Necessary features • Evaluate and select appropriate tools/libraries 28
- 29. 29 Q&A
- 30. © 2014 HCMC Software Testing Club THANK YOU