The Salesforce Mobile SDK team has been working in overdrive mode for the last few months. While I was still catching up on the changes made in 5.0 release (released in December 2016), there has been substantial work done over the last quarter and v5.1 has been released earlier this week.
For someone who’s followed the Mobile SDK since it’s early days, I believe this release is a major milestone and a massive turning point for developers as it brings several features that turn this open-source Github project into an enterprise-grade development kit. Read on to know more about what’s changed, why and how it impacts you.
It’s the most exciting time of the year for any Apple developers (iOS/ watchOS/ macOS/ tvOS) – it’s WWDC 2016. Apple just released the Developer Preview for XCode 8 which lets you build and test your apps for iOS 10 – the next major version that will be released this fall.
The first thing I tried after downloading XCode 8 was to see how nicely (or how badly) the Salesforce iOS SDK will play with it.
Although I presented 3 sessions at Dreamforce 2015, only one – Building Salesforce1 Mobile Extensions with Swift was video recorded. The talk was presented at the Innovation Theatre in the Dev Zone and it was good to see a large turnaround for this rather unconventional topic.
I’ve played around a lot with Swift ever since it was launched. I also worked on porting some of my simpler Force.com Mobile SDK apps written in pure Objective-C to use Swift to better understand the nuances of Swift. While that exercise itself warrants a blog post and it’s on my to-do list, I’m writing a quickie to introduce this very interesting series of tutorials – ‘Designing Enterprise Mobile Apps With iOS and Salesforce’.
The series is a brainchild of Quinton Wall and I’ve been interacting with him about contributing my first tutorial to it – which should see the light of day very soon. Continue reading
The Force.com Mobile SDK 3.x has brought about some welcome changes such as Cocoapods support, Gradle support, Cordova update to 3.7 and many more. However, it has also meant that some things which worked perfectly in Mobile SDK 2.x no longer work. One such critical bug relates to how the image URLs are handled in Mobile SDK 3.x hybrid apps.
Read on if you are one of those hybrid developers who’s either upgraded your app from Mobile SDK 2.x or are about to do so. Continue reading
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!