Architecture Overview of the RunnerGo Testing Platform

RunnerGo, as a testing platform, supports interface debugging, interface automation, and interface performance testing. Because it is an online platform, it has a corresponding architecture design. The original intention is multi‑faceted, and during design and development it underwent many changes, finally settling on the current architecture. Of course, this may not be the optimal architecture, but it is the best fit for the current stage.

Architecture diagram:

Process design:

Service introduction:

rg‑management service: mainly provides user management, interfaces, scenarios, plans, reports, machines, as well as report aggregation, distributed intelligent algorithms and other functions.

rg‑engine service: the pressure‑testing engine, primarily responsible for sending interface requests and recording test data.

rg‑collector service: mainly consumes Kafka messages (test data) and processes the data.

Front‑end service: mainly used for display, verification and interaction with users.

Middleware introduction:

Redis: stores temporary data such as report status, machine status, temporary report data, and other transient changes.

MySQL: stores plan lists, operation logs, report lists, user information, team information, scheduled task configurations, scenario configurations, etc.

MongoDB: stores reports, logs, log statuses and other unstructured data.

OSS/Local service: stores avatars, test files and similar assets.

Kafka: serves as the message channel for test data.

Nginx: provides load balancing.