Automation test suites allow teams to uncover defects faster with every new application release. While they provide efficiency, automation test teams should follow appropriate design principles consistently to build a highly robust, reusable, maintainable and scalable test framework. 

As they get started, Automation testing teams may prioritise short term benefits over the broader overarching test automation vision. This leads to a poor automation experience in the medium to long run. In addition, the choice of the test automation framework library plays a crucial role towards attaining the desired business goals. Over a period of time, some automation test frameworks have gone out of favour in the testing community, owing to: 

1. Deprecated / unmaintained open-source test framework library
2. Limited forums. Limited test community support
3. Limited built-in test parallelisation, limited built-in plugins etc.
4. Limited or no cloud platform support

Many such test automation teams encounter a need to migrate their automation framework to a new one or build a brand new framework implementation completely from scratch. In this session, I’ll take an example case study of how our team planned an automation test suite migration for Xamarin.UITest → Appium, and assisted a customer team implement it for their mobile app automation test suite. Specifically, I’ll be covering:

1. Triggers / Need for test automation migration
2. Applying a holistic migration strategy
3. Creating an implementation / action plan
4. Identified learnings post successful migration

With the advent and advancements in Web APIs, accurately displaying responsive web page content across fragmented mobile device browsers is merely just one of the checkboxes that Quality Assurance teams need to care about, albeit a very important one.

Similar to native / hybrid apps installed directly on Android and iOS, mobile web applications also implement advanced real world use cases that heavily leverage mobile device hardware such as processor, graphics, memory etc. and device sensors like camera, microphone, location, motion etc.

In addition, web apps can also access device OS level features for SMS/call integrations, notifications, payments, accessibility which further calls for testing such web apps on real mobile devices.

In our talk, we are going to cover -

1. Expansion of mobile web testing landscape with Web APIs

2. Why is mobile web testing important for businesses

3. Real-world mobile web testing customer use cases across Finance, Banking and E-commerce

4. Mimics for a real device : A risky business

5. Achieving versatility in meeting the dynamic infrastructure needs