Boosting API Test Efficiency with Scenario‑Based Apollo Framework

1. Why Develop Scenario‑Based Testing

Apollo framework introduction: a multi‑function interface testing framework for the KuJiaLe business system.

As the company rapidly expands, higher quality demands exceed the capabilities of the previous framework, necessitating an upgrade.

2. Desired Changes

Improve productivity and interface yield by focusing on two aspects:

Simplicity – easy for anyone to use.

Focus on interface quality.

2.1 Simplicity

Reduced case entry cost: Apollo Repo compatibility allows seamless migration and reuse of existing cases.

Reduced case authoring cost: Template demos enable one‑click copy and minor modifications.

Reduced case maintenance cost: "No‑code" style case creation with simple inputs preserves Apollo framework style.

2.2 Focus on Interface Quality

Scenario support: multiple interfaces combine to form a test case scenario.

More validation methods: various assertions, diff functions, and multi‑interface combination checks.

Special support for underlying services such as mesh and dcsmesh.

3. Platform Composition

The platform consists of three parts: environment management, category management, and test case management.

3.1 Environment Management

3.2 Category Management

Supports creating up to two‑level categories for organizing test cases.

3.3 Test Case Management

The page handles test case creation, import, and execution. The design avoids custom scripts to maximize efficiency and maintainability.

4. Design and Implementation

4.1 Link Design

Integrated with all company platforms to form a closed loop.

4.2 Code Development

Introduced pre‑case and scenario handling to connect upstream and downstream interfaces.

Implemented a response processing engine for special handling of different return types.

4.3 Feature Support

Request Parameter Support

Partial parameter display; see the detailed introduction article for full list.

Common Function Support

Six built‑in functions address specific business needs.

4.4 Results Showcase

Automated Bug Discovery

H2 automated bug discovery rate steadily improves.

5. Advanced Capability – Traffic Replay Support

5.1 Product Design

5.2 Product Implementation

Based on application name, the system identifies uncovered interfaces for precise coverage.

Recorded traffic generates interface test cases.

6. Planning and Outlook

The platform now covers most custom and hard‑decoration interfaces and some smart‑design projects; the most challenging business lines are fully supported, with remaining lines pending rollout.

Its core philosophy is to maximize case writing efficiency and automated discovery rate, a goal that is both simple in concept and challenging in execution.

Future work focuses on:

Improving case writing efficiency

Deeply investigate pain points across business lines to provide precise development support; each repo is analyzed for full coverage.

Improving automated discovery rate

Achieving high‑stability, high‑efficiency bug detection requires both powerful tools and disciplined methodology, which will be encapsulated and promoted.