Improving Map Client Testing Efficiency through Automation and Continuous Integration

The map client testing process involves functional, stability, static code, performance, compatibility, and security testing, along with auxiliary tasks such as test case, device, and project management, which often consume excessive manual effort.

Two examples illustrate inefficiencies: (1) lack of a centralized device‑management system caused lengthy device allocation; the solution was to develop a device‑management app and platform to track device status. (2) Complex large‑area search logic required 115 minutes per run; after code review, case automation, and sharing, execution time dropped 86% to about 15 minutes.

Key experience includes monitoring code submissions for core feature verification, achieving up to 40% automation of functional tests, reducing integration test cycles from 22 to 6 hours, and enabling daily gray‑scale testing of the Android map client.

Automation Setup

2.1 Test Case Adjustment – Ensure existing manual cases are automatable, with clear purpose and a single verification point; a good case example is searching from "my location" to "Xizhimen".

2.2 Automation Tools – Android uses Robotium, adb + bat scripts, Java; iOS uses UIAutomation, tuneup‑js + shell, MobileDevice, JavaScript.

2.3 Automation Framework – A keyword‑driven script model separates business logic from data, allowing interface replacement without rewriting scripts and supporting multiple data sets per case.

Implementation

3.1 Test Case Management – A unified platform generates synchronized Android and iOS test cases from a single entry, simplifying maintenance.

3.2 Continuous Integration – Jenkins automates daily builds, entry‑level testing, daily automated suites, and security scans; automated packaging monitors SVN changes every three minutes, triggers builds, and runs entry tests that alert developers on failures.

3.3 User Experience Hall – Provides a crowdsourced mobile testing platform (Baidu MTC) that distributes automated test plugins to real users, collects feedback, and reduces risk for new releases.

Overall, the combination of systematic case management, keyword‑driven automation, and CI pipelines dramatically improves testing efficiency and product quality for mobile map clients.