Book Image

Hands-On Full-Stack Development with Swift

By : Ankur Patel
Book Image

Hands-On Full-Stack Development with Swift

By: Ankur Patel

Overview of this book

Making Swift an open-source language enabled it to share code between a native app and a server. Building a scalable and secure server backend opens up new possibilities, such as building an entire application written in one language—Swift. This book gives you a detailed walk-through of tasks such as developing a native shopping list app with Swift and creating a full-stack backend using Vapor (which serves as an API server for the mobile app). You'll also discover how to build a web server to support dynamic web pages in browsers, thereby creating a rich application experience. You’ll begin by planning and then building a native iOS app using Swift. Then, you'll get to grips with building web pages and creating web views of your native app using Vapor. To put things into perspective, you'll learn how to build an entire full-stack web application and an API server for your native mobile app, followed by learning how to deploy the app to the cloud, and add registration and authentication to it. Once you get acquainted with creating applications, you'll build a tvOS version of the shopping list app and explore how easy is it to create an app for a different platform with maximum code shareability. Towards the end, you’ll also learn how to create an entire app for different platforms in Swift, thus enhancing your productivity.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Automated testing pipeline


Usually, when working on larger projects with multiple people, you would want to ensure that the code quality does not degrade over time. There are several ways to do this; one way is by reviewing code before merging it. You can also require tests to be added for a new feature or require existing tests to be updated to ensure that you have enough code coverage for the feature or a bug fix is being introduced. We can create a checklist for the contributors to add test, but having a way to run the tests for every code change request sent along with running tests every time any changes are merged into the repository is the best way to detect issues early and fix them before they go to production. This practice of running tests on your project on a regular basis is known as Continuous Integration and ensures that there are no issues in production.

Having a CI pipeline helps developers find issues earlier by running the tests automatically and can act as a gatekeeper...