Service component test method and device

Abstract

Embodiments of the invention provide a service component test method and device, and aim at reducing service component test cost and achieving better test effect. In the first aspect, the service component test method comprises the following steps of: requesting service component information and service method information from a server; generating a contract parameter information request accordingto a service component name and a service method name selected by a user and sending the contract parameter information request to the server; generating contract test information according to contract parameter information returned by the server and sending the contract test information to the server; and receiving a test result returned by the server after calling a service method of a corresponding service component according to the contract test information.

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. and many more. 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 re...

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