Functional test best practice
Download as PPTX, PDF0 likes458 views
This document discusses best practices for functional test automation. It begins by describing common failure patterns seen in test results, such as single tests failing across browsers or browsers failing all tests. Problems like fragile selectors that don't work across browsers, timing issues, non-deterministic tests, and test dependencies are explained. Best practices to address these problems include using stable selectors, avoiding sleeps/waits and making tests self-contained. The document also introduces Test Armada as a solution for running tests across platforms and browsers, and collecting results and insights. It concludes with contact information for further questions.
Functional test best practice
- 1. E X P E R I E N C E T O O L S CUSTO M ER E X P E R I E N C E T O O L S DEVELOPER Lei Zhu October 23, 2018 Functional Test Best Practices
- 2. Introduction Lei Zhu Software Engineer WalmartLabs EMAIL: lzhu@walmart.com
- 3. Agenda • Test Automation Result Patterns • Common Problems & Best Practices • Test Armada’s Solution • Q&A
- 7. Single Test Failing on All Browsers
- 8. Single Browser Failing for All Tests
- 11. Common Problems & Best Practices
- 12. Common Problems: Selector Test Pattern • All tests fail in particular browser(s) Problem • Selector only works on some browsers or OS Example: :nth-child
- 13. Best Practices: Selector Best Practice • Support same selector for mainstream browsers • Selector: .class_name
- 14. Common Problems: Timing Test Pattern • One test fails in all browsers Problem • Test relies on sleeping or timing tricks to pass Example: sleep(), pause()
- 15. Best Practices: Timing Best Practice • Use wait() instead • Only operate when element is operable • Page is fully rendered • Element is in DOM • Element is in viewport • Insulate test from loading network resources
- 16. Common Problems: Non Deterministic Tests Test Pattern • One test fails in all browsers Problem • Non-deterministic test Example: Rolling Carousel
- 17. Best Practices: Non Deterministic Tests #1 Best Practice • Create predictable test • NO conditional statement • One test for one path
- 18. Best Practices : Non Deterministic Tests #2 Best Practice • Make AUT act predictable to accommodate automation
- 19. Common Problems: Test Dependencies Test Pattern • One test fails in all browsers • All tests fail in all browsers Problem • Test relies on result of other tests
- 20. Best Practices: Test Dependencies Best Practice • Isolate test from others • Use hooks to create repeatable test
- 22. Test Armada: High Level Architecture AUTOMATION TEST ARMADA DATA INSIGHTS TEST ARMADA MOCKING APPIUM Sauce Labs TestObject GITHUB
- 24. Q&A