How DevOps Accelerated Mobile Marketing Testing at Agricultural Bank

Background

With the rapid and diverse development of mobile applications, digital communication has become essential, and data‑driven marketing is gradually replacing traditional methods. The bank's mobile marketing platform "Financial Store" customizes stores for client managers, requiring fast response and timely delivery.

Practice Situation

To improve response speed and delivery capability, the project team adopted a DevOps model (DEV, QA, OPS) for unified product development management, enabling rapid, reliable, and secure iterations.

The integrated team collaborates across business, development, testing, and operations, sharing product lifecycle responsibility. The following outlines the testing work within DevOps.

Test Management

Testing is layered throughout the DevOps pipeline.

1. Development stage: after code is built with Maven, unit tests (JUnit), code compliance checks (JTest), and security checks (Checkmarx) run. If any fail, the pipeline stops and feedback is sent to developers.

2. Functional testing stage: after deployment to the test environment, automated API tests, UI automation, manual testing, and non‑functional tests (performance, security) are triggered.

3. Pre‑production stage: core interfaces are tested for validation.

A reasonable test‑layering strategy is key to quality. By shifting focus to unit and API tests, the team reduces reliance on slow, costly UI automation. Test case design is moved left in the pipeline, allowing earlier detection.

Automation is central to DevOps testing. The team uses the in‑house Automation Testing Platform (ATP) to design, execute, and analyze automated cases, with a data pool providing reliable, independent test data.

Metrics

Key metrics include test case execution rate, pass rate, average defects per case, automation rate, business scenario automation success rate, false‑positive rate, automation investment distribution, ATP automation efficiency, severe defect ratio, and defect fix rate.

Each metric is quantified to assess testing capability and quality; for example, false‑positive analysis identifies causes such as network instability or script failures, enabling targeted improvements.

Application Effects

After adopting DevOps, the mobile marketing team achieved a two‑week iteration cycle, enabling timely demand response and rapid product releases. Automated processes reduced human error, uncovered defects earlier, and ensured product quality and reliability. Continuous integration and delivery streamlined the entire product lifecycle, maximizing resource utilization.

Future Outlook

Facing shorter delivery cycles and faster deployment frequencies, testers must adapt. The team plans to expand automation coverage to achieve full test automation and integrate performance testing into the ATP pipeline for automated performance validation.

Projects Passing DevOps 3‑Level Assessment

Credit Middle‑Office Project

Personal Online Banking Project

Distributed Application Interconnection Platform (AIR) Project

Value‑Added Tax Input Management Project

Financial Store Project