Imagine your QA/QE teams that have either created, or adopted an existing automation framework, based on Selenium, to suit their technical needs. However, some of the work flows are repeated across multiple teams, where duplication of those automated flows are now maintained separately.
Now, also further imagine that each QA/QE team has their own page objects. Unfortunately, managing those page objects, even while practicing those “best practices” just aren’t cutting it.
Listen to senior automation engineers, also organizers of DC Agile Software Testing, the largest Agile Test Meetup in the DC metro area, Peter Kim and Cynthia Wu, share how they overcame these challenges, with a step-by-step show-and-tell. This session will indulge you on adopting and applying a model based automation design and strategy to drive overall quality, reliability, and scalability, using a Selenium based framework, for successful integration and acceptance testing. Join our session to hear and see live demos of a model based approach compared to existing “best practices”.
This session will include discussion on the pros and cons of a model based design in contrast with existing best practices in PageObject (Factory) approach and design.
Learn how our QA/QE teams, each using their own framework, using C#/NET, Nodejs, Java, and Ruby were able to use a simple design and strategy to empower each team to continue with using their own framework, while enjoying the ability to successfully co-share workflows and even those pesky page objects.
During this session, you will hear and see live demos of our “statement of the problem” – multiple frameworks that were written using ‘best practices’, yet unable to co-share test artifacts with other well-written frameworks.
