Automated Web UI testing can be challenging when the UI flows on the desktop web and mobile web are different because the product experience is separately optimized for each screen size. I will demonstrate how to build a stable test framework and infrastructure for web applications from the scratch for the same. 

Enabling UI tests as part of the continuous delivery pipeline is crucial. I will brief how to design a framework that supports both desktop web and mobile web, building the infrastructure for executing the tests in parallel, and adding the tests into the continuous delivery pipeline using Selenium, Docker, and Jenkins pipeline.

I will discuss accessing native device components on the mobile web, minimizing the complexity of the business layer concept, and a template for selecting which cloud provider suits you for web testing.

In this talk, I will also cover how to create a slack notification service to send the high-level test result status to the team channel and the best practice for web locator strategy.

Techstack Used: Java, Selenium, Appium, Python, Docker

There are dozens of matured docker based solutions available in the market for Android automation testing,

but

what about iOS testing?

It’s hard to create and maintain the docker based solution for iOS testing since it demands the Xcode and for the optimal performance the system needs the Apple certified hardware.

Combining Ansible with Selenium Grid yields a powerful combination because it allows us to set-up our grid and nodes in just a few seconds. In this talk I will demonstrate how to use simulators to build a reliable and scalable in-house iOS simulator lab using Ansible, Selenium Grid and Appium.

Targeting both mobile devices and desktop browsers has become a necessity for successful tech applications. Whether an existing web application triggers the development of native apps or a desktop version is introduced to supplement the smartphone experience, supporting both worlds is a reality for a majority of businesses.
To maximise user experience, an application should behave as identical as possible across all platforms. However, more often than not versions for different platforms are built by different teams with different designers, possibly across multiple sites (even countries, continents, timezones) each with their own tech-stack and development process. In such a set-up, using different tools for automated testing could come naturally and add to the challenges of building a single product.
We argue that a common approach to test automation is critical. Not only will it save time and development costs, it can also increase communication and improve collaboration between teams and be a great facilitator for setting the focus on the product as a whole rather than separate deliverables for each platform. In this sense, it can serve as an umbrella across all involved teams.
We will demonstrate a simple JAVA-based solution using Selenium, Appium and Cucumber to combine testing for different platforms (namely Android, iOS and Web) within the same framework. We will talk about best practices in designing an extendable and easy-to-use test framework and how we can facilitate cloud-based services to integrate our tests into a CI pipeline.

Continuous testing is an integral part of continuous delivery pipeline. When it comes to mobile application, the testing become increasingly complex.

As part of our internal quarter hackathon at Carousell, we developed an automation testing framework and device lab in 48 hours which has both parallel and distributed mode of running.

We will share about how you can set up a similar device lab in your organization and the best practices to be followed.