How Tencent Scaled Mini‑Program Development with Cloud‑Native DevOps and Serverless

1. Business Background

Tencent Online Education includes three main products: Tencent Classroom for adult learning, Penguin Tutor for K12 education, and ABCmouse for children's English learning.

All three businesses have mini‑programs deployed on various client platforms.

2. Mini‑Program Engineering Practice

Because many features are developed in parallel, the team faced problems such as inconsistent development environments, missing npm build steps, QR‑code preview expiration, and accidental code leakage during release.

Missing npm build before publishing can cause outdated dependencies.

QR‑code preview has limited validity, especially with multiple concurrent features.

Release steps lack visibility, leading to accidental code inclusion.

To address these issues, a DevOps workflow was built, covering build, test, release and collaboration.

A custom CLI tool Imweapp was created on top of the WeChat Developer Tool’s CLI, providing branch‑merge checks, npm‑package validation, automated versioning and upload.

Automated testing includes UI testing with miniprogram-automator and jest, and unit testing with miniprogram-simulate and jest. Common pitfalls such as component name prefixes, asynchronous UI actions, native component inspection, and API mocking are listed.

3. Mini‑Program Cloud Development Practice

To overcome limitations of the built‑in SDK, the team adopted Serverless cloud functions and a custom Web SDK to share backend resources across multiple mini‑programs and web clients.

Serverless functions are triggered by API Gateway; cold‑start latency is reduced by pre‑initialising resources, using VPC networking, and splitting heavy controllers into separate functions.

The team integrated the Serverless‑plus package with their Koa‑based framework IMServer, creating imserve-serverless for easy Serverless development.

Deployment is managed via the Cloud Development CLI, which standardises build environments, supports Git‑hook triggered deployments to test, pre‑release and production environments, and archives code for rollback.

Overall, the solution unifies mini‑program CI/CD, automated testing, Serverless migration and cloud‑function deployment, improving reliability and scalability across dozens of teams and over thirty mini‑programs.