Automated Interface Testing with ATP and Swagger Integration

The article uses a martial‑arts metaphor to present automated interface testing as a disciplined practice, highlighting the ATP (Automated Testing Platform) developed in‑house, which supports both UI and API automation.

It describes a four‑step process for using ATP: recording interface transaction formats, designing test cases with value extraction and checkpoints, creating execution batches, and analyzing results.

Three traditional ways to capture transaction formats are listed—using ATP’s recording template, transaction logs, or the internal ISmart standard interface documentation—each requiring manual effort and risking incomplete coverage.

By integrating ATP with Swagger, the platform can automatically retrieve and update transaction format information from Swagger’s descriptive files, eliminating manual entry and ensuring completeness.

Swagger provides a visual UI for viewing and testing interfaces, serving as a shared contract among developers, testers, and project managers.

ATP also supports various data‑assignment methods for test cases, such as pulling from a data pool, setting fixed values, establishing field relationships, and string concatenation; fixed‑value assignment is most frequently used.

When testers lack deep knowledge of input semantics, ATP can generate test cases directly from system logs, automatically populating input values and reducing the effort required for case design.

The integration dramatically lowers communication and labor costs, accelerates test case creation, and frees testers to focus on comprehensive path coverage and quality assurance.

The article concludes by thanking supporting departments and promising further sharing of testing techniques.