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 ...
Automated testing pipeline
Get Hands-On Full-Stack Development with Swift now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
