In Part 3, I showed how you can automate typical CRUD flows in any hybrid or native app built using the Salesforce1 Mobile SDK. As I mentioned earlier as well, it’s good to be able to create UI tests with literally point and click capabilities using Appium, but it’s a far fetched reality from achieving end to end automation testing.
So, let’s now solve the last and the most interesting part of the jigsaw puzzle and write some code to build our UI automation framework.
In Part 1, I introduced the concept of mobile automation testing, discussed key challenges and then laid the ground for why I chose Appium as my preferred framework for Salesforce1 mobile automation. In Part 2, I explained how to use Appium Inspector and showed with a demo how you can automate the oAuth dance for Salesforce1 Mobile SDK apps.
Now, let’s get down to business – the key operations in any mobile app are some sort of CRUD (Create, Read, Update, Delete) operations. Let’s explore how we can leverage Appium to automate these flows without actually writing a single line of code!
Last day of year 2014 and what better than writing a post about my most interesting research of this year for the Salesforce Mobile SDK! In the previous post, we learnt about the need and challenges associated with mobile automation testing in general. Now, let’s move forward and explore an example with some uses cases of typical mobile automation requirements in Salesforce1 apps.
Let’s consider the sample AccountEditor hybrid app that’s shipped with the Salesforce1 Mobile SDK to identify some automation use cases. Continue reading