HTTP interface test method and apparatus

Abstract

The invention discloses an HTTP interface test method and apparatus. A specific embodiment of the method comprises the steps of obtaining a test case input by a user and aiming at a to-be-tested HTTPinterface; taking a first test step in the test case as a current test step, and executing the following HTTP interface test steps of packaging test operation and test data of the current test step into an HTTP test request package and sending the HTTP test request package to the to-be-tested HTTP interface; judging whether response data returned by the to-be-tested HTTP interface is the same as expected result data of the current test step or not, and if the response data is different from the expected result data, generating a test failure result; if the response data is the same as the expected result data, further judging whether the current test step is a final step of the test case or not, and if yes, generating a test success result; and if not, taking the next test step as the current test step, and continuing to execute the HTTP interface test steps. According to the method and the apparatus, the HTTP interface test efficiency is improved.

Description

technical field [0001] The present application relates to the field of computer technology, in particular to the field of Internet technology, and in particular to a method and device for testing an HTTP interface. Background technique [0002] At present, the commonly used solution for web page automation testing is to open the web page through a test tool (for example, Selenuim), wait for the page elements of the specified operation to be loaded, and then perform simulated user behavior operations (for example, access, input, click, file selection, etc.), Obtain page elements through the operation results and judge the operation results to finally determine whether the test case is successful. [0003] However, there are the following problems in simulating browser operations through testing tools: (1) No matter whether it is opened silently in memory or opened by calling the user interface, there will be loading efficiency problems due to waiting for a certain script code...

AI Technical Summary

Problems solved by technology

[0003] However, there are the following problems in simulating browser operations through testing tools: (1) No matter whether it is opened silently in memory or opened by calling the user interface, there will be loading efficiency problems due to waiting for a certain script code on the page to execute; (2) for some Page element changes require frequent maintenance of test scripts, which increases test costs; (3) the cost of developing scripts is high, and page elements need to be analyzed; (4) the modularization effect is poor, because the test tool is automated based on page elements, so calling modules must also Page elements must be loaded before they can be used, which is inefficient in use or maintenance

For HTTP interface verification, the previous page operations are meaningless

Images