Book Image

Continuous Delivery for Mobile with fastlane

By : Doron Katz
Book Image

Continuous Delivery for Mobile with fastlane

By: Doron Katz

Overview of this book

Competitive 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.
Table of Contents (27 chapters)
Title Page
Dedication
www.PacktPub.com
Foreword
Contributors
Preface
Index

Continuous delivery and testing


The emphasis of this book is on continuous delivery, so it's not only important to include testing in your workflow but also to be able to distribute to testers continuously and effortlessly. Most projects these days at least practice a form of agile development, which means working in sprints.

A sprint is an agile concept which time-boxes durations of around three to four weeks, in which a development feature is completed. The completion of features in a sprint is based not only on development completion but more importantly, test completion.

During this rapid development mini-iteration series, it is imperative that developers release a feature for testing, testers discover bugs, developers resolve, and testers verify once more until the project passes test completion. This is essentially what constitutes an agile sprint that progresses towards feature completion.

Before a feature can satisfy the Definition of Done (DoD) (https://www.scruminc.com/definition...