Platform for Managing and Executing Interface Test Cases

In continuous business testing, interface test cases accumulate and need efficient management and execution; the platform addresses this by classifying cases by business scenario and type, providing visual execution and reducing both management and execution costs.

Platform Introduction

1. New Project : Configure a test case project with a descriptive name and specify the test code path for @Test methods.

2. Update Nodes : Parse TestNG @Test methods to display a tree of package, class, method names and descriptions.

3. Add Test Cases : Aggregate multiple interface cases into a test set, similar to TestNG groups, e.g., by requirement, interface, or regression category.

4. Execution Methods : Click to execute by providing the test environment IP, or schedule tasks to run at specific times or intervals for automated regression or monitoring.

5. Execution Results : After execution, a report shows the number of successful and failed cases, with detailed method names for each.

Technical Implementation

The case project manager downloads source code from a Git repository and compiles it; the node manager extracts package, class, and method information into a database, enabling generation of test sets (regression, smoke, requirement). Execution tasks can be run immediately or scheduled, with statuses such as success, failure, in‑progress, or partial success, and generate detailed reports.

Node Generation

Source code is downloaded, and scripts split interface test methods into package, class, and method nodes, storing them and their mappings in the database; new cases trigger node updates.

Execute Suite

Based on the nodes of a test set, a TestNG XML configuration is generated and executed, producing a report that records successful and failed methods.

Summary

The platform unifies the team's interface testing approach, lowers testing costs, enhances self‑testing capabilities for developers, and provides centralized test set management and scheduling.

Future expectations include reducing coding effort for scenario‑based testing through templates and components, integrating API documentation and test data, and offering diff, coverage, mock, and fault‑injection tools for a complete testing workflow.