CN113590475B - Joint debugging test method and joint debugging test device of online development platform - Google Patents
Joint debugging test method and joint debugging test device of online development platform Download PDFInfo
- Publication number
- CN113590475B CN113590475B CN202110790880.7A CN202110790880A CN113590475B CN 113590475 B CN113590475 B CN 113590475B CN 202110790880 A CN202110790880 A CN 202110790880A CN 113590475 B CN113590475 B CN 113590475B
- Authority
- CN
- China
- Prior art keywords
- joint debugging
- task
- server
- address
- debugging
- 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.)
- Active
Links
- 238000011161 development Methods 0.000 title claims abstract description 90
- 238000012360 testing method Methods 0.000 title claims abstract description 38
- 238000010998 test method Methods 0.000 title claims abstract description 20
- 238000013500 data storage Methods 0.000 claims abstract description 38
- 238000000034 method Methods 0.000 claims abstract description 37
- 238000012545 processing Methods 0.000 claims description 33
- 238000004891 communication Methods 0.000 claims description 23
- 238000012544 monitoring process Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 11
- 230000000007 visual effect Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 10
- 238000002955 isolation Methods 0.000 description 10
- 238000006243 chemical reaction Methods 0.000 description 5
- 238000012800 visualization Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
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)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
Abstract
The technical scheme of the application provides a joint debugging test method of an online development platform, a joint debugging test device of the online development platform, a server and a storage medium. The joint debugging test method of the online development platform comprises the steps of obtaining Socket corresponding to a joint debugging task based on user ID identification of the joint debugging task and task ID identification allocation, wherein the Socket at least comprises an IP address and a port number of a server for receiving the joint debugging result; creating SocketSink connection based on Socket; socketSink the connection contains an IP address and port number indicating the path for storing the joint debugging result; and acquiring the joint debugging result through SocketSink connection, and storing the joint debugging result to a data storage area of a server for receiving the joint debugging result based on the IP address and the port number. Compared with the prior art, the method has the advantages that the joint debugging results are stored in the database, and then the client side checks the result data in the database in a visual tool or command line mode, so that the data feedback efficiency of the joint debugging results can be effectively improved, and the data checking flow and manpower resources are saved.
Description
Technical Field
The embodiment of the invention relates to the technical field of data processing, in particular to a joint debugging test method of an online development platform, a joint debugging test device of the online development platform, a server and a storage medium.
Background
In the big data age, data volume and day-time increase. Stream, batch computing engines are becoming increasingly popular in enterprise applications. However, the flow and batch computing projects are developed according to one requirement, the development time is long, the labor consumption is high, and the flow and batch computing platforms are born. Along with this, there is also debugging of the relevant computing tasks on the platform.
Disclosure of Invention
The embodiment of the invention provides a joint debugging test method of an online development platform, a joint debugging test device of the online development platform, a server and a storage medium.
The first aspect of the embodiments of the present disclosure provides a joint debugging method for an online development platform, which is applied to a server of the development platform, and includes:
acquiring a Socket corresponding to a joint debugging task based on a user ID (identity) of the joint debugging task and task ID (identity) allocation, wherein the Socket at least comprises an IP (Internet protocol) address and a port number of a server for receiving a joint debugging result;
Creating SocketSink connection based on the Socket; wherein the SocketSink connections include the IP address and port number indicating the path to store the joint debugging results;
And acquiring the joint debugging result in the debugging server through the SocketSink connection, and storing the joint debugging result to a data storage area of the server receiving the joint debugging result based on the IP address and the port number.
In one embodiment, the joint debugging method further comprises:
Sending the IP address and the port number to a client; the IP address is used for the client to establish communication connection with the server receiving the joint debugging result according to the IP address; and the port number and a port corresponding to the port number for the client to access acquire the joint debugging result stored in the data storage area.
In one embodiment, the method for testing the joint debugging includes, before the joint debugging result is obtained in the debugging server through the SocketSink connection:
Issuing a debugging instruction to a debugging server, wherein the debugging instruction at least comprises the joint debugging task and the IP address and port number corresponding to the joint debugging task, and the debugging instruction is used for enabling the debugging server to execute the joint debugging task according to the debugging instruction; the IP address and the port number are used for the development platform to determine the joint debugging result of the joint debugging task in a plurality of debugging servers.
In one embodiment, the joint debugging method further comprises:
monitoring the queried condition of the joint debugging result in real time;
if the joint debugging result is not queried within the preset time, closing the Socket.
In one embodiment, the method further comprises:
Acquiring source data to be debugged in a development platform file system;
The issuing of the debug instruction to the debug server includes:
and transmitting the source data to be debugged to the debugging server.
A second aspect of the embodiments of the present disclosure provides a joint debugging method of an online development platform, applied to a client, including:
receiving an IP address and a port number sent by the development platform;
establishing communication connection with a server receiving joint debugging results in the development platform based on the IP address;
And acquiring the joint debugging result stored in the server for receiving the joint debugging result based on the port corresponding to the port number.
A third aspect of the embodiments of the present disclosure provides a joint debugging device of an online development platform, which is applied to a server of the development platform, and includes:
The first processing unit is used for acquiring Socket corresponding to the joint debugging task and distributed based on the user ID identification of the joint debugging task and the task ID identification, and the Socket at least comprises an IP address and a port number of a server for receiving the joint debugging result;
The second processing unit is used for creating SocketSink connection based on the Socket; wherein the SocketSink connections include the IP address and port number indicating the path to store the joint debugging results;
And the third processing unit is used for obtaining the joint debugging result in the debugging server through the SocketSink connection and storing the joint debugging result to a data storage area of the server receiving the joint debugging result based on the IP address and the port number.
In one embodiment, the first processing unit is further configured to send the IP address and the port number to a client; the IP address is used for the client to establish communication connection with the server receiving the joint debugging result according to the IP address; and the port number and a port corresponding to the port number are used for the client to acquire the joint debugging result stored in the data storage area.
In one embodiment, the third processing unit is configured to issue a debug instruction to the debug server before the joint debugging result is obtained in the debug server through the SocketSink connection, where the debug instruction at least includes the joint debugging task and the IP address and port number corresponding to the joint debugging task, and the debug instruction is used for the debug server to execute the joint debugging task according to the debug instruction; the IP address and the port number are used for the development platform to determine the joint debugging result of the joint debugging task in a plurality of debugging servers.
In one embodiment, the joint debugging device further comprises:
the fourth processing unit is used for monitoring the queried condition of the joint debugging result in real time;
if the joint debugging result is not queried within the preset time, closing the Socket.
In one embodiment, the third processing unit is further configured to
Acquiring source data to be debugged in a development platform file system; and
And transmitting the source data to be debugged to the debugging server.
A fourth aspect of the present disclosure provides a joint debugging device of an online development platform, applied to a client, including:
the first processing unit is used for receiving the IP address and the port number sent by the development platform;
The second processing unit is used for establishing communication connection with a server receiving the joint debugging result in the development platform based on the IP address;
And the third processing unit is used for acquiring the joint debugging result stored in the server for receiving the joint debugging result based on the port corresponding to the port number.
A fifth aspect of the disclosed embodiments provides a server, comprising: a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is adapted to perform the steps of the method of the first and second aspects described above when the computer program is run.
A sixth aspect of the disclosed embodiments provides a computer readable storage medium having a computer program stored thereon, characterized in that the computer program when executed by a processor implements the steps of the methods of the first and second aspects described above.
The joint debugging test method of the online development platform comprises the steps of obtaining Socket corresponding to a joint debugging task based on user ID identification of the joint debugging task and task ID identification allocation, wherein the Socket at least comprises an IP address and a port number of a server for receiving the joint debugging result; creating SocketSink connection based on Socket; wherein SocketSink connections contain IP addresses and port numbers indicating paths for storing joint debugging results; and obtaining the joint debugging result in the debugging server through SocketSink connection, and storing the joint debugging result to a data storage area of the server for receiving the joint debugging result based on the IP address and the port number. In the application, the joint debugging result in the debugging server is determined based on the IP address and the port number in the Socket through the established SocketSink connection, and the obtained joint debugging result is directly fed back to the data storage area of the server corresponding to the IP address through the SocketSink connection, so that the client can directly read the joint debugging result based on the IP address and the port number to the data storage area in the server storing the joint debugging result. Compared with the prior art, the method has the advantages that the joint debugging results are stored in the database, and then the client side checks the result data in the database in a visual tool or command line mode, so that the data feedback efficiency of the joint debugging results can be effectively improved, and the data checking flow and manpower resources are saved.
Drawings
FIG. 1 is a flowchart of a method for testing joint debugging of an online development platform, according to an exemplary embodiment;
FIG. 2 is a flowchart diagram II of a joint debugging method of an online development platform, shown in accordance with an exemplary embodiment;
FIG. 3 is a schematic diagram of a joint debugging test process of the online development platform shown according to an example embodiment;
FIG. 4 is a flowchart of a method for joint debugging of an online development platform, shown in accordance with an exemplary embodiment;
FIG. 5 is a flowchart of the original logical operations illustrated in accordance with an exemplary embodiment;
FIG. 6 is a flowchart of the logical operation of a joint debugging semi-isolated task shown in accordance with an exemplary embodiment;
FIG. 7 is a flowchart of the logical operations of a joint debugging full isolation task, shown in accordance with an exemplary embodiment;
FIG. 8 is a schematic diagram of a joint debugging test device of the online development platform according to an exemplary embodiment;
FIG. 9 is a schematic diagram II of a joint debugging test device of the online development platform according to an exemplary embodiment;
Fig. 10 is a schematic diagram illustrating a structure of a terminal according to an exemplary embodiment.
Detailed Description
The technical scheme of the invention is further elaborated below by referring to the drawings in the specification and the specific embodiments.
FIG. 1 is a flowchart of a method for testing joint debugging of an online development platform, according to an exemplary embodiment. As shown in FIG. 1, the joint debugging test method of the online development platform comprises the following steps:
Step S100, socket corresponding to the joint debugging task is obtained based on user ID identification of the joint debugging task and task ID identification allocation, wherein the Socket at least comprises an IP address and a port number of a server for receiving the joint debugging result;
step S110, creating SocketSink connection based on the Socket; wherein the SocketSink connections include the IP address and port number indicating the path to store the joint debugging results;
And step S120, connecting through SocketSink, obtaining the joint debugging result in a debugging server, and storing the joint debugging result to a data storage area of the server for receiving the joint debugging result based on the IP address and the port number.
In an exemplary embodiment, the development platform may perform multiple joint debugging tasks. When executing multiple joint debugging tasks, each task may be distinguished based on the user ID identification (i.e., seesion Id) and the task ID identification. For example, when the same user account login platform starts a task, the user ID identifiers corresponding to the joint debugging tasks started under the account are the same, and the corresponding task ID identifiers between different joint debugging tasks are different. For the same joint debugging task started under different user accounts, the user ID identifiers of the joint debugging tasks are different, and the task ID identifiers are the same. Different joint debugging tasks started under different user accounts have different user ID identifications and different task ID identifications. Thus, a user ID and a task ID identify a joint debugging task that is initiated under a user account.
In an exemplary embodiment, after the on-platform joint debugging task is started, the obtaining a Socket corresponding to the joint debugging task based on a user ID identifier of the joint debugging task and task ID identifier allocation includes:
Assembling a keyword KEY through the user ID identifier and the task ID identifier, and searching a Socket corresponding to the joint debugging task in the Map container based on the keyword KEY;
If the corresponding Socket exists, based on a port existing in the Socket, an IP address of a platform server for receiving the joint debugging result is sent to the client;
If the corresponding Socket does not exist, creating a Socket, binding the created Socket to a port, and sending the IP address of the platform server for receiving the joint debugging result to the client through the bound port.
In an exemplary embodiment, a SocketSink connection is created based on Socket; wherein SocketSink connections contain the IP address and port number indicating the path in which the joint debugging results are stored.
In the application, one joint debugging task corresponds to one IP address and occupies one port corresponding to one port number.
And SocketSink, after the joint debugging result is obtained from the debugging server, storing the joint debugging result into a data storage area of the server corresponding to the IP address based on the occupied port number, and allowing the client to directly read the stored joint debugging result based on the port number to the data storage area of the server corresponding to the IP address.
In an exemplary embodiment, the port numbers corresponding to the opened different joint debugging tasks are different. SocketSink is connected with a debugging server to obtain a joint debugging result, and then feeds the joint debugging result back to a Socket through a port number corresponding to the joint debugging task, and stores the joint debugging result to a corresponding data storage area in the server. When the client acquires the joint debugging result, the joint debugging result corresponding to the joint debugging task is read from the server according to the port number.
The joint debugging test method of the online development platform comprises the steps of obtaining Socket corresponding to a joint debugging task based on user ID identification of the joint debugging task and task ID identification allocation, wherein the Socket at least comprises an IP address and a port number of a server for receiving the joint debugging result; creating SocketSink connection based on Socket; wherein SocketSink connections contain IP addresses and port numbers indicating paths for storing joint debugging results; and obtaining the joint debugging result in the debugging server through SocketSink connection, and storing the joint debugging result to a data storage area of the server for receiving the joint debugging result based on the IP address and the port number.
In the application, the joint debugging result in the debugging server is determined based on the IP address and the port number in the Socket through the established SocketSink connection, and the obtained joint debugging result is directly fed back to the data storage area of the server corresponding to the IP address through the SocketSink connection, so that the client can directly read the joint debugging result based on the IP address and the port number to the data storage area in the server storing the joint debugging result. Compared with the prior art, the method has the advantages that the joint debugging results are stored in the database, and then the result data in the database is checked in the form of the visualization tool or the command line, so that the data feedback efficiency of the joint debugging results can be effectively improved, and the data checking flow and human resources are saved.
In one embodiment, the joint debugging method further comprises:
Sending the IP address and the port number to a client; the IP address is used for the client to access the IP address to establish communication connection with the server receiving the joint debugging result; and the port number and a port corresponding to the port number are used for the client to acquire the joint debugging result stored in the data storage area.
In an exemplary embodiment, after the joint debugging task is started on the platform, an IP address and a port number corresponding to the joint debugging task are sent to the client. Different joint debugging tasks correspond to different port numbers. And the client acquires joint debugging results respectively corresponding to different joint debugging tasks based on different port numbers. After receiving the IP address and the port number corresponding to the joint debugging task, the client may establish a communication connection with the platform server, for example, establish a full duplex communication of WebSocket protocol. After SocketSink connection feeds the joint debugging result back to the platform server, the client accesses a port corresponding to the port number of the platform server to obtain the joint debugging result through WebSocket communication.
In one embodiment, the method for testing the joint debugging includes, before the joint debugging result is obtained in the debugging server through the SocketSink connection:
Issuing a debugging instruction to a debugging server, wherein the debugging instruction at least comprises the joint debugging task and the IP address and port number corresponding to the joint debugging task, and the debugging instruction is used for enabling the debugging server to execute the joint debugging task according to the debugging instruction; the IP address and the port number are used for the development platform to determine the joint debugging result of the joint debugging task in a plurality of debugging servers.
In an exemplary embodiment, after receiving the joint debugging task, the platform needs to distribute the joint debugging task to the debugging servers in the server cluster. The debug server performs specific joint debugging tasks. When the platform issues the joint debugging task, the corresponding IP address and the port number can be issued together. After the debugging server executes the joint debugging task, socketSink is connected with the Socket in the platform according to the IP address and the port number corresponding to the joint debugging task to determine the joint debugging result corresponding to the joint debugging task, and then the joint debugging result is fed back to the Socket in the platform.
In one embodiment, the joint debugging method further comprises:
monitoring the queried condition of the joint debugging result in real time;
if the joint debugging result is not queried within the preset time, closing the Socket.
In an exemplary embodiment, in order to save platform resources, a task monitoring module schedule is built in the platform, a monitoring task of the joint debugging task is executed, and consumption conditions of corresponding sockets are monitored. If the client does not consume the Socket service to inquire the joint debugging result through the WebSocket within the preset time, closing the Socket corresponding to the joint debugging task so as to save platform resources (including releasing occupied ports and the like) for executing the joint debugging task in the platform.
In one embodiment, the method further comprises:
Acquiring source data to be debugged in a development platform file system;
The issuing of the debug instruction to the debug server includes:
and transmitting the source data to be debugged to the debugging server.
In an exemplary embodiment, a port number may be included in the SocketSink connection that indicates the source data retrieval, which may indicate the data region of the development platform filesystem source data retrieval. And when a debugging instruction is issued to the debugging server, the acquired source data are issued to the debugging server together to execute the joint debugging task.
In an exemplary embodiment, when the full-isolation joint debugging test is adopted, the source data acquisition of the joint debugging test can be changed from the third party acquisition to the direct acquisition in the platform file system. Meanwhile, the joint debugging result is stored into a database from a Sink, is directly fed back to a Socket from SocketSink connection, and is stored into a data storage area which can be directly read by a client through a port.
In an exemplary embodiment, when a semi-isolated joint debugging test is employed, source data for the joint debugging test may be obtained by a third party. Meanwhile, the joint debugging result is stored into a database from a Sink, is directly fed back to a Socket from SocketSink connection, and is stored into a data storage area which can be directly read by a client through a port.
The embodiment of the disclosure also provides a joint debugging test method of the online development platform, which is applied to the client. FIG. 2 is a flowchart diagram II of a joint debugging method of an online development platform, according to an example embodiment. As shown in fig. 2, the joint debugging method includes:
Step 200, receiving an IP address and a port number sent by the development platform;
step S210, establishing communication connection with a server receiving a joint debugging result in the development platform based on the IP address;
Step S220, based on the port corresponding to the port number, acquiring the joint debugging result stored in the server for receiving the joint debugging result.
In an exemplary embodiment, after receiving the IP address and the port number sent by the development platform, the client server may establish a long connection with the development platform server, access the port corresponding to the port number of the platform server in real time, and query SocketSink the joint debugging result fed back by the connection.
In an exemplary embodiment, the development platform may perform multiple joint debugging tasks. When executing multiple joint debugging tasks, each task may be distinguished based on the user ID identification (i.e., seesion Id) and the task ID identification. For example, when the same user account login platform starts a task, the user ID identifiers corresponding to the joint debugging tasks started under the account are the same, and the corresponding task ID identifiers between different joint debugging tasks are different. For the same joint debugging task started under different user accounts, the user ID identifiers of the joint debugging tasks are different, and the task ID identifiers are the same. Different joint debugging tasks started under different user accounts have different user ID identifications and different task ID identifications. Thus, a user ID and a task ID identify a joint debugging task that is initiated under a user account.
In an exemplary embodiment, a keyword KEY can be assembled on the platform through a user ID identifier and a task ID identifier, and Socket corresponding to the joint debugging task is searched in the Map container based on the keyword KEY;
If the corresponding Socket exists, based on a port existing in the Socket, an IP address of a platform server for receiving the joint debugging result is sent to the client;
If the corresponding Socket does not exist, creating a Socket, binding a port, and sending the IP address of the platform server for receiving the joint debugging result to the client through the bound port.
In an exemplary embodiment, a SocketSink connection is created based on Socket; wherein SocketSink connections contain the IP address and port number indicating the path in which the joint debugging results are stored. In the application, one joint debugging task corresponds to one IP address to occupy one port number. And SocketSink, after the joint debugging result is obtained from the debugging server, storing the joint debugging result into a data storage area of the server corresponding to the IP address based on the occupied port number, and allowing the client to directly read the stored joint debugging result based on the port number to the data storage area of the server corresponding to the IP address.
In an exemplary embodiment, the port numbers corresponding to the opened different joint debugging tasks are different. SocketSink is connected with a debugging server to obtain a joint debugging result, and then feeds the joint debugging result back to a Socket through a port number corresponding to the joint debugging task, and stores the joint debugging result to a corresponding data storage area in the server. When the client acquires the joint debugging result, the joint debugging result corresponding to the joint debugging task is read from the server according to the port number.
The joint debugging test method of the online development platform comprises the steps of receiving an IP address and a port number sent by the development platform; establishing communication connection with a server receiving the joint debugging result in the development platform based on the IP address; and acquiring the joint debugging result stored in a server for receiving the joint debugging result based on the port corresponding to the port number. In the application, through the IP address and port number corresponding to the joint debugging task, long connection communication between the platform servers is established, the port corresponding to the port number is accessed in real time, and the joint debugging result stored in the server receiving the joint debugging result is obtained. Compared with the prior art, the method and the device have the advantages that the data feedback efficiency of the joint debugging result can be effectively improved and the data checking flow and human resources are saved by checking the stored result data through the database in the form of the visualization tool or the command line.
FIG. 3 is a schematic diagram of a joint debugging test process of the online development platform shown according to an example embodiment. As shown in fig. 3, the joint debugging test procedure is divided into 8 steps, including:
1. the client selects a joint debugging task;
2. After receiving the joint debugging task selected by the client, the platform starts a joint debugging test task and creates a Socket corresponding to the joint debugging task;
3. After creating Socket, the platform side carries out logic conversion to create SocketSink connection;
4. the platform side starts joint debugging task monitoring service to monitor the execution of the joint debugging task;
5. the platform side distributes the started joint debugging task to the server cluster to execute joint debugging test;
6. The platform side transmits the joint debugging result completed by the server cluster back to the platform Socket through SocketSink connection;
7. the client acquires the joint debugging result through communication connection established with the platform side, and the page is displayed on the client to display the joint debugging result;
8. And stopping the joint debugging task.
FIG. 4 is a flowchart illustrating an overall method of joint debugging testing of an online development platform, according to an exemplary embodiment. As shown in fig. 4, the overall flow includes:
Step S410, starting a joint debugging task;
step S420, judging whether a corresponding joint debugging task is started or not;
Step S430, when no corresponding joint debugging task is started, starting the joint debugging task and creating a Socket;
Step S440, after creating Socket service, performing task logic conversion, determining whether to use joint debugging task semi-isolation test or full-isolation test, and performing source data source conversion and joint debugging result output path conversion in task logic conversion pilot debugging task semi-isolation test and full-isolation test;
Step S450, starting a monitoring service to monitor joint debugging tasks;
Step S460, dispatching the cluster server to execute joint debugging test tasks and transmitting joint debugging results back to the platform Socket;
Step S470, step S420 judges that the corresponding joint debugging task is started, then the IP address and the port number in the Socket information are returned to the client, or after the Socket is created in step S430, the IP address and the port number in the Socket information are returned to the client;
Step S480, the client obtains a joint debugging result through a WebSocket consumption platform Socket;
Step S490, the client displays the page display joint debugging result.
FIG. 5 is a flowchart illustrating the original logical operations according to an exemplary embodiment. As shown in fig. 5, in the prior art, the source data 1 and the source data 2 of the logic operation in the joint debugging test are both acquired by a third party. And outputting the joint debugging results to a database by the Sink.
FIG. 6 is a flowchart illustrating the logical operation of a joint debugging semi-isolated task in accordance with an exemplary embodiment. As shown in fig. 6, in the present application, the logic operation of the joint debugging semi-isolation task is that the acquisition sources of the source data 1 and the source data 2 are not changed, but the joint debugging result output is changed from Sink to SocketSink. And returning the joint debugging result to the platform Socket through SocketSink.
FIG. 7 is a flowchart illustrating the logical operation of a joint debugging full isolation task in accordance with an example embodiment. As shown in fig. 7, in the present application, the logical operation of the joint debugging full isolation task is that the acquisition sources of the source data 1 and the source data 2 are changed to acquire the stored sample source data from the platform file system, and the joint debugging result output is changed from Sink to SocketSink. And returning the joint debugging result to the platform Socket through SocketSink.
The embodiment of the disclosure also provides a joint debugging testing device of the online development platform, which is applied to a server of the development platform. Fig. 8 is a schematic diagram of a joint debugging device of the online development platform according to an exemplary embodiment. As shown in fig. 8, the joint debugging device includes:
The first processing unit 31 is configured to obtain a Socket corresponding to a joint debugging task based on a user ID identifier of the joint debugging task and a task ID identifier assignment, where the Socket at least includes an IP address and a port number of a server that are used to receive a joint debugging result;
A second processing unit 32, configured to create SocketSink connections based on the Socket; wherein the SocketSink connections include the IP address and port number indicating the path to store the joint debugging results;
and the third processing unit 33 is configured to obtain the joint debugging result from the debug server through the SocketSink connection, and store the joint debugging result to the data storage area of the server receiving the joint debugging result based on the IP address and the port number.
In an exemplary embodiment, the development platform may perform multiple joint debugging tasks. When executing multiple joint debugging tasks, each task may be distinguished based on the user ID identification (i.e., seesion Id) and the task ID identification. For example, when the same user account login platform starts a task, the user ID identifiers corresponding to the joint debugging tasks started under the account are the same, and the corresponding task ID identifiers between different joint debugging tasks are different. For the same joint debugging task started under different user accounts, the user ID identifiers of the joint debugging tasks are different, and the task ID identifiers are the same. Different joint debugging tasks started under different user accounts have different user ID identifications and different task ID identifications. Thus, a user ID and a task ID identify a joint debugging task that is initiated under a user account.
In an exemplary embodiment, after the on-platform joint debugging task is started, the obtaining a Socket corresponding to the joint debugging task based on a user ID identifier of the joint debugging task and task ID identifier allocation includes:
Assembling a keyword KEY through the user ID identifier and the task ID identifier, and searching a Socket corresponding to the joint debugging task in the Map container based on the keyword KEY;
If the corresponding Socket exists, based on a port existing in the Socket, an IP address of a platform server for receiving the joint debugging result is sent to the client;
If the corresponding Socket does not exist, creating a Socket, binding a port, and sending the IP address of the platform server for receiving the joint debugging result to the client through the bound port.
In an exemplary embodiment, a SocketSink connection is created based on Socket; wherein SocketSink connections contain the IP address and port number indicating the path in which the joint debugging results are stored. In the application, one joint debugging task corresponds to one IP address to occupy one port number. And SocketSink, after the joint debugging result is obtained from the debugging server, storing the joint debugging result into a data storage area of the server corresponding to the IP address based on the occupied port number, and allowing the client to directly read the stored joint debugging result based on the port number to the data storage area of the server corresponding to the IP address.
In an exemplary embodiment, the port numbers corresponding to the opened different joint debugging tasks are different. SocketSink is connected with a debugging server to obtain a joint debugging result, and then feeds the joint debugging result back to a Socket through a port number corresponding to the joint debugging task, and stores the joint debugging result to a corresponding data storage area in the server. When the client acquires the joint debugging result, the joint debugging result corresponding to the joint debugging task is read from the server according to the port number.
According to the joint debugging testing device of the online development platform, socket corresponding to the joint debugging task is obtained through obtaining user ID identification based on the joint debugging task and task ID identification distribution, and the Socket at least comprises an IP address and a port number of a server for receiving the joint debugging result; creating SocketSink connection based on Socket; wherein SocketSink connections contain IP addresses and port numbers indicating paths for storing joint debugging results; and obtaining the joint debugging result in the debugging server through SocketSink connection, and storing the joint debugging result to a data storage area of the server for receiving the joint debugging result based on the IP address and the port number. In the application, the joint debugging result in the debugging server is determined based on the IP address and the port number in the Socket through the established SocketSink connection, and the obtained joint debugging result is directly fed back to the data storage area of the server corresponding to the IP address through the SocketSink connection, so that the client can directly read the joint debugging result based on the IP address and the port number to the data storage area in the server storing the joint debugging result. Compared with the prior art, the method has the advantages that the joint debugging results are stored in the database, and then the result data in the database is checked in the form of the visualization tool or the command line, so that the data feedback efficiency of the joint debugging results can be effectively improved, and the data checking flow and human resources are saved.
In one embodiment, the first processing unit is further configured to send the IP address and the port number to a client; the IP address is used for the client to establish communication connection with the server receiving the joint debugging result according to the IP address; and the port number and a port corresponding to the port number are used for the client to acquire the joint debugging result stored in the data storage area.
In an exemplary embodiment, after the joint debugging task is started on the platform, an IP address and a port number corresponding to the joint debugging task are sent to the client. Different joint debugging tasks correspond to different port numbers. And the client acquires joint debugging results respectively corresponding to different joint debugging tasks based on different port numbers. After receiving the IP address and the port number corresponding to the joint debugging task, the client may establish a communication connection with the platform server, for example, establish a full duplex communication of WebSocket protocol. After SocketSink connection feeds the joint debugging result back to the platform server, the client accesses a port corresponding to the port number of the platform server to obtain the joint debugging result through WebSocket communication.
In one embodiment, the third processing unit is configured to issue a debug instruction to the debug server before the joint debugging result is obtained in the debug server through the SocketSink connection, where the debug instruction at least includes the joint debugging task and the IP address and port number corresponding to the joint debugging task, and the debug instruction is used for the debug server to execute the joint debugging task according to the debug instruction; the IP address and the port number are used for the development platform to determine the joint debugging result of the joint debugging task in a plurality of debugging servers.
In an exemplary embodiment, after receiving the joint debugging task, the platform needs to distribute the joint debugging task to the debugging servers in the server cluster. The debug server performs specific joint debugging tasks. When the platform issues the joint debugging task, the corresponding IP address and the port number can be issued together. After the debugging server executes the joint debugging task, socketSink is connected with the Socket in the platform according to the IP address and the port number corresponding to the joint debugging task to determine the joint debugging result corresponding to the joint debugging task, and then the joint debugging result is fed back to the Socket in the platform.
In an exemplary embodiment, after creating SocketSink the connection, when the multi-tasking is performed, the multi-tasking may be performed by generating a multi-threaded pipeline from the execution engine.
In one embodiment, the joint debugging device further comprises:
the fourth processing unit is used for monitoring the queried condition of the joint debugging result in real time;
if the joint debugging result is not queried within the preset time, closing the Socket.
In an exemplary embodiment, in order to save platform resources, a task monitoring module schedule is built in the platform, a monitoring task of the joint debugging task is executed, and consumption conditions of corresponding sockets are monitored. If the client does not consume the Socket query joint debugging result through the WebSocket within the preset time, closing the Socket corresponding to the joint debugging task, so as to save platform resources (including releasing occupied ports and the like) for executing the joint debugging task in the platform.
In one embodiment, the third processing unit is further configured to
Acquiring source data to be debugged in a development platform file system; and
And transmitting the source data to be debugged to the debugging server.
In an exemplary embodiment, a port number may be included in the SocketSink connection that indicates the source data retrieval, which may indicate the data region of the development platform filesystem source data retrieval. And when a debugging instruction is issued to the debugging server, the acquired source data are issued to the debugging server together to execute the joint debugging task.
In an exemplary embodiment, when the full-isolation joint debugging test is adopted, the source data acquisition of the joint debugging test can be changed from the third party acquisition to the direct acquisition in the platform file system. Meanwhile, the joint debugging result is stored into a database from a Sink, is directly fed back to a Socket from SocketSink connection, and is stored into a data storage area which can be directly read by a client through a port.
In an exemplary embodiment, when a semi-isolated joint debugging test is employed, source data for the joint debugging test may be obtained by a third party. Meanwhile, the joint debugging result is stored into a database from a Sink, is directly fed back to a Socket from SocketSink connection, and is stored into a data storage area which can be directly read by a client through a port.
A fourth aspect of the embodiments of the present disclosure provides a joint debugging device of an online development platform, which is applied to a client. Fig. 9 is a schematic diagram of a joint debugging device of the online development platform according to a second embodiment. As shown in fig. 9, the joint debugging device includes:
a first processing unit 41, configured to receive an IP address and a port number sent by the development platform;
a second processing unit 42, configured to establish a communication connection with a server in the development platform that receives the joint debugging result based on the IP address;
And the third processing unit 43 is configured to obtain, based on the port corresponding to the port number, the joint debugging result stored in the server that receives the joint debugging result.
In an exemplary embodiment, after receiving the IP address and the port number sent by the development platform, the client server may establish a long connection with the development platform server, access the port corresponding to the port number of the platform server in real time, and query SocketSink the joint debugging result fed back by the connection.
In an exemplary embodiment, the development platform may perform multiple joint debugging tasks. When executing multiple joint debugging tasks, each task may be distinguished based on the user ID identification (i.e., seesion Id) and the task ID identification. For example, when the same user account login platform starts a task, the user ID identifiers corresponding to the joint debugging tasks started under the account are the same, and the corresponding task ID identifiers between different joint debugging tasks are different. For the same joint debugging task started under different user accounts, the user ID identifiers of the joint debugging tasks are different, and the task ID identifiers are the same. Different joint debugging tasks started under different user accounts have different user ID identifications and different task ID identifications. Thus, a user ID and a task ID identify a joint debugging task that is initiated under a user account.
In an exemplary embodiment, a keyword KEY can be assembled on the platform through a user ID identifier and a task ID identifier, and Socket corresponding to the joint debugging task is searched in the Map container based on the keyword KEY;
If the corresponding Socket exists, based on a port existing in the Socket, an IP address of a platform server for receiving the joint debugging result is sent to the client;
If the corresponding Socket does not exist, creating a Socket, binding a port, and sending the IP address of the platform server for receiving the joint debugging result to the client through the bound port.
In an exemplary embodiment, a SocketSink connection is created based on Socket; wherein SocketSink connections contain the IP address and port number indicating the path in which the joint debugging results are stored. In the application, one joint debugging task corresponds to one IP address to occupy one port number. And SocketSink, after the joint debugging result is obtained from the debugging server, storing the joint debugging result into a data storage area of the server corresponding to the IP address based on the occupied port number, and allowing the client to directly read the stored joint debugging result based on the port number to the data storage area of the server corresponding to the IP address.
In an exemplary embodiment, the port numbers corresponding to the opened different joint debugging tasks are different. SocketSink is connected with a debugging server to obtain a joint debugging result, and then feeds the joint debugging result back to a Socket through a port number corresponding to the joint debugging task, and stores the joint debugging result to a corresponding data storage area in the server. When the client acquires the joint debugging result, the joint debugging result corresponding to the joint debugging task is read from the server according to the port number.
The joint debugging testing device of the online development platform comprises a step of receiving an IP address and a port number sent by the development platform; establishing communication connection with a server receiving the joint debugging result in the development platform based on the IP address; and acquiring the joint debugging result stored in a server for receiving the joint debugging result based on the port corresponding to the port number. In the application, through the IP address and port number corresponding to the joint debugging task, long connection communication between the platform servers is established, the port corresponding to the port number is accessed in real time, and the joint debugging result stored in the server receiving the joint debugging result is obtained. Compared with the prior art, the method and the device have the advantages that the data feedback efficiency of the joint debugging result can be effectively improved and the data checking flow and human resources are saved by checking the stored result data through the database in the form of the visualization tool or the command line.
The application also provides a server. Fig. 10 is a schematic diagram of a server structure shown according to an exemplary embodiment. As shown in fig. 10, a server provided by an embodiment of the present application includes: a processor 530 and a memory 520 for storing a computer program capable of running on the processor, wherein the processor 530 is adapted to perform the steps of the method provided by the above embodiments when the computer program is run.
The application also provides a computer readable storage medium. The computer readable storage medium provided by the embodiments of the present application has a computer program stored thereon, which when executed by a processor implements the steps of the method provided by the above embodiments.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.
The units described as separate units may or may not be physically separate, and units displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present invention may be integrated in one processing module, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units.
In some cases, the two technical features do not conflict, and a new method technical scheme can be combined.
In some cases, the above two technical features may be combined into a new device technical scheme without any conflict.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware associated with program instructions, where the foregoing program may be stored in a computer readable storage medium, and when executed, the program performs steps including the above method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or a optical disk, or the like, which can store program codes.
The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (14)
1. The joint debugging test method for the online development platform is characterized by being applied to a server of the development platform and comprising the following steps of:
acquiring Socket corresponding to a joint debugging task based on a user ID (identity) of the joint debugging task and task ID (identity) allocation, wherein the Socket at least comprises an IP (Internet protocol) address and a port number of a server for receiving a joint debugging result, and the port numbers corresponding to different joint debugging tasks are different;
Creating SocketSink connection based on the Socket; wherein the SocketSink connections include the IP address and port number indicating the path to store the joint debugging results;
Acquiring the joint debugging result from a debugging server through SocketSink connection, and storing the joint debugging result to a data storage area of a server corresponding to the IP address and receiving the joint debugging result based on the port number;
The obtaining the Socket corresponding to the joint debugging task based on the user ID identification of the joint debugging task and the task ID identification allocation comprises the following steps: and assembling a keyword KEY based on the user ID identifier and the task ID identifier of the joint debugging task, and searching a Socket corresponding to the joint debugging task in a Map container based on the keyword KEY.
2. The joint debugging test method of an online development platform according to claim 1, wherein the joint debugging test method further comprises:
Sending the IP address and the port number to a client; the IP address is used for the client to establish communication connection with the server receiving the joint debugging result according to the IP address; the port number is used for the client to access the port corresponding to the port number so as to acquire the joint debugging result stored in the data storage area.
3. The joint debugging test method of the online development platform according to claim 1, wherein the joint debugging test method comprises, before the joint debugging result is obtained in the debugging server through the SocketSink connection:
Issuing a debugging instruction to a debugging server, wherein the debugging instruction at least comprises the joint debugging task and the IP address and the port number corresponding to the joint debugging task, and the debugging instruction is used for the debugging server to execute the joint debugging task according to the debugging instruction; the IP address and the port number are used for the development platform to determine the joint debugging result of the joint debugging task in a plurality of debugging servers.
4. The joint debugging test method of an online development platform according to claim 1, wherein the joint debugging test method further comprises:
monitoring the queried condition of the joint debugging result in real time;
if the joint debugging result is not queried within the preset time, closing the Socket.
5. The joint debugging method of an online development platform of claim 3, wherein the method further comprises:
Acquiring source data to be debugged in a development platform file system;
The issuing of the debug instruction to the debug server includes:
and transmitting the source data to be debugged to the debugging server.
6. The joint debugging test method of the online development platform is characterized by being applied to a client and comprising the following steps of:
Receiving an IP address and a port number sent by the development platform, wherein the IP address and the port number are contained in Socket corresponding to joint debugging tasks, and the port numbers corresponding to different joint debugging tasks are different;
establishing communication connection with a server receiving joint debugging results in the development platform based on the IP address;
acquiring the joint debugging result stored in the server for receiving the joint debugging result based on the port corresponding to the port number;
And the Socket corresponding to the joint debugging task is searched and determined in the Map container based on the user ID identifier of the joint debugging task and the KEY word KEY assembled by the task ID identifier.
7. The joint debugging testing device of the online development platform is characterized by being applied to a server of the development platform and comprising the following components:
the first processing unit is used for acquiring Socket corresponding to the joint debugging task based on the user ID identification of the joint debugging task and the allocation of the task ID identification, wherein the Socket at least comprises an IP address and a port number of a server for receiving the joint debugging result, and the port numbers corresponding to different joint debugging tasks are different;
The second processing unit is used for creating SocketSink connection based on the Socket; wherein the SocketSink connections include the IP address and port number indicating the path to store the joint debugging results;
The third processing unit is used for obtaining the joint debugging result in the debugging server through the SocketSink connection and storing the joint debugging result to a data storage area of a server corresponding to the IP address and receiving the joint debugging result based on the port number;
The first processing unit is configured to assemble a keyword KEY based on a user ID identifier and a task ID identifier of a joint debugging task, and search a Socket corresponding to the joint debugging task in a Map container based on the keyword KEY.
8. The joint debugging device of the online development platform according to claim 7, wherein the first processing unit is further configured to send the IP address and the port number to a client; the IP address is used for the client to establish communication connection with the server receiving the joint debugging result according to the IP address; the port number is used for the client to acquire the joint debugging result stored in the data storage area based on the port corresponding to the port number.
9. The online development platform joint debugging test device according to claim 7, wherein the third processing unit is configured to issue a debug instruction to a debug server before the joint debugging result is obtained in the debug server through the SocketSink connection, where the debug instruction at least includes the joint debugging task and the IP address and port number corresponding to the joint debugging task, and the debug instruction is configured to allow the debug server to execute the joint debugging task according to the debug instruction; the IP address and the port number are used for the development platform to determine the joint debugging result of the joint debugging task in a plurality of debugging servers.
10. The joint debugging testing device of the online development platform of claim 7, wherein the joint debugging testing device further comprises:
the fourth processing unit is used for monitoring the queried condition of the joint debugging result in real time;
if the joint debugging result is not queried within the preset time, closing the Socket.
11. The joint debugging device of an online development platform according to claim 9, wherein the third processing unit is further configured to
Acquiring source data to be debugged in a development platform file system; and
And transmitting the source data to be debugged to the debugging server.
12. The joint debugging testing device of the online development platform is characterized by being applied to a client and comprising:
The first processing unit is used for receiving the IP address and the port number sent by the development platform; the IP address and the port number are contained in Socket corresponding to the joint debugging task, and the port numbers corresponding to different joint debugging tasks are different;
The second processing unit is used for establishing communication connection with a server receiving the joint debugging result in the development platform based on the IP address;
The third processing unit is used for acquiring the joint debugging result stored in the server for receiving the joint debugging result based on the port corresponding to the port number; and the Socket corresponding to the joint debugging task is searched and determined in the Map container based on the user ID identifier of the joint debugging task and the KEY word KEY assembled by the task ID identifier.
13. A server, comprising: a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is adapted to perform the steps of the method of any of claims 1 to 6 when the computer program is run.
14. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110790880.7A CN113590475B (en) | 2021-07-13 | 2021-07-13 | Joint debugging test method and joint debugging test device of online development platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110790880.7A CN113590475B (en) | 2021-07-13 | 2021-07-13 | Joint debugging test method and joint debugging test device of online development platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113590475A CN113590475A (en) | 2021-11-02 |
| CN113590475B true CN113590475B (en) | 2024-05-31 |
Family
ID=78247150
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110790880.7A Active CN113590475B (en) | 2021-07-13 | 2021-07-13 | Joint debugging test method and joint debugging test device of online development platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113590475B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114168244A (en) * | 2021-11-23 | 2022-03-11 | 北京快乐茄信息技术有限公司 | Information processing method and device, electronic equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1359492A (en) * | 1999-01-21 | 2002-07-17 | 毕事快公司 | System and method for testing and validating devices having an embedded operating system |
| CN104679631A (en) * | 2015-03-23 | 2015-06-03 | 重庆蓝岸通讯技术有限公司 | Testing method and system for equipment based on Android system |
| CN105487977A (en) * | 2015-11-30 | 2016-04-13 | 北京锐安科技有限公司 | Agility-oriented automatic test management system and method |
| CN109542981A (en) * | 2018-11-21 | 2019-03-29 | 网易（杭州）网络有限公司 | A kind of system and method, electronic equipment, storage medium that data synchronize |
| CN110493074A (en) * | 2019-07-19 | 2019-11-22 | 珠海金山网络游戏科技有限公司 | A kind of test method and system of server and client |
| CN111045911A (en) * | 2019-12-19 | 2020-04-21 | 京东数字科技控股有限公司 | Performance test method, performance test device, storage medium and electronic equipment |
| CN111211934A (en) * | 2019-12-25 | 2020-05-29 | 曙光信息产业(北京)有限公司 | Cluster remote communication test method and system |
| CN111258902A (en) * | 2020-01-17 | 2020-06-09 | 平安医疗健康管理股份有限公司 | Performance test method and performance test system based on SockJS server |
| CN112597000A (en) * | 2020-12-09 | 2021-04-02 | 山东浪潮通软信息科技有限公司 | WebScoket protocol-based automatic testing method for instant messaging software |
-
2021
- 2021-07-13 CN CN202110790880.7A patent/CN113590475B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1359492A (en) * | 1999-01-21 | 2002-07-17 | 毕事快公司 | System and method for testing and validating devices having an embedded operating system |
| CN104679631A (en) * | 2015-03-23 | 2015-06-03 | 重庆蓝岸通讯技术有限公司 | Testing method and system for equipment based on Android system |
| CN105487977A (en) * | 2015-11-30 | 2016-04-13 | 北京锐安科技有限公司 | Agility-oriented automatic test management system and method |
| CN109542981A (en) * | 2018-11-21 | 2019-03-29 | 网易（杭州）网络有限公司 | A kind of system and method, electronic equipment, storage medium that data synchronize |
| CN110493074A (en) * | 2019-07-19 | 2019-11-22 | 珠海金山网络游戏科技有限公司 | A kind of test method and system of server and client |
| CN111045911A (en) * | 2019-12-19 | 2020-04-21 | 京东数字科技控股有限公司 | Performance test method, performance test device, storage medium and electronic equipment |
| CN111211934A (en) * | 2019-12-25 | 2020-05-29 | 曙光信息产业(北京)有限公司 | Cluster remote communication test method and system |
| CN111258902A (en) * | 2020-01-17 | 2020-06-09 | 平安医疗健康管理股份有限公司 | Performance test method and performance test system based on SockJS server |
| CN112597000A (en) * | 2020-12-09 | 2021-04-02 | 山东浪潮通软信息科技有限公司 | WebScoket protocol-based automatic testing method for instant messaging software |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113590475A (en) | 2021-11-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107453960B (en) | Method, device and system for processing test data in service test | |
| CN113206763B (en) | Simulation test system and method suitable for Internet of things management platform | |
| CN108111364B (en) | Service system testing method and device | |
| CN105045714A (en) | Method and device for testing starting duration of application software and terminal | |
| CN113590475B (en) | Joint debugging test method and joint debugging test device of online development platform | |
| CN116048987A (en) | Processing method, device, electronic equipment, system and storage medium for flow business | |
| CN113849356B (en) | Equipment testing method and device, electronic equipment and storage medium | |
| CN111522744A (en) | Service testing method, device and computer readable storage medium | |
| CN112035346B (en) | Automatic test method, system and medium based on embedded DSP operating system | |
| CN109254791A (en) | Develop management method, computer readable storage medium and the terminal device of data | |
| CN110209565A (en) | A kind of metadata schema adjustment method and its device | |
| CN110955449A (en) | Method and device for releasing gray scale of client | |
| CN109376048A (en) | A kind of test method and equipment of touch screen | |
| CN114003419B (en) | Method, system and device for automatically testing RAS characteristics of memory based on OSES | |
| CN110650063A (en) | Centralized bank third-party software simulation system and method | |
| CN115840617A (en) | Debugging method, system and related device | |
| CN113495723B (en) | Method, device and storage medium for calling functional component | |
| CN113763094B (en) | Service information processing method, device, server, medium and system | |
| CN106844188A (en) | A kind of test agent method, device and test system | |
| CN113868116A (en) | Test dependent data generation method and device, server and storage medium | |
| CN107302605B (en) | Configuration method and device of television proxy server, television and storage medium | |
| CN111082984A (en) | Method and device for simulating login of network equipment to carry out command line interaction | |
| US11537503B2 (en) | Code editor for user interface component testing | |
| CN116893978B (en) | Test plan generation method, system and storage medium based on PTCRB authentication | |
| CN112667498B (en) | Server building method, device, computer equipment and readable 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |