Integrating and Extending CocoaPods for Local iOS Project Management and Testing

The Qunar technical carnival featured a session on the Qmobile track, where engineer Wang Kunpeng shared the team’s experience integrating and extending CocoaPods for iOS development.

The presentation covered three main integration areas: dependency‑management integration, test‑engine integration, and team‑management integration, all aimed at boosting development efficiency and quality.

In the dependency‑management part, common problems such as debug flag loss, beta version mismatches, and cumbersome Podfile edits across multiple targets were identified. The solution involved using external scripts to enforce RC versions, separating version configuration, and providing a revised Podfile example.

The testing integration addressed the lengthy process of accessing the payment module by introducing a local mock‑data test project that can launch the checkout flow directly, reducing the need for full end‑to‑end navigation and unstable beta environments.

Team‑management integration tackled issues with differing Xcode certificates and frequent Podfile.lock conflicts. A Ruby‑based tool was created to automate certificate installation and test‑project switching, and the Podfile.lock file was removed from version control to avoid merge problems.

Overall, the approach demonstrates how a customized CocoaPods workflow can serve as a local engineering solution that simplifies dependency handling, testing, and collaborative development for iOS mobile applications.