COMAQA Winter 2017. Roundtable discussions: “Architecture for UI automation solutions”

Let us talk about UI automation architecture as a "Layered cake" via prism of modules, layers, architectural patterns, design patterns, both specific for QA Automation and general purpose. In Architecture, as in any other creative field, the most complicated thing, which is hardly acquired and difficult to formalize – is finding balance. How to find balance between complexity and simplicity, universality and specifics, agility, adaptability and specialization. Each reporter will look through the list of offered aspects of UI automation architecture through the prism of their experience. Of course, we can’t build the universal criteria of adequateness of architecture to the stated task, but we will come to some kind of consensus; in a structured form we will tell all of you different opinions, and I’m sure the listeners are going to receive a lot of useful information and can easily find balance when making architectural decisions during their everyday work.
1. Modules
2. Layers
3. Architectural patterns
4. Specific for QA Automation DP’s General purpose DP’s
5. Ho to make a right choice
6. Statefull and stateless solutions
7. Comparative analyses
8. Wrappers as a one of key points
9. Comparative analyses
10. Using cloud features: scalability, e.g.
11. Mobile: nuances if emulators or/and real devices usage
12. Parallelization and multithreading as part of TA;
13. Popularity of OS related tasks – working with OS file system, time, remote connection, WIN32 api, etc.
14. Criterias
15. Summary

Related Posts

Leave a comment