Method and apparatus for testing service components

Abstract

Embodiments of the present invention provide a method and device for testing a service component, which can reduce the test cost of the service component and achieve better test results. According to the first aspect of an embodiment of the present invention, a method for testing a service component is provided, including: requesting service component information and service method information from the server; generating contract parameters according to the service component name and service method name selected by the user request information and send it to the server; generate contract test information and send it to the server according to the contract parameter information returned by the server; receive the service of calling the corresponding service component from the server according to the contract test information The test result returned after the method.

Description

technical field [0001] The invention relates to the field of computer technology, in particular to a method and device for testing service components. Background technique [0002] In a large-scale web system, the system provides or relies on different types of service components. Service components refer to a collection of codes with certain service functions, such as querying user order information, querying product price information, sending messages, and exporting report data. etc. In these scenarios, service components need to be testable, so as to keep abreast of the runtime status and runtime results of the service. [0003] In the prior art, when testing a service component, it is necessary to develop a corresponding HTTP interface for the specific service method of the service component to be tested in the web system, and call the service method of the service component through the HTTP interface service to perform the test. [0004] In the process of realizing th...

AI Technical Summary

Problems solved by technology

[0004] In the process of realizing the present invention, the inventor found that there are at least the following problems in the prior art: (1) There are many open frameworks of the existing web system, and different open frameworks require developers to provide HTTP interfaces of corresponding technologies. Components can be tested, and related codes required for testing need to be developed; when there are a large number of service components and each service component contains several service methods, because the existing technology test scheme is not universal, it will bring a huge workload, adding The Burden of Big App Developers

(2) On the other hand, in the prior art, when sending parameters for testing, the parameters are directly passed in the URL. During the process of passing parameters, URL encoding is required to prevent garbled characters, and special characters need to be escaped, especially for nested It is very inconvenient to manually compile parameters; in addition, all parameters are manually input during testing, and the caller must know the format information of the parameters, which brings great difficulties to the test

Images