About my time in Split, Croatia; about Schengen rules for travellers, and Uber outside of the US
Mobile testing requires you to cover many platforms. In the Android world, you are in even more trouble because of the large number of devices where this operating system is deployed. Today, many developers who started using Robotium to test their Mobile apps are slowly moving towards Appium to meet a new demand for the cross-platform market.
In this talk, we deep dive into Robotium and Appium. We determine when your team needs to consider changing what tool you use. We explore how to transition towards Appium successfully, and what mistakes you should avoid on both team and organizational levels.
Mobile Testing is hard! You have to test not only Native Mobile but also Web-based applications. This multi-platform focus makes the testing effort to be at least twice as complicated as when a simple web application is targeted.
With the growing market around smartphones, developers needed more ways to ensure software quality of their product. This need is why many mobile UI test frameworks have been introduced. With the most significant share of the mobile market being taken by Android OS, development and testing efforts have been especially crucial in this ecosystem.
Among the variety of Mobile UI automation tools, two frameworks have been especially notable: Robotium and Appium. However, with more organizations moving towards multi-platform solutions, those of us, who used Robotium, are slowly moving towards Appium. This journey from Robotium to Appium is where the main focus of this presentation lies.
In this session, we deep dive into both Robotium and Appium. We discuss why and how to transition from Robotium to Appium in the Android ecosystem. Lastly, we look at common mistakes made during this transition, and how to avoid them.
- Birds-Eye View of the Mobile Market
- Deep Dive into Robotium and Appium
- Tips and Trick for a successful transition from Robotium to Appium