Interface automatic test method and device, computer equipment and storage medium

Abstract

The invention relates to an automatic interface testing method and device, computer equipment and a storage medium.The method comprises the steps of obtaining input parameter information related to all to-be-tested interfaces from a specified database, and generating an interface test script according to the input parameter information related to all the to-be-tested interfaces; executing the interface test script to call all to-be-tested interfaces; and obtaining all the return messages received after calling all the to-be-tested interfaces, and performing test result analysis according to all the received return messages to obtain test results of all the to-be-tested interfaces. The embodiment of the invention can adapt to the automatic test of the current quick iterative version, and can quickly and accurately call the existing query interface to realize the quick coverage of the service main process when an emergency version, particularly a new version required to be published forbottom layer code transformation or upgrading, is involved.

Description

technical field [0001] The present application relates to the technical field of interface testing, in particular to an interface automatic testing method, device, computer equipment and storage medium. Background technique [0002] When it comes to urgent versions, especially when the underlying code transformation or upgrade requires the release of a new version, it is necessary to quickly and accurately cover the distributed remote call (RPC) service that needs to be called in the test, so as to analyze the impact of the changes of the new version on the existing interface influences. [0003] From the perspective of the existing automation implementation of the middle-end order query interface, the existing query interface SAT automation (SAT full name: Suning Automation Tester, which is an automated testing tool independently developed by Suning) starts from the upstream order receiving link, according to The types of orders are different, different variables (constant...

AI Technical Summary

Problems solved by technology

[0004] The above-mentioned implementation method is relatively complicated, there are many shared files, and there are many conflicts, which makes the maintenance cost of testers relatively high, and the link is relatively long, and the execution time of each test case is long, which cannot adapt to the current rapid iteration version. Automated testing, when it comes to emergency versions, especially when the underlying code transformation or upgrade needs to release a new version, cannot meet the needs of quickly and accurately calling the existing query interface to achieve rapid coverage of the main business process, and if there is a query in the test The interface is not covered, and there may be situations like circular reference ($ref) that make the front end unrecognizable

Images