Continuous Delivery for Mobile with fastlane

Doron Katz

• Publisher: Packt Publishing
• Year: 2018
• ISBN:
  9781788391252
• Edition: 1
• Topic: Informatica
• Subtopic: Programmazione in Ruby

Learn continuous deployment and automation with code-signing, continuous testing, building, deploying, and releasing of your app. About This Book• A practical guide on automating your mobile development pipeline with Fastlane, Jenkins, and Slack.• Build, test, run and deploy your mobile application release with this end to end guide.• Implement Continuous Integration, delivery, and deployment practices to optimize your application development workflow for faster and efficient release builds.Who This Book Is ForThis book is intended for mobile developers who are keen on incorporating Continuous integration and deployment practices in their workflow.What You Will Learn• Harness the fastlane tools for the Continuous Deployment strategy• Integrate Continuous Deployment with existing Continuous Integration.• Automate upload of screenshots across all device screen-sizes• Manage push notifications, provisioning profiles, and code-signing certificates• Orchestrate automated build and deployments of new versions of your app• Regulate your TestFlight users and on-board new testersIn DetailCompetitive mobile apps depend strongly on the development team's ability to deliver successful releases, consistently and often. Although continuous integration took a more mainstream priority among the development industry, companies are starting to realize the importance of continuity beyond integration and testing.This book starts off with a brief introduction to fastlane—a robust command-line tool that enables iOS and Android developers to automate their releasing workflow.The book then explores and guides you through all of its features and utilities; it provides the reader a comprehensive understanding of the tool and how to implement them. Themes include setting up and managing your certificates and provisioning and push notification profiles; automating the creation of apps and managing the app metadata on iTunes Connect and the Apple Developer Portal; and building, distributing and publishing your apps to the App Store.You will also learn how to automate the generation of localized screenshots and mesh your continuous delivery workflow into a continuous integration workflow for a more robust setup. By the end of the book, you will gain substantial knowledge on delivering bug free, developer-independent, and stable application release cycle.Style and approachA step by step guide taking the readers through all the tools of fastlane.

Automate Unit Tests with scan

So far, we have accomplished a lot with fastlane, automating our workflow from registering to building our apps to publishing them to the app store, along with screenshots and metadata. As you pasue to appreciate how much easier our workflow is, be assured that we aren’t done yet; there is still a lot more to offer, and we will continue to press on with our next action, scan (https://docs.fastlane.tools/actions/run_tests/).

scan fits into our fastlane workflow seamlessly, allowing us to conduct automated testing, either adhoc or as part of our Fastfile, making it easier to create specific configurations to output tests in either HTML, JSON, Unit reports, or through sending the outcome straight to Slack. This action is certainly an important one that should be a part of your lane right before you publish to the App Store, or for beta-testing, to ensure the unit and regression integrity is maintained.

Before we dive deep into what fastlane offers us, we will give you a quick introduction to how to conduct unit testing in iOS 11, which will serve as an excellent segue into the rest of this chapter. We will also be using our project to explore existing unit tests.

By the end of this chapter, you will have learned how to add scan to your workflow process, which will:

• Create a test script
• Run a test script
• Create a test script report

We will be working with scan through the command line to:

• Create and run test scripts
• Integrate the lane into our project Fastfile

An introduction to testing in iOS 11 and Swift 4

This section won't cover everything with unit testing, and there are really interesting sub-topics with testing that you should get familiar with at your own leisure. For some great unit-testing resources, refer to What's New in Testing (WWDC 2017) (https://developer.apple.com/videos/play/wwdc2017/409/) and Testing with Xcode (https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/testing_with_xcode/chapters/03-testing_basics.html).

Unit testing can be defined as a function that tests an aspect of your app. A good testing strategy takes into account testing any new components that are created or changed, from the core functionality boundary testing, to testing bug fixes. Testing also needs to be repeatable and self-validating, or, in other words, you should be able to assert the same results each time you run the test, and the tests should be a clear pass or fail. Furthermore, good tests also need to be independent and decoupled, and should not require any dependencies, setup, or tear-down prior to the commencement of the next testing method.

With that in mind, we are going to start by creating a skeleton unit test class and then explore some of the existing and complete u...