CN113590475A - Joint debugging test method and joint debugging test device for online development platform - Google Patents
Joint debugging test method and joint debugging test device for online development platform Download PDFInfo
- Publication number
- CN113590475A CN113590475A CN202110790880.7A CN202110790880A CN113590475A CN 113590475 A CN113590475 A CN 113590475A CN 202110790880 A CN202110790880 A CN 202110790880A CN 113590475 A CN113590475 A CN 113590475A
- Authority
- CN
- China
- Prior art keywords
- joint debugging
- debugging
- server
- joint
- result
- 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.)
- Granted
Links
- 238000011161 development Methods 0.000 title claims abstract description 90
- 238000012360 testing method Methods 0.000 title claims abstract description 50
- 238000010998 test method Methods 0.000 title claims abstract description 28
- 238000013500 data storage Methods 0.000 claims abstract description 38
- 238000012545 processing Methods 0.000 claims description 38
- 238000000034 method Methods 0.000 claims description 27
- 238000004891 communication Methods 0.000 claims description 25
- 238000012544 monitoring process Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 10
- 230000000007 visual effect Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 9
- 238000006243 chemical reaction Methods 0.000 description 5
- 238000002955 isolation Methods 0.000 description 4
- 238000012800 visualization Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000003287 optical 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
-
- 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 a Socket corresponding to a joint debugging task based on a user ID identification and a task ID identification of the joint debugging task, wherein the Socket at least comprises an IP address and a port number of a server for receiving joint debugging results; creating a Socket sink connection based on Socket; the socket sink connection comprises an IP address and a port number which indicate a path for storing the joint debugging result; and acquiring a joint debugging result through the socket sink connection, and storing the joint debugging result to a data storage area of a server receiving the joint debugging result based on the IP address and the port number. Compared with the prior art, the joint debugging result is stored in the database, and 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 result can be effectively improved, and the data checking flow and the manpower resource 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, the amount of data has increased dramatically with the day. Stream and batch computing engines are becoming more and more popular in enterprise applications. However, the stream and batch computing project is developed according to one requirement, the development time is long, the labor consumption is high, and a stream and batch computing platform is born. Consequently, 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 test 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 identification and a task ID identification of the joint debugging task, wherein the Socket at least comprises an IP address and a port number of a server for receiving a joint debugging result;
creating a SocketSink connection based on the Socket; wherein the SocketSink connection includes the IP address and port number indicating a path for storing the joint debugging result;
and acquiring the joint debugging result in a debugging server through the connection of the Socketsink, 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 one embodiment, the joint debugging test method further includes:
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 for receiving the joint debugging result according to the IP address; and the port number and the port corresponding to the port number are used for the client to access to obtain the joint debugging result stored in the data storage area.
In an embodiment, before the obtaining of the joint debugging result in the debugging server through the SocketSink connection, the joint debugging test method includes:
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; and 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 the debugging servers.
In one embodiment, the joint debugging test method further includes:
monitoring the inquired condition of the joint debugging result in real time;
and if the joint debugging result is not inquired within the preset time length, closing the Socket.
In one embodiment, the method further comprises:
acquiring source data needing debugging in a development platform file system;
the issuing of the debugging instruction to the debugging server comprises the following steps:
and issuing the source data needing debugging to the debugging server.
A second aspect of the embodiments of the present disclosure provides a joint debugging test method for 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 between the server receiving the joint debugging result 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 testing apparatus for an online development platform, which is applied to a server of the development platform, and includes:
the system comprises a first processing unit, a second processing unit and a third processing unit, wherein the first processing unit is used for acquiring a Socket corresponding to a joint debugging task based on a user ID identification and a task ID identification of the joint debugging task, and the Socket at least comprises an IP address and a port number of a server used for receiving a joint debugging result;
the second processing unit is used for creating a Socket sink connection based on the Socket; wherein the SocketSink connection includes the IP address and port number indicating a path for storing the joint debugging result;
and the third processing unit is used for acquiring the joint debugging result in a debugging server through the socket sink 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 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 for receiving the joint debugging result according to the IP address; and the port number and the 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 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 the 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; and 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 the debugging servers.
In one embodiment, the joint debugging test device further comprises:
the fourth processing unit is used for monitoring the inquired condition of the joint debugging result in real time;
and if the joint debugging result is not inquired within the preset time length, closing the Socket.
In one embodiment, the third processing unit is further configured to
Acquiring source data needing debugging in a development platform file system; and
and issuing the source data needing debugging to the debugging server.
A fourth aspect of the present disclosure provides a joint debugging testing apparatus for an online development platform, which is applied to a client, and includes:
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 joint debugging results 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 an embodiment of the present disclosure provides a server, including: a processor and a memory for storing a computer program operable on the processor, wherein the processor is configured to perform the steps of the method of the first and second aspects when executing the computer program.
A sixth aspect of the embodiments of the present disclosure provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps of the method of the first aspect and the second aspect.
The joint debugging test method of the online development platform comprises the steps of obtaining a Socket corresponding to a joint debugging task based on a user ID identification and a task ID identification of the joint debugging task, wherein the Socket at least comprises an IP address and a port number of a server for receiving joint debugging results; creating a Socket sink connection based on Socket; wherein the SocketSink connection comprises an IP address and a port number indicating a path for storing the joint debugging result; and acquiring the joint debugging result in the debugging server through the socket sink 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 the method, the joint debugging result in the debugging server is determined by the created Socket sink connection based on the IP address and the port number in the Socket, 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 Socket sink connection, so that the client can directly read the joint debugging result from the data storage area in the server storing the joint debugging result based on the IP address and the port number. Compared with the prior art, the joint debugging result is stored in the database, and 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 result can be effectively improved, and the data checking flow and the manpower resource are saved.
Drawings
FIG. 1 is a flow diagram illustrating a first method for joint debugging testing of an online development platform, according to an exemplary embodiment;
FIG. 2 is a flowchart illustrating a second method for joint debugging testing of an online development platform, according to an exemplary embodiment;
FIG. 3 is a diagram illustrating a joint debugging test process for an online development platform, according to an exemplary embodiment;
FIG. 4 is a flowchart illustrating an overall method for joint debugging testing of an online development platform, according to an exemplary embodiment;
FIG. 5 is a flowchart illustrating the original logical operations in accordance with an exemplary embodiment;
FIG. 6 is a flowchart illustrating the logical operation of the joint debugging semi-isolated task in accordance with an exemplary embodiment;
FIG. 7 is a flowchart illustrating the logical operations of joint debugging fully isolated tasks in accordance with an illustrative embodiment;
FIG. 8 is a first schematic structural diagram of a joint debugging test apparatus of an online development platform according to an exemplary embodiment;
FIG. 9 is a schematic structural diagram of a joint debugging test apparatus of an online development platform shown in accordance with an exemplary embodiment;
fig. 10 is a diagram illustrating a terminal structure according to an example embodiment.
Detailed Description
The technical solution of the present invention is further described in detail with reference to the drawings and the specific embodiments of the specification.
Fig. 1 is a first flowchart illustrating a joint debugging testing method for an online development platform according to an exemplary embodiment. As shown in fig. 1, the joint debugging test method of the online development platform includes:
step S100, acquiring a Socket corresponding to the joint debugging task based on a user ID identification and a task ID identification of the joint debugging task, wherein the Socket at least comprises an IP address and a port number of a server for receiving a joint debugging result;
step S110, based on the Socket, establishing a Socket sink connection; wherein the SocketSink connection includes the IP address and port number indicating a path for storing the joint debugging result;
and step S120, acquiring the joint debugging result in a debugging server through the socket sink 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 an exemplary embodiment, the development platform may perform multiple joint debugging tasks. When a plurality of joint debugging tasks are executed, the tasks can be distinguished according to the user ID identification (namely the Seesion Id) and the task ID identification. For example, when the same user account logs in a platform to start tasks, the user ID identifications corresponding to each joint debugging task started under the account are the same, and the corresponding task ID identifications between different joint debugging tasks are different. For the same joint debugging task started under different user accounts, the user ID identifications are different, and the task ID identifications are the same. Different joint debugging tasks started under different user accounts have different user ID identifications and different task ID identifications. Therefore, a user ID identification and a task ID identification can determine a joint debugging task opened under a user account.
In an exemplary embodiment, after the joint debugging task on the platform is started, the obtaining of the Socket corresponding to the joint debugging task based on the user ID identifier and the task ID identifier of the joint debugging task includes:
assembling a KEY KEY through a user ID identification and a task ID identification, and searching a Socket corresponding to the joint debugging task in a Map container based on the KEY KEY;
if the corresponding Socket exists, sending an IP address of the platform server for receiving the joint debugging result to the client based on a port existing in the Socket;
and 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, based on Socket, a Socket sink connection is created; wherein the SocketSink connection includes the IP address and port number indicating a path in which the joint call result is stored.
In the application, one joint debugging task corresponds to one IP address and occupies a port corresponding to a port number.
And after the socket sink connection acquires the joint debugging result from the debugging server, storing the joint debugging result into the data storage area of the server corresponding to the IP address based on the occupied port number, and enabling the client to directly read the stored joint debugging result from the data storage area of the server corresponding to the IP address based on the port number.
In an exemplary embodiment, the port numbers corresponding to the different joint debugging tasks are different. And after the Socket sink is connected to the debugging server to obtain the joint debugging result, the joint debugging result is fed back to the Socket through the port number corresponding to the joint debugging task, and the joint debugging result is stored in the corresponding data storage area in the server. When the client side obtains the joint debugging result, the joint debugging result corresponding to the joint debugging task is read in the server according to the port number.
The joint debugging test method of the online development platform comprises the steps of obtaining a Socket corresponding to a joint debugging task based on a user ID identification and a task ID identification of the joint debugging task, wherein the Socket at least comprises an IP address and a port number of a server for receiving joint debugging results; creating a Socket sink connection based on Socket; wherein the SocketSink connection comprises an IP address and a port number indicating a path for storing the joint debugging result; and acquiring the joint debugging result in the debugging server through the socket sink 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 the method, the joint debugging result in the debugging server is determined by the created Socket sink connection based on the IP address and the port number in the Socket, 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 Socket sink connection, so that the client can directly read the joint debugging result from the data storage area in the server storing the joint debugging result based on the IP address and the port number. Compared with the prior art, the joint debugging result is stored in the database, and the result data in the database is checked through a visualization tool or a command line form, so that the data feedback efficiency of the joint debugging result can be effectively improved, and the data checking flow and the manpower resource are saved.
In one embodiment, the joint debugging test method further includes:
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 for receiving the joint debugging result; and the port number and the 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, the IP address and the 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 full duplex communication of the WebSocket protocol. After the socket sink 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 through Websocket communication to obtain the joint debugging result.
In an embodiment, before the obtaining of the joint debugging result in the debugging server through the SocketSink connection, the joint debugging test method includes:
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; and 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 the 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 debugging server executes a specific joint debugging task. When the platform issues the joint debugging task, the joint debugging task and the corresponding IP address and port number can be issued together. After the debugging server executes the joint debugging task, the Socket sink connection determines a joint debugging result corresponding to the joint debugging task according to the IP address and the port number corresponding to the joint debugging task, and then feeds the joint debugging result back to the Socket in the platform.
In one embodiment, the joint debugging test method further includes:
monitoring the inquired condition of the joint debugging result in real time;
and if the joint debugging result is not inquired within the preset time length, closing the Socket.
In an exemplary embodiment, in order to save platform resources, a task monitoring module schedule is established in the platform, a monitoring task of a joint debugging task is executed, and consumption conditions of corresponding sockets are monitored. If the client does not inquire the joint debugging result through the WebSocket consumption Socket service within the preset time length, 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 needing debugging in a development platform file system;
the issuing of the debugging instruction to the debugging server comprises the following steps:
and issuing the source data needing debugging to the debugging server.
In an exemplary embodiment, the SocketSink connection may include a port number therein indicating source data acquisition, which may indicate a data area for development platform file system source data acquisition. And when the 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 fully isolated joint debugging test is adopted, the acquisition of the source data of the joint debugging test can be changed from the acquisition by a third party to the direct acquisition in the platform file system. Meanwhile, the storage of the joint debugging result in the database through the Sink is changed into the direct feedback to the Socket through the Socket Sink connection of the application, and the direct feedback is stored in a data storage area which can be directly read by the client through the port.
In an exemplary embodiment, when employing semi-isolated joint debugging testing, source data for the joint debugging testing may be obtained by a third party. Meanwhile, the storage of the joint debugging result in the database through the Sink is changed into the direct feedback to the Socket through the Socket Sink connection of the application, and the direct feedback is stored in a data storage area which can be directly read by the client through the 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 illustrating a joint debugging testing method of the online development platform according to an exemplary embodiment. As shown in fig. 2, the joint debugging test method includes:
step S200, receiving an IP address and a port number sent by the development platform;
step S210, establishing communication connection between the server receiving the joint debugging result in the development platform based on the IP address;
step S220, obtaining the joint debugging result stored in the server receiving the joint debugging result based on the port corresponding to the port number.
In an exemplary embodiment, after receiving an IP address and a port number sent by a development platform, a client server may establish a long connection with the development platform server, access a port corresponding to the port number of the platform server in real time, and query a joint debugging result fed back by a SocketSink connection.
In an exemplary embodiment, the development platform may perform multiple joint debugging tasks. When a plurality of joint debugging tasks are executed, the tasks can be distinguished according to the user ID identification (namely the Seesion Id) and the task ID identification. For example, when the same user account logs in a platform to start tasks, the user ID identifications corresponding to each joint debugging task started under the account are the same, and the corresponding task ID identifications between different joint debugging tasks are different. For the same joint debugging task started under different user accounts, the user ID identifications are different, and the task ID identifications are the same. Different joint debugging tasks started under different user accounts have different user ID identifications and different task ID identifications. Therefore, a user ID identification and a task ID identification can determine a joint debugging task opened under a user account.
In an exemplary embodiment, a KEY KEY can be assembled on a platform through a user ID identification and a task ID identification, and a Socket corresponding to a joint debugging task is searched in a Map container based on the KEY KEY;
if the corresponding Socket exists, sending an IP address of the platform server for receiving the joint debugging result to the client based on a port existing in the Socket;
and 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, based on Socket, a Socket sink connection is created; wherein the SocketSink connection includes the IP address and port number indicating a path in which the joint call result is stored. In the application, one joint debugging task corresponds to one IP address and occupies one port number. And after the socket sink connection acquires the joint debugging result from the debugging server, storing the joint debugging result into the data storage area of the server corresponding to the IP address based on the occupied port number, and enabling the client to directly read the stored joint debugging result from the data storage area of the server corresponding to the IP address based on the port number.
In an exemplary embodiment, the port numbers corresponding to the different joint debugging tasks are different. And after the Socket sink is connected to the debugging server to obtain the joint debugging result, the joint debugging result is fed back to the Socket through the port number corresponding to the joint debugging task, and the joint debugging result is stored in the corresponding data storage area in the server. When the client side obtains the joint debugging result, the joint debugging result corresponding to the joint debugging task is read in 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 between the server receiving the joint debugging result 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. In the method, long connection communication with the platform server is established through the IP address and the port number corresponding to the joint debugging task, the port corresponding to the port number is accessed in real time, and the joint debugging result stored in the server for receiving the joint debugging result is obtained. Compared with the prior art that the stored result data are checked in the database in a visualization tool or command line mode, the data feedback efficiency of joint debugging results can be effectively improved, and data checking processes and human resources are saved.
FIG. 3 is a diagram illustrating a joint debugging test process for an online development platform, according to an example embodiment. As shown in fig. 3, the joint debugging test process 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 a Socket on the platform side, performing logic conversion, and creating a Socket sink connection;
4. the platform side starts a joint debugging task monitoring service and monitors the execution of joint debugging tasks;
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 the Socket sink connection;
7. the client acquires the joint debugging result through the communication connection established with the platform side, and displays the joint debugging result on a display page of the client;
8. and stopping the joint debugging task.
Fig. 4 is a flowchart illustrating an overall method for joint debugging testing of an online development platform according to an exemplary embodiment. As shown in fig. 4, the overall process includes:
step S410, starting a joint debugging task;
step S420, judging whether a corresponding joint debugging task is started;
step S430, when no corresponding joint debugging task is started, starting the joint debugging task and creating a Socket;
step S440, after Socket service is established, task logic conversion is carried out, whether joint debugging task semi-isolation test or full isolation test is adopted is determined, and the task logic conversion refers to source data source conversion and joint debugging result output path conversion in the joint debugging task semi-isolation test and the full isolation test;
step S450, starting a monitoring service, and monitoring a joint debugging task;
step S460, dispatching the cluster server to execute the joint debugging test task, and returning the joint debugging result to the platform Socket;
step S470 and step S420, if it is determined that the corresponding joint debugging task has been started, returning the IP address and the port number in the Socket information to the client, or returning the IP address and the port number in the Socket information to the client after the Socket is created in step S430;
s480, the client side obtains a joint debugging result through a WebSocket consumption platform Socket;
step S490, the client displays the page and displays the joint tone 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, both the source data 1 and the source data 2 of the logic operation in the joint debugging test are obtained by a third party. And the joint debugging results are output to the database by Sink.
FIG. 6 is a flowchart illustrating the logical operations of the 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-isolated 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 the Socket sink.
FIG. 7 is a flowchart illustrating the logical operations of joint debugging fully isolated tasks in accordance with an exemplary embodiment. As shown in fig. 7, in the present application, the logic operation of the joint debugging fully isolated task is to obtain source data 1 and source data 2 instead of obtaining 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 the Socket sink.
The embodiment of the disclosure further 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 first schematic structural diagram of a joint debugging testing apparatus of an online development platform according to an exemplary embodiment. As shown in fig. 8, the joint debugging test apparatus includes:
the first processing unit 31 is configured to obtain a Socket corresponding to the joint debugging task, where the Socket is allocated based on a user ID identifier and a task ID identifier of the joint debugging task, and the Socket at least includes an IP address and a port number of a server used for receiving a joint debugging result;
a second processing unit 32, configured to create a SocketSink connection based on the Socket; wherein the SocketSink connection includes the IP address and port number indicating a path for storing the joint debugging result;
and a third processing unit 33, configured to obtain the joint debugging result in a debugging server through the SocketSink connection, and store the joint debugging result to a data storage area of the server that receives 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 a plurality of joint debugging tasks are executed, the tasks can be distinguished according to the user ID identification (namely the Seesion Id) and the task ID identification. For example, when the same user account logs in a platform to start tasks, the user ID identifications corresponding to each joint debugging task started under the account are the same, and the corresponding task ID identifications between different joint debugging tasks are different. For the same joint debugging task started under different user accounts, the user ID identifications are different, and the task ID identifications are the same. Different joint debugging tasks started under different user accounts have different user ID identifications and different task ID identifications. Therefore, a user ID identification and a task ID identification can determine a joint debugging task opened under a user account.
In an exemplary embodiment, after the joint debugging task on the platform is started, the obtaining of the Socket corresponding to the joint debugging task based on the user ID identifier and the task ID identifier of the joint debugging task includes:
assembling a KEY KEY through a user ID identification and a task ID identification, and searching a Socket corresponding to the joint debugging task in a Map container based on the KEY KEY;
if the corresponding Socket exists, sending an IP address of the platform server for receiving the joint debugging result to the client based on a port existing in the Socket;
and 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, based on Socket, a Socket sink connection is created; wherein the SocketSink connection includes the IP address and port number indicating a path in which the joint call result is stored. In the application, one joint debugging task corresponds to one IP address and occupies one port number. And after the socket sink connection acquires the joint debugging result from the debugging server, storing the joint debugging result into the data storage area of the server corresponding to the IP address based on the occupied port number, and enabling the client to directly read the stored joint debugging result from the data storage area of the server corresponding to the IP address based on the port number.
In an exemplary embodiment, the port numbers corresponding to the different joint debugging tasks are different. And after the Socket sink is connected to the debugging server to obtain the joint debugging result, the joint debugging result is fed back to the Socket through the port number corresponding to the joint debugging task, and the joint debugging result is stored in the corresponding data storage area in the server. When the client side obtains the joint debugging result, the joint debugging result corresponding to the joint debugging task is read in the server according to the port number.
In the joint debugging test device of the online development platform of the embodiment of the disclosure, a Socket corresponding to a joint debugging task is acquired based on a user ID identification of the joint debugging task and a task ID identification, and the Socket at least comprises an IP address and a port number of a server for receiving a joint debugging result; creating a Socket sink connection based on Socket; wherein the SocketSink connection comprises an IP address and a port number indicating a path for storing the joint debugging result; and acquiring the joint debugging result in the debugging server through the socket sink 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 the method, the joint debugging result in the debugging server is determined by the created Socket sink connection based on the IP address and the port number in the Socket, 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 Socket sink connection, so that the client can directly read the joint debugging result from the data storage area in the server storing the joint debugging result based on the IP address and the port number. Compared with the prior art, the joint debugging result is stored in the database, and the result data in the database is checked through a visualization tool or a command line form, so that the data feedback efficiency of the joint debugging result can be effectively improved, and the data checking flow and the manpower resource 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 for receiving the joint debugging result according to the IP address; and the port number and the 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, the IP address and the 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 full duplex communication of the WebSocket protocol. After the socket sink 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 through Websocket communication to obtain the joint debugging result.
In one embodiment, 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 the 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; and 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 the 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 debugging server executes a specific joint debugging task. When the platform issues the joint debugging task, the joint debugging task and the corresponding IP address and port number can be issued together. After the debugging server executes the joint debugging task, the Socket sink connection determines a joint debugging result corresponding to the joint debugging task according to the IP address and the port number corresponding to the joint debugging task, and then feeds the joint debugging result back to the Socket in the platform.
In an exemplary embodiment, after the SocketSink connection is created, when multitask distribution is performed, multithreading pipeline may be generated according to an execution engine to perform multitask distribution.
In one embodiment, the joint debugging test device further comprises:
the fourth processing unit is used for monitoring the inquired condition of the joint debugging result in real time;
and if the joint debugging result is not inquired within the preset time length, closing the Socket.
In an exemplary embodiment, in order to save platform resources, a task monitoring module schedule is established in the platform, a monitoring task of a joint debugging task is executed, and consumption conditions of corresponding sockets are monitored. If the client does not inquire the joint debugging result through the WebSocket consumption Socket within the preset time length, 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 needing debugging in a development platform file system; and
and issuing the source data needing debugging to the debugging server.
In an exemplary embodiment, the SocketSink connection may include a port number therein indicating source data acquisition, which may indicate a data area for development platform file system source data acquisition. And when the 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 fully isolated joint debugging test is adopted, the acquisition of the source data of the joint debugging test can be changed from the acquisition by a third party to the direct acquisition in the platform file system. Meanwhile, the storage of the joint debugging result in the database through the Sink is changed into the direct feedback to the Socket through the Socket Sink connection of the application, and the direct feedback is stored in a data storage area which can be directly read by the client through the port.
In an exemplary embodiment, when employing semi-isolated joint debugging testing, source data for the joint debugging testing may be obtained by a third party. Meanwhile, the storage of the joint debugging result in the database through the Sink is changed into the direct feedback to the Socket through the Socket Sink connection of the application, and the direct feedback is stored in a data storage area which can be directly read by the client through the port.
A fourth aspect of the present disclosure provides a joint debugging testing apparatus for an online development platform, which is applied to a client. Fig. 9 is a schematic structural diagram of a joint debugging testing apparatus of an online development platform according to an exemplary embodiment. As shown in fig. 9, the joint debugging test apparatus includes:
a first processing unit 41, configured to receive an IP address and a port number sent by the development platform;
the second processing unit 42 is configured to establish a communication connection with a server in the development platform that receives the joint debugging result based on the IP address;
a third processing unit 43, configured to obtain the joint debugging result stored in the server receiving the joint debugging result based on the port corresponding to the port number.
In an exemplary embodiment, after receiving an IP address and a port number sent by a development platform, a client server may establish a long connection with the development platform server, access a port corresponding to the port number of the platform server in real time, and query a joint debugging result fed back by a SocketSink connection.
In an exemplary embodiment, the development platform may perform multiple joint debugging tasks. When a plurality of joint debugging tasks are executed, the tasks can be distinguished according to the user ID identification (namely the Seesion Id) and the task ID identification. For example, when the same user account logs in a platform to start tasks, the user ID identifications corresponding to each joint debugging task started under the account are the same, and the corresponding task ID identifications between different joint debugging tasks are different. For the same joint debugging task started under different user accounts, the user ID identifications are different, and the task ID identifications are the same. Different joint debugging tasks started under different user accounts have different user ID identifications and different task ID identifications. Therefore, a user ID identification and a task ID identification can determine a joint debugging task opened under a user account.
In an exemplary embodiment, a KEY KEY can be assembled on a platform through a user ID identification and a task ID identification, and a Socket corresponding to a joint debugging task is searched in a Map container based on the KEY KEY;
if the corresponding Socket exists, sending an IP address of the platform server for receiving the joint debugging result to the client based on a port existing in the Socket;
and 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, based on Socket, a Socket sink connection is created; wherein the SocketSink connection includes the IP address and port number indicating a path in which the joint call result is stored. In the application, one joint debugging task corresponds to one IP address and occupies one port number. And after the socket sink connection acquires the joint debugging result from the debugging server, storing the joint debugging result into the data storage area of the server corresponding to the IP address based on the occupied port number, and enabling the client to directly read the stored joint debugging result from the data storage area of the server corresponding to the IP address based on the port number.
In an exemplary embodiment, the port numbers corresponding to the different joint debugging tasks are different. And after the Socket sink is connected to the debugging server to obtain the joint debugging result, the joint debugging result is fed back to the Socket through the port number corresponding to the joint debugging task, and the joint debugging result is stored in the corresponding data storage area in the server. When the client side obtains the joint debugging result, the joint debugging result corresponding to the joint debugging task is read in the server according to the port number.
The joint debugging test device of the online development platform comprises an IP address and a port number which are sent by a receiving development platform; establishing communication connection between the server receiving the joint debugging result 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. In the method, long connection communication with the platform server is established through the IP address and the port number corresponding to the joint debugging task, the port corresponding to the port number is accessed in real time, and the joint debugging result stored in the server for receiving the joint debugging result is obtained. Compared with the prior art that the stored result data are checked in the database in a visualization tool or command line mode, the data feedback efficiency of joint debugging results can be effectively improved, and data checking processes and human resources are saved.
The application also provides a server. Fig. 10 is a schematic diagram illustrating a server architecture according to an example embodiment. As shown in fig. 10, a server provided in 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 configured to execute the steps of the method provided by the above embodiments when the computer program runs.
The present application also provides a computer-readable storage medium. The computer-readable storage medium provided by the embodiments of the present application stores thereon a computer program, which when executed by a processor implements the steps of the method provided by the above-mentioned embodiments.
In the several embodiments provided in 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 merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, all the functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may be separately used as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
In some cases, any two of the above technical features may be combined into a new method solution without conflict.
In some cases, any two of the above technical features may be combined into a new device solution without conflict.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media capable of storing program codes, such as a removable Memory device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, and an optical disk.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (14)
1. A joint debugging test method of an online development platform is characterized in that the joint debugging test method is applied to a server of the development platform and comprises the following steps:
acquiring a Socket corresponding to a joint debugging task based on a user ID identification and a task ID identification of the joint debugging task, wherein the Socket at least comprises an IP address and a port number of a server for receiving a joint debugging result;
creating a SocketSink connection based on the Socket; wherein the SocketSink connection includes the IP address and port number indicating a path for storing the joint debugging result;
and acquiring the joint debugging result in a debugging server through the connection of the Socketsink, 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.
2. The joint debugging test method for the online development platform according to claim 1, further comprising:
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 for receiving the joint debugging result according to the IP address; and the port number and the port corresponding to the port number are used for the client to access to obtain the joint debugging result stored in the data storage area.
3. The joint debugging test method for 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; and 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 the debugging servers.
4. The joint debugging test method for the online development platform according to claim 1, further comprising:
monitoring the inquired condition of the joint debugging result in real time;
and if the joint debugging result is not inquired within the preset time length, closing the Socket.
5. The joint debugging test method for the online development platform according to claim 3, further comprising:
acquiring source data needing debugging in a development platform file system;
the issuing of the debugging instruction to the debugging server comprises the following steps:
and issuing the source data needing debugging to the debugging server.
6. A joint debugging test method of an online development platform is characterized by being applied to a client and comprising the following steps:
receiving an IP address and a port number sent by the development platform;
establishing communication connection between the server receiving the joint debugging result 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.
7. The utility model provides an online development platform's joint debugging testing arrangement which characterized in that is applied to development platform's server, includes:
the system comprises a first processing unit, a second processing unit and a third processing unit, wherein the first processing unit is used for acquiring a Socket corresponding to a joint debugging task based on a user ID identification and a task ID identification of the joint debugging task, and the Socket at least comprises an IP address and a port number of a server used for receiving a joint debugging result;
the second processing unit is used for creating a Socket sink connection based on the Socket; wherein the SocketSink connection includes the IP address and port number indicating a path for storing the joint debugging result;
and the third processing unit is used for acquiring the joint debugging result in a debugging server through the socket sink 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.
8. The joint debugging test 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 for receiving the joint debugging result according to the IP address; and the port number and the port corresponding to the port number are used for the client to acquire the joint debugging result stored in the data storage area.
9. The joint debugging test device of the online development platform according to claim 7, wherein the third processing unit is configured to issue a debugging instruction to a debugging server through the SocketSink connection before the joint debugging result is obtained in the debugging server, wherein the debugging instruction at least includes 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; and 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 the debugging servers.
10. The joint debugging test device of the online development platform according to claim 7, further comprising:
the fourth processing unit is used for monitoring the inquired condition of the joint debugging result in real time;
and if the joint debugging result is not inquired within the preset time length, closing the Socket.
11. The joint debugging test device for the on-line development platform according to claim 9, wherein the third processing unit is further configured to
Acquiring source data needing debugging in a development platform file system; and
and issuing the source data needing debugging to the debugging server.
12. The utility model provides an online development platform's joint debugging testing arrangement which characterized in that, is applied to the customer end, includes:
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 joint debugging results 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.
13. A server, comprising: a processor and a memory for storing a computer program operable on the processor, wherein the processor is operable to perform the steps of the method of any of claims 1 to 6 when the computer program is executed.
14. 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 of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110790880.7A CN113590475B (en) | 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 | Joint debugging test method and joint debugging test device of online development platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113590475A true CN113590475A (en) | 2021-11-02 |
| CN113590475B CN113590475B (en) | 2024-05-31 |
Family
ID=
Cited By (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 |
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 |
Cited By (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 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108600311B (en) | Method and device for simulating interface data by client | |
| CN109885496B (en) | Test log management method and system | |
| CN109408310B (en) | Debugging method of server, server and readable storage medium | |
| CN111352750B (en) | Method and system for identifying defect hidden trouble of multi-source image of power transmission line | |
| CN105373563B (en) | Database switching method and device | |
| CN110209565A (en) | A kind of metadata schema adjustment method and its device | |
| CN113448988A (en) | Method and device for training algorithm model, electronic equipment and storage medium | |
| CN113590475B (en) | Joint debugging test method and joint debugging test device of online development platform | |
| CN113590475A (en) | Joint debugging test method and joint debugging test device for online development platform | |
| CN112417122A (en) | Multi-turn question and answer method and device, computer readable storage medium and electronic equipment | |
| CN112559525A (en) | Data checking system, method, device and server | |
| CN111611065A (en) | Calling method and device of machine learning algorithm, storage medium and electronic equipment | |
| CN111447273A (en) | Cloud processing system and data processing method based on cloud processing system | |
| CN113722211B (en) | BMC debugging method, device, system and embedded equipment | |
| CN113495723B (en) | Method, device and storage medium for calling functional component | |
| CN116132344A (en) | Container service debugging method and device based on K8s cluster and electronic equipment | |
| CN111221841A (en) | Real-time processing method and device based on big data | |
| CN112653598B (en) | Automatic testing method, device, equipment and readable storage medium | |
| CN115130911A (en) | Method and device for processing delivery tasks failed to execute by robot | |
| CN113868116A (en) | Test dependent data generation method and device, server and storage medium | |
| CN113849356A (en) | Equipment testing method and device, electronic equipment and storage medium | |
| US7079999B2 (en) | Bus simulation apparatus and bus simulation program | |
| CN113850683A (en) | Car insurance inquiry request processing method and device, computer equipment and storage medium | |
| CN113763094A (en) | Service information processing method, device, server, medium and system | |
| CN109828893A (en) | Multitask android performance test methods based on docker engine and the system for executing this method |
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 |