CN112527656A - Websocket interface test method, device and equipment - Google Patents
Websocket interface test method, device and equipment Download PDFInfo
- Publication number
- CN112527656A CN112527656A CN202011496474.1A CN202011496474A CN112527656A CN 112527656 A CN112527656 A CN 112527656A CN 202011496474 A CN202011496474 A CN 202011496474A CN 112527656 A CN112527656 A CN 112527656A
- Authority
- CN
- China
- Prior art keywords
- websocket
- websocket interface
- interface
- container
- service container
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000010998 test method Methods 0.000 title claims abstract description 27
- 238000012360 testing method Methods 0.000 claims description 85
- 238000000034 method Methods 0.000 claims description 22
- 230000004083 survival effect Effects 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 9
- 230000002159 abnormal effect Effects 0.000 claims description 7
- 230000036541 health Effects 0.000 claims description 7
- 230000003993 interaction Effects 0.000 claims description 7
- 238000012545 processing Methods 0.000 description 9
- 238000011161 development Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002085 persistent effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a test method, a device, equipment and a computer readable storage medium of a WebSocket interface.
Description
Technical Field
The invention relates to the technical field of interface testing, in particular to a testing method, a testing device, testing equipment and a computer readable storage medium for a WebSocket interface.
Background
The hypertext transfer protocol (HTTP protocol) communication can only be that a client sends a request to a server, and the server returns a query result. The HTTP protocol does not make it possible for the server to actively push information to the client. In the early days, many websites adopted a polling scheme to implement the push technology, i.e. at a specific time interval (e.g. every second), the browser sends out an HTTP request to the server, and then the server returns the latest data to the browser of the client. This conventional model has the obvious disadvantage that the browser needs to send requests to the server continuously, however HTTP requests may contain a long header, where the really valid data may be only a small part, which obviously consumes a lot of bandwidth resources. In this case, HTML5 defines a WebSocket protocol, which can better save server resources and bandwidth, and can perform communication in real time. The WebSocket technology has been widely applied in the current Web era with high performance requirements and high user experience.
The WebSocket protocol is a protocol for full-duplex communication over a single TCP connection, so that data exchange between a client and a server is simpler, and the server is allowed to actively push data to the client. In an Application Program Interface (API) of WebSocket, a browser and a server only need to complete one handshake, and persistent connection can be directly established between the browser and the server, and bidirectional data transmission is carried out.
In view of the gradually wide application of the WebSocket in the field of Web development, a test for a WebSocket interface is particularly important. In the development process, a mode that the front end and the background independently develop becomes a primary type selection mode in the industry. After the front end is developed, data are acquired from the background through the interface and are used for testing and evaluating products of the front end. If the development work at the background is not finished, the front end cannot acquire data through the interface for testing, so that the development work progress of the front end is greatly limited, and the joint debugging efficiency of the interface is low.
Because the existing Mock platform for WebSocket cannot provide WebSocket service in the development process, in order to accelerate the front-end development work progress, a front-end developer can only skip a link connected with the service and hard code some test data related to a WebSocket interface, and the test mode for the WebSocket interface not only aggravates the work of the front-end developer, but also often cannot accurately reflect the actual situation of the WebSocket interface due to the coded test data.
Disclosure of Invention
The invention aims to provide a test method, a test device, test equipment and a computer readable storage medium for a WebSocket interface, which are convenient for front-end developers to test the WebSocket interface by simulating real WebSocket interface service and improve the accuracy of test results.
In order to solve the technical problem, the invention provides a test method of a WebSocket interface, which comprises the following steps:
acquiring WebSocket interface configuration;
calling a container definition file, and generating a WebSocket interface service container according to the WebSocket interface configuration;
sending the information of the WebSocket interface service container to a front-end processor;
and generating a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor, so that a front-end developer can utilize the WebSocket test case container to perform WebSocket interface test.
Optionally, the obtaining of the WebSocket interface configuration specifically includes:
and receiving WebSocket interface configuration input on the human-computer interaction interface.
Optionally, the calling the container definition file and generating the WebSocket interface service container according to the WebSocket interface configuration specifically include:
converting the WebSocket interface configuration into a code version of a server corresponding to the front-end processor to obtain the converted WebSocket interface configuration;
and calling the container definition file, and generating the WebSocket interface service container according to the converted WebSocket interface configuration.
Optionally, the type of the WebSocket interface configuration specifically includes: at least one of a protocol type, an interface uniform resource locator, a push frequency, a custom event name, data corresponding to the custom event name, a format of returned data, push content, and a container lifetime.
Optionally, the information of the WebSocket interface service container specifically includes: state information of the WebSocket interface service container and a port number of the WebSocket interface service container.
Optionally, the generating a WebSocket test case container according to the configuration of the front-end processor on the WebSocket interface service container specifically includes:
and receiving interface joint debugging and interface configuration of the WebSocket interface service container performed by a front-end developer based on the front-end processor, and generating a WebSocket test case container.
Optionally, the method further includes:
detecting the survival time of the WebSocket interface service container and the health state of the WebSocket interface service container;
if the survival time limit of the WebSocket interface service container exceeds the default survival time limit of the WebSocket interface service container, destroying the WebSocket interface service container;
and if the health state of the WebSocket interface service container is abnormal, sending an abnormal prompt.
In order to solve the above technical problem, the present invention further provides a testing apparatus for a WebSocket interface, including:
the acquisition unit is used for acquiring WebSocket interface configuration;
the generating unit is used for calling the container definition file and generating a WebSocket interface service container according to the WebSocket interface configuration;
the sending unit is used for sending the information of the WebSocket interface service container to a front-end processor;
and the configuration unit is used for generating a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor, so that a front-end developer can utilize the WebSocket test case container to perform WebSocket interface test.
In order to solve the above technical problem, the present invention further provides a test apparatus for a WebSocket interface, including:
the memory is used for storing instructions, and the instructions comprise the steps of the test method of the WebSocket interface;
a processor to execute the instructions.
In order to solve the above technical problem, the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the test method for the WebSocket interface as described in any one of the above.
The WebSocket interface testing method provided by the invention comprises the steps of firstly obtaining WebSocket interface configuration, calling a container definition file, generating a WebSocket interface service container according to the WebSocket interface configuration, then sending information of the WebSocket interface service container to a front-end processor, and generating a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor, so that a front-end developer can utilize the WebSocket test case container to carry out WebSocket interface testing. The WebSocket interface test method provided by the invention creates the WebSocket test service case in a container mode, does not need a front-end developer to encode test data related to the WebSocket interface, can be taken at any time and highly configurable, can simulate real and independent WebSocket service for the front-end developer, is convenient to cover various test cases of the WebSocket interface in the front-end development process, and improves the accuracy of the test result of the WebSocket interface.
The invention also provides a testing device, equipment and a computer readable storage medium of the WebSocket interface, which have the beneficial effects and are not described again.
Drawings
In order to more clearly illustrate the embodiments or technical solutions of the present invention, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
Fig. 1 is a flowchart of a testing method for a WebSocket interface according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a testing apparatus of a WebSocket interface according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a test device of a WebSocket interface according to an embodiment of the present invention.
Detailed Description
The core of the invention is to provide a test method, a device, equipment and a computer readable storage medium of a WebSocket interface, which are convenient for front-end developers to test the WebSocket interface by simulating real WebSocket interface service.
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a flowchart of a testing method for a WebSocket interface according to an embodiment of the present invention.
As shown in fig. 1, the test method for the WebSocket interface provided in the embodiment of the present invention includes:
s101: and acquiring the WebSocket interface configuration.
S102: and calling the container definition file, and generating a WebSocket interface service container according to the WebSocket interface configuration.
S103: and sending the information of the WebSocket interface service container to the front-end processor.
S104: and generating a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor, so that a front-end developer can perform WebSocket interface test by using the WebSocket test case container.
The existing test scheme of the WebSocket interface is difficult to accurately simulate on a service end layer, if no WebSocket interface service exists, a front-end developer can only skip a service connection link and hard code some test data, the method is low in efficiency and inaccurate, and the test method of the WebSocket interface provided by the embodiment of the invention creates a real WebSocket service container for debugging and using of the front-end developer, so that the use experience same as that of back-end joint debugging is achieved.
In specific implementation, the test method of the WebSocket interface provided by the embodiment of the present invention can be implemented by programming based on a Web platform (usually, a Mock platform). Through the test method of the WebSocket interface provided by the embodiment, a WebSocket Mock service for debugging can be provided for a front-end developer.
For step S101, a preset default WebSocket interface configuration may be obtained, or a human-computer interaction interface may be provided in advance for a developer, an option or an input box related to the WebSocket interface configuration is provided on the human-computer interaction interface, and the WebSocket interface configuration input on the human-computer interaction interface is received. The WebSocket interface configuration type may specifically include: at least one of a protocol type, an interface uniform resource locator, a push frequency, a custom event name, data corresponding to the custom event name, a format of the returned data, push content, and a container lifetime. Through the customization of more types of WebSocket interface configurations, more configuration choices can be provided for front-end developers, the coverage rate of WebSocket interface test cases is improved, and the debugging process of the front-end developers on WebSocket services is simplified.
For step S102, the container definition file Dockerfile is called to generate a WebSocket interface service container according to the WebSocket interface configuration.
If the WebSocket interface configuration input by the staff is received based on the human-computer interaction interface, the WebSocket interface configuration needs to be converted into a code version of the server, such as a code of a node. Therefore, step S102 may include:
converting the WebSocket interface configuration into a code version of a server corresponding to the front-end processor to obtain the converted WebSocket interface configuration;
and calling the container definition file, and generating a WebSocket interface service container according to the converted WebSocket interface configuration.
For step S103, the information of the WebSocket interface service container is sent to the front-end processor, so that the front-end developer establishes a connection with the WebSocket interface service container. The information of the WebSocket interface service container may specifically include: state information of the WebSocket interface service container and a port number of the WebSocket interface service container. And the state and the exposed port number of the WebSocket interface service container are obtained through interaction with a container definition file of the configured WebSocket interface service container and are presented to the front-end processor.
For step S104, generating a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor, which may specifically include:
and receiving interface joint debugging and interface configuration of a WebSocket interface service container performed by a front-end developer based on a front-end processor, and generating a WebSocket test case container.
Based on the front-end processor, a front-end developer performs interface joint debugging according to the information of the WebSocket interface service container, such as 'ws:// 192.168.1.128: 8080'. It is the WebSocket service client that can communicate with any server, the "ws" protocol identifier (wss if encrypted), and the address of the request is the Application Programming Interface (API) that the backend supports WebSocket.
After the interface joint debugging is completed, the front-end developer can modify the configuration of the WebSocket interface service container, restart the WebSocket interface service container or destroy the WebSocket interface service container based on the front-end processor. After the configuration of the WebSocket interface service container is modified, a front-end developer can immediately take effect by clicking the 'restart simulation case container', and the WebSocket test case container is obtained. On the basis, a front-end developer can generate different test cases (namely WebSocket test case containers) through different configurations of the WebSocket interface service containers, so that the effect of covering more WebSocket interface test cases is achieved.
The WebSocket interface testing method provided by the embodiment of the invention comprises the steps of firstly obtaining WebSocket interface configuration, calling a container definition file, generating a WebSocket interface service container according to the WebSocket interface configuration, then sending information of the WebSocket interface service container to a front-end processor, and generating a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor, so that a front-end developer can utilize the WebSocket test case container to carry out WebSocket interface testing. The WebSocket interface test method provided by the invention creates the WebSocket test service case in a container mode, does not need a front-end developer to encode test data related to the WebSocket interface, can be taken at any time and highly configurable, can simulate real and independent WebSocket service for the front-end developer, is convenient to cover various test cases of the WebSocket interface in the front-end development process, and improves the accuracy of the test result of the WebSocket interface.
On the basis of the above embodiment, the test method for the WebSocket interface provided by the embodiment of the present invention may further include:
detecting the survival time of the WebSocket interface service container and the health state of the WebSocket interface service container;
if the survival time limit of the WebSocket interface service container exceeds the default survival time limit of the WebSocket interface service container, destroying the WebSocket interface service container;
and if the health state of the WebSocket interface service container is abnormal, sending an abnormal prompt.
By setting the default survival time limit for the WebSocket interface service container, the situation that a useless WebSocket interface service container occupies a system space for a long time is avoided. When the WebSocket interface service container is generated, generating a corresponding timing task to count the survival time of the WebSocket interface service container and automatically destroying the WebSocket interface service container when the survival time of the WebSocket interface service container reaches the default survival time.
Meanwhile, after the WebSocket interface service container is generated, the health state of the WebSocket interface service container is monitored in real time, and developers are reminded of the abnormal situation of the WebSocket interface service container in real time.
On the basis of the above detailed description of the embodiments corresponding to the test method of the WebSocket interface, the invention also discloses a test device, equipment and a computer readable storage medium of the WebSocket interface corresponding to the method.
Fig. 2 is a schematic structural diagram of a testing apparatus of a WebSocket interface according to an embodiment of the present invention.
As shown in fig. 2, the test apparatus for a WebSocket interface provided in the embodiment of the present invention includes:
an obtaining unit 201, configured to obtain a WebSocket interface configuration;
the generating unit 202 is configured to invoke a container definition file and generate a WebSocket interface service container according to WebSocket interface configuration;
a sending unit 203, configured to send information of the WebSocket interface service container to the front-end processor;
the configuration unit 204 is configured to generate a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor, so that a front-end developer performs a WebSocket interface test by using the WebSocket test case container.
Since the embodiments of the apparatus portion and the method portion correspond to each other, please refer to the description of the embodiments of the method portion for the embodiments of the apparatus portion, which is not repeated here.
Fig. 3 is a schematic structural diagram of a test device of a WebSocket interface according to an embodiment of the present invention.
As shown in fig. 3, the test device for the WebSocket interface provided in the embodiment of the present invention includes:
a memory 310, configured to store instructions, where the instructions include steps of a test method of a WebSocket interface according to any one of the above embodiments;
a processor 320 for executing the instructions.
Processor 320 may include one or more processing cores, such as a 3-core processor, an 8-core processor, and so forth. The processor 320 may be implemented in at least one hardware form of a digital Signal processing (dsp), a Field-Programmable Gate Array (FPGA), a Programmable Logic Array (pla), or a digital Signal processing (dsp). The processor 320 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a central Processing unit (cpu); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 320 may be integrated with an image processor GPU (graphics Processing unit), which is responsible for rendering and drawing the content that the display screen needs to display. In some embodiments, processor 320 may also include an Artificial Intelligence (AI) (artificial intelligence) processor for processing computational operations related to machine learning.
Memory 310 may include one or more computer-readable storage media, which may be non-transitory. Memory 310 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 310 is at least used for storing a computer program 311, where after the computer program 311 is loaded and executed by the processor 320, relevant steps in the test method for the WebSocket interface disclosed in any one of the foregoing embodiments can be implemented. In addition, the resources stored by the memory 310 may also include an operating system 312, data 313, and the like, and the storage may be transient storage or persistent storage. The operating system 312 may be Windows, among others. Data 313 may include, but is not limited to, data involved in the above-described methods.
In some embodiments, the test equipment of the WebSocket interface may further include a display 330, a power supply 340, a communication interface 350, an input-output interface 360, a sensor 370, and a communication bus 380.
Those skilled in the art will appreciate that the architecture shown in fig. 3 does not constitute a limitation of the test equipment of the WebSocket interface and may include more or fewer components than those shown.
The test device for the WebSocket interface provided by the embodiment of the application comprises the memory and the processor, and the processor can realize the test method for the WebSocket interface when executing the program stored in the memory, and the effect is the same as that of the test method for the WebSocket interface.
It should be noted that the above-described embodiments of the apparatus and device are merely illustrative, for example, the division of modules is only one division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form. Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and performs all or part of the steps of the methods according to the embodiments of the present invention, or all or part of the technical solution.
To this end, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the steps of the test method such as the WebSocket interface.
The computer-readable storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory ROM (Read-Only Memory), a random Access Memory ram (random Access Memory), a magnetic disk, or an optical disk.
The computer program contained in the computer-readable storage medium provided in this embodiment can implement the steps of the test method for the WebSocket interface described above when executed by the processor, and the effect is the same as above.
The test method, the test device, the test equipment and the computer readable storage medium of the WebSocket interface provided by the invention are described in detail above. The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device, the apparatus and the computer-readable storage medium disclosed in the embodiments correspond to the method disclosed in the embodiments, so that the description is simple, and the relevant points can be referred to the description of the method. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A test method of a WebSocket interface is characterized by comprising the following steps:
acquiring WebSocket interface configuration;
calling a container definition file, and generating a WebSocket interface service container according to the WebSocket interface configuration;
sending the information of the WebSocket interface service container to a front-end processor;
and generating a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor, so that a front-end developer can utilize the WebSocket test case container to perform WebSocket interface test.
2. The test method according to claim 1, wherein the obtaining of the WebSocket interface configuration specifically comprises:
and receiving WebSocket interface configuration input on the human-computer interaction interface.
3. The testing method according to claim 2, wherein the invoking of the container definition file generates a WebSocket interface service container according to the WebSocket interface configuration, and specifically includes:
converting the WebSocket interface configuration into a code version of a server corresponding to the front-end processor to obtain the converted WebSocket interface configuration;
and calling the container definition file, and generating the WebSocket interface service container according to the converted WebSocket interface configuration.
4. The testing method of claim 1, wherein the type of the WebSocket interface configuration specifically includes: at least one of a protocol type, an interface uniform resource locator, a push frequency, a custom event name, data corresponding to the custom event name, a format of returned data, push content, and a container lifetime.
5. The testing method of claim 1, wherein the information of the WebSocket interface service container specifically includes: state information of the WebSocket interface service container and a port number of the WebSocket interface service container.
6. The method according to claim 1, wherein the generating a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor specifically includes:
and receiving interface joint debugging and interface configuration of the WebSocket interface service container performed by a front-end developer based on the front-end processor, and generating a WebSocket test case container.
7. The test method of claim 1, further comprising:
detecting the survival time of the WebSocket interface service container and the health state of the WebSocket interface service container;
if the survival time limit of the WebSocket interface service container exceeds the default survival time limit of the WebSocket interface service container, destroying the WebSocket interface service container;
and if the health state of the WebSocket interface service container is abnormal, sending an abnormal prompt.
8. A testing device of a WebSocket interface is characterized by comprising:
the acquisition unit is used for acquiring WebSocket interface configuration;
the generating unit is used for calling the container definition file and generating a WebSocket interface service container according to the WebSocket interface configuration;
the sending unit is used for sending the information of the WebSocket interface service container to a front-end processor;
and the configuration unit is used for generating a WebSocket test case container according to the configuration of the WebSocket interface service container by the front-end processor, so that a front-end developer can utilize the WebSocket test case container to perform WebSocket interface test.
9. A test device of a WebSocket interface is characterized by comprising:
a memory for storing instructions, the instructions comprising the steps of the test method of the WebSocket interface of any one of claims 1 to 7;
a processor to execute the instructions.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method for testing a WebSocket interface according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011496474.1A CN112527656A (en) | 2020-12-17 | 2020-12-17 | Websocket interface test method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011496474.1A CN112527656A (en) | 2020-12-17 | 2020-12-17 | Websocket interface test method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112527656A true CN112527656A (en) | 2021-03-19 |
Family
ID=75001124
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011496474.1A Pending CN112527656A (en) | 2020-12-17 | 2020-12-17 | Websocket interface test method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112527656A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114978869A (en) * | 2022-07-15 | 2022-08-30 | 数研院(福建)信息产业发展有限公司 | Configurable interface state automatic judgment method and system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108200170A (en) * | 2018-01-02 | 2018-06-22 | 武汉斗鱼网络科技有限公司 | Message treatment method, device and readable storage medium storing program for executing |
| CN109614310A (en) * | 2018-10-22 | 2019-04-12 | 中国平安财产保险股份有限公司 | Management method, device, computer equipment and the storage medium of test interface |
| CN109918310A (en) * | 2019-03-15 | 2019-06-21 | 集奥聚合(北京)人工智能科技有限公司 | A kind of Modeling Platform interface test method |
| CN111159049A (en) * | 2019-12-31 | 2020-05-15 | 中国银行股份有限公司 | Automatic interface testing method and system |
| CN111290936A (en) * | 2018-12-07 | 2020-06-16 | 北京奇虎科技有限公司 | Interface testing method and device |
| CN111444088A (en) * | 2020-03-11 | 2020-07-24 | 广州虎牙科技有限公司 | Test case calling method and device for interface test |
| US10824544B1 (en) * | 2018-11-28 | 2020-11-03 | Intuit Inc. | Generating test data as a service for use in testing software during software development |
-
2020
- 2020-12-17 CN CN202011496474.1A patent/CN112527656A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108200170A (en) * | 2018-01-02 | 2018-06-22 | 武汉斗鱼网络科技有限公司 | Message treatment method, device and readable storage medium storing program for executing |
| CN109614310A (en) * | 2018-10-22 | 2019-04-12 | 中国平安财产保险股份有限公司 | Management method, device, computer equipment and the storage medium of test interface |
| US10824544B1 (en) * | 2018-11-28 | 2020-11-03 | Intuit Inc. | Generating test data as a service for use in testing software during software development |
| CN111290936A (en) * | 2018-12-07 | 2020-06-16 | 北京奇虎科技有限公司 | Interface testing method and device |
| CN109918310A (en) * | 2019-03-15 | 2019-06-21 | 集奥聚合(北京)人工智能科技有限公司 | A kind of Modeling Platform interface test method |
| CN111159049A (en) * | 2019-12-31 | 2020-05-15 | 中国银行股份有限公司 | Automatic interface testing method and system |
| CN111444088A (en) * | 2020-03-11 | 2020-07-24 | 广州虎牙科技有限公司 | Test case calling method and device for interface test |
Non-Patent Citations (4)
| Title |
|---|
| DICYT: "Docker 容器健康检查机制", 《HTTPS://BLOG.CSDN.NET/DICYT/ARTICLE/DETAILS/77775219》 * |
| NEI: "使用 NEI 实现接口Mock服务", 《HTTPS://WWW.BOOKSTACK.CN/READ/NEI-TOOLKIT/DOC-使用NEI进行前后端并行开发.MD》 * |
| ZHUGEAMING2018: "『中级篇』docker体验阿里云的容器服务", 《HTTPS://BLOG.CSDN.NET/ZHUGEAMING2018/ARTICLE/DETAILS/82710424》 * |
| 田想兵: "模拟websocket推送消息服务mock工具二", 《HTTPS://WWW.CNBLOGS.COM/TIANXIANGBING/P/MOCK-WEBSOCKET.HTML》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114978869A (en) * | 2022-07-15 | 2022-08-30 | 数研院(福建)信息产业发展有限公司 | Configurable interface state automatic judgment method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200242020A1 (en) | Mock server for testing | |
| CN110198247B (en) | Interface test method and system | |
| CN103942225B (en) | A kind of resource transfer method, client and the system of mixed type applications client | |
| CN105677452B (en) | Task processing method and device for task platform | |
| CN106648556B (en) | Method and device for front-end and back-end integrated development test | |
| CN110224896B (en) | Network performance data acquisition method and device and storage medium | |
| CN104821954A (en) | Cross-platform remote procedure call method | |
| CN111274512A (en) | Page loading method, device and medium | |
| CN106484459B (en) | Flow control method and device applied to JavaScript | |
| CN111352836A (en) | Pressure testing method and related device | |
| CN111026634A (en) | Interface automation test system, method, device and storage medium | |
| CN112732572A (en) | Service testing method, device and system, storage medium and electronic device | |
| CN110598135A (en) | Network request processing method and device, computer readable medium and electronic equipment | |
| CN112729868A (en) | Vehicle diagnosis method, device, equipment and medium | |
| CN109725887B (en) | Data interaction method and device based on message research and development framework and terminal equipment | |
| CN108694120B (en) | Method and device for testing service component | |
| CN111767229A (en) | Performance test method, device and equipment | |
| CN106708717B (en) | A kind of exploitation adjustment method and device | |
| CN112527656A (en) | Websocket interface test method, device and equipment | |
| CN107395663B (en) | Data acquisition method and device | |
| CN104796929B (en) | Network debugging method and device | |
| CN112073488A (en) | Method and device for processing request | |
| CN111124924A (en) | API (application program interface) deployment method and device, electronic equipment and storage medium | |
| CN110874278A (en) | Embedding method of external system, workflow system, device and storage medium | |
| CN113672225B (en) | User interface processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210319 |
|
| RJ01 | Rejection of invention patent application after publication |