UI Test Automation, with Selenium, has become the core QA strategy for functional testing. Most QA/QE teams continue leveraging automation designs and patterns following “best practices” that were adopted 10+ years ago. Yes, there are new technologies, some that have come and gone, as well as all the promises of continuous integration with continuous testing .. however the main contributing factor to a failed UI automation strategy is it’s core design. Despite all those cloud solution providers, advanced image detection solutions, and abundance of automation products – the truth is … design matters, or in this case – let’s discuss Application Modeling. First, the understanding of why those 10+ year old designs and patterns contribute to a losing automation strategy, that most team’s continue to adopt (at least as their starting point) , is crucial to helping QA leadership avoid making those mistakes that so many QA teams continue to hit. Second, let’s discuss how to implement an Application Model based automation framework. It’s a simple yet powerful strategy to ensure scalable, reliable, and ‘inclusive’ strategy. Application Modeling leverages meta-data programming and dynamic code generators to “model” the application with rulesets. This means more concise test coverage while spending less resources on writing mundane, copy/paste, .. otherwise throw-away code.

April 30 @ 10:50
10:50 — 11:30 (40′)

Nisarg Joshi, Peter Kim