Design patterns in test automation
•23 likes•25,609 views
Report
Share
Design patters exist for years in software development. Some developers love them, some think they are useless. But design patters has very clear goals: describe common solutions for common problems, create shared language for community, improve understanding and reuse of existing approaches. Test automation has its own set of problems, so there is a set of helpful design patterns for this area. In this talk I will run through all known patterns and describe them in details with several practical samples.
![[기본과정] 코드 테스트와 커버리지 기본 교육(개념)](https://cdn.slidesharecdn.com/ss_thumbnails/basicofcodeleveltestandcoverage-190203041600-thumbnail.jpg?width=384&fit=bounds)
More Related Content
What's hot
What's hot(20)
Similar to Design patterns in test automation
Similar to Design patterns in test automation(20)
More from Mikalai Alimenkou
More from Mikalai Alimenkou(20)
![Hexagonal architecture with Spring Boot [EPAM Java online conference]](https://cdn.slidesharecdn.com/ss_thumbnails/hexagonalarchitecturewithspringboot-180925151506-thumbnail.jpg?width=768&fit=bounds)
![Bro, manage test data like a pro! [QA Fest 2018]](https://cdn.slidesharecdn.com/ss_thumbnails/bromanagetestdatalikeapro-180922193659-thumbnail.jpg?width=768&fit=bounds)
Recently uploaded
Recently uploaded(20)
Design patterns in test automation
- 1. Design patterns in test automation Mikalai Alimenkou http://xpinjection.com @xpinjection
- 4. Disclaimer This talk is based on personal experience
- 5. Design pattern? What is it?
- 7. Main driver is *ity Test Logic Application Driver Test Data Reliability Clarity Flexibility Maintainability Stability
- 8. Structural Patterns Structure test code better to improve maintainability, avoid duplicates and separate concepts, so it becomes easier for test engineer to understand, change and support tests.
- 9. Index Page Main Page login Search Page search filter ordersearch Details Page open see more show me like this close #1. Page Object
- 10. Page structure
- 12. #2. Fluent/Chain of invocations
- 14. #4. Page Element/Composite List of Items Link Menu Panel Checkbox
- 17. #6. Strategy • Validation • Navigation • Calculation • Execution
- 18. Data Patterns Separate data management from test logic and reduce amount of data related boilerplate code in tests, making logic more clear and maintainable for test engineers.
- 19. #7. Value Object
- 20. #8. Builder
- 23. #11. Object Pool/Flyweight • DB instance • Browser • Pages • Heavy domain objects
- 25. Entity Driven Data Provider
- 26. Technical Patterns Keep technical aspects separately from test logic if some additional level of control or low level data is needed, reducing tests complexity and improving test code maintainability.
- 27. #13. Decorator Driver in driver in driver in driver in driver in driver in driver in driver in driver…
- 28. #14. Proxy
- 29. Use HTTP proxy for tests • Blacklist external resources (Facebook, Twitter, Ads, etc.) • Cache images and other nonfunctional resources • Collect HTTP traffic for analysis (404, redirects, loading time, etc.) • Speedup page loading
- 30. Business Involvement Patterns Try to bring business people and requirements as close as possible to test automation, making it more valuable and helpful for the whole product team.
- 31. #15. Keyword Driven Testing
- 34. #17. Steps
- 35. WebDriver or Pages inside
- 36. Steps is a key for success Acceptance tests Page Objects
- 37. Steps in different formats = Testing scenario WebDriver test
Editor's Notes
- This is all I wanted to share with you today. Thanks for participation! I would be happy to answer any questions or continue discussion during the break.