Method and apparatus for testing communication protocol of multi-process terminal software

Abstract

The application discloses a kind of multi-process terminal software communication protocol test method and device, belong to multi-process terminal software test field.The multi-process terminal software communication protocol test method includes: based on multiple communication protocols corresponding to multiple processes, generate visual test page;Receive the first input of visual test page by user, and first input is used to input test task;In response to first input, based on test task and multiple communication protocols, return target execution result.The multi-process terminal software communication protocol test method of the application, by the document of communication protocol, automatically generates visual test tool page, to be tested process interface is verified by visual test tool page, in the case where being not necessary to modify to be tested process, it can complete the checking work of interface protocol and automatically target execution result, effectively ensure that interface between multiple processes is developed according to communication protocol, improve the standardization of multi-process communication protocol.

Description

Technical Field

[0001] This application belongs to the field of multi-process terminal software testing, and in particular relates to a testing method and apparatus for multi-process terminal software communication protocols. Background Technology

[0002] Smart terminal devices are widely used in various fields such as transportation and smart buildings. These devices typically handle hardware module control and backend system integration. In related technologies, a multi-process model is commonly used to develop terminal device software, reducing the impact of hardware module and third-party dynamic library anomalies and significantly improving software reliability. However, existing multi-process models suffer from inconsistent quality and insufficient testing, easily leading to numerous problems during integration and use, affecting overall software quality and development progress. Furthermore, testing each process requires corresponding code modifications, making testing difficult and complex. Summary of the Invention

[0003] This application aims to address at least one of the technical problems existing in the prior art. To this end, this application proposes a testing method and apparatus for a multi-process terminal software communication protocol, thereby standardizing the multi-process communication protocol and simplifying the user's development process.

[0004] Firstly, this application provides a testing method for a multi-process terminal software communication protocol, the method comprising:

[0005] A visual test page is generated based on multiple communication protocols corresponding to multiple processes.

[0006] Receive the user's first input on the visual test page, where the first input is used to input a test task;

[0007] In response to the first input, the target execution result is returned based on the test task and the multiple communication protocols.

[0008] According to the testing method for multi-process terminal software communication protocols in this application, a visual testing tool page is automatically generated based on the communication protocol documentation. This visual testing tool page verifies the interface of the process under test, checking its completion status and whether it is developed in accordance with the communication protocol. The interface protocol check can be completed without modifying the process under test, and the target execution result is automatically returned. This effectively ensures that the interfaces between multiple processes are developed in accordance with the communication protocol, thus achieving the goal of standardizing multi-process communication protocols. It also simplifies the user's development process and effectively improves testing efficiency. Therefore, it solves the technical problems of inconsistencies between communication protocols and process interfaces, and cumbersome self-testing in the development of multi-process software for smart terminals.

[0009] According to one embodiment of this application, generating a visual test page based on multiple communication protocols corresponding to multiple processes includes:

[0010] Receives a second input from the user for multiple worksheets; the second input is used to enter definition information.

[0011] In response to the second input, multiple communication protocols corresponding to the multiple processes are defined based on the definition information; wherein, the multiple processes correspond one-to-one with the multiple communication protocols, and the multiple communication protocols correspond one-to-one with the multiple worksheets;

[0012] The multiple worksheets are converted using a target file conversion tool to generate a web page file.

[0013] The target test service process loads the webpage file and generates a parsed webpage file.

[0014] Receive a third input from the user, the third input being used to input the test service address;

[0015] In response to the third input, the visual test page is generated based on the test service address and the parsed web page file.

[0016] According to one embodiment of this application, the definition information includes at least one of process module name, external interface, input / output parameters, and interface description.

[0017] According to one embodiment of this application, the web page file includes at least one of the following: process module name, external interface, input / output parameters, and interface description.

[0018] According to one embodiment of this application, the step of returning the target execution result based on the test task and the plurality of communication protocols includes:

[0019] The visual test page sends the test task to the test service process based on the communication protocol;

[0020] The test service process calls the target interface corresponding to the test task based on the test task;

[0021] The process under test performs the target operation based on the test task and returns the first execution result;

[0022] The test service process parses the first execution result to generate the target execution result and returns the target execution result to the visualization test page.

[0023] According to one embodiment of this application, the step of returning the target execution result includes:

[0024] The execution results of the target are displayed on the visualization test page.

[0025] Secondly, this application provides a testing apparatus for a multi-process terminal software communication protocol, the apparatus comprising:

[0026] The first processing module is used to generate visual test pages based on multiple communication protocols corresponding to multiple processes;

[0027] The second processing module is used to receive the user's first input on the visual test page, the first input being used to input a test task;

[0028] The third processing module is used to respond to the first input and return the target execution result based on the test task and the multiple communication protocols.

[0029] The testing device for the multi-process terminal software communication protocol of this application automatically generates a visual testing tool page based on the communication protocol documentation. This visual testing tool page verifies the interface of the process under test, checking its completion status and whether it is developed in accordance with the communication protocol. Without modifying the process under test, the device can complete the interface protocol check and automatically return the target execution result. This effectively ensures that the interfaces between multiple processes are developed in accordance with the communication protocol, thus achieving the goal of standardizing multi-process communication protocols. It also simplifies the user's development process and effectively improves testing efficiency. Therefore, it solves the technical problems of inconsistencies between communication protocols and process interfaces, as well as cumbersome self-testing, that exist in the development of multi-process software for smart terminals.

[0030] Thirdly, this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement a test method for the multi-process terminal software communication protocol as described in the first aspect above.

[0031] Fourthly, this application provides a non-transitory computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements a test method for the multi-process terminal software communication protocol as described in the first aspect above.

[0032] Fifthly, this application provides a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the test method for the multi-process terminal software communication protocol as described in the first aspect.

[0033] Sixthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements a test method for the multi-process terminal software communication protocol as described in the first aspect above.

[0034] The above-described one or more technical solutions in the embodiments of this application have at least one of the following technical effects:

[0035] By documenting the communication protocol, a visual testing tool page is automatically generated. This page allows for the verification of the interface of the process under test, checking its completion status and compliance with the communication protocol. The interface protocol check can be completed without modifying the process under test, and the target execution result is automatically returned. This effectively ensures that interfaces between multiple processes are developed according to the communication protocol, thus standardizing multi-process communication protocols. It also simplifies the user's development process and significantly improves testing efficiency. This resolves technical issues such as inconsistencies between communication protocols and process interfaces, and cumbersome self-testing in multi-process software development for smart terminals.

[0036] Furthermore, the interface process is verified by generating a visual testing tool based on the communication protocol, ensuring that the interfaces between multiple processes are developed in accordance with the communication protocol, thereby achieving the goal of standardizing the multi-process communication protocol.

[0037] Furthermore, by displaying the target execution results, a visualization service can be provided to users, which is highly intuitive.

[0038] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0039] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which:

[0040] Figure 1 This is one of the flowcharts illustrating the testing method for the multi-process terminal software communication protocol provided in this application embodiment;

[0041] Figure 2 This is a second flowchart illustrating the testing method for the multi-process terminal software communication protocol provided in this application embodiment;

[0042] Figure 3 This is the third flowchart illustrating the testing method for the multi-process terminal software communication protocol provided in this application embodiment;

[0043] Figure 4 This is a schematic diagram of the structure of the test device for the multi-process terminal software communication protocol provided in the embodiments of this application;

[0044] Figure 5 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0045] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0046] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0047] The following description, in conjunction with the accompanying drawings, details the testing method, testing apparatus, electronic device, and readable storage medium for the multi-process terminal software communication protocol provided in this application, through specific embodiments and application scenarios.

[0048] The testing method for multi-process terminal software communication protocols can be applied to the terminal, and can be executed by the hardware or software in the terminal.

[0049] The terminal includes, but is not limited to, portable communication devices such as mobile phones or tablets. It should also be understood that, in some embodiments, the terminal may not be a portable communication device, but rather a desktop computer.

[0050] The testing method for multi-process terminal software communication protocols provided in this application embodiment can be executed by an electronic device or a functional module or entity in an electronic device that can implement the testing method for multi-process terminal software communication protocols. The electronic devices mentioned in this application embodiment include, but are not limited to, mobile phones, tablets, computers, cameras, and wearable devices. The testing method for multi-process terminal software communication protocols provided in this application embodiment will be described below using an electronic device as the execution subject as an example.

[0051] like Figure 1 As shown, the test method for the multi-process terminal software communication protocol includes steps 110, 120 and 130.

[0052] Step 110: Generate a visual test page based on multiple communication protocols corresponding to multiple processes;

[0053] In this step, multiple processes are those involved in the development and testing of terminal device software.

[0054] For example, multiple processes can include: test service process and the process being tested, etc.

[0055] Different processes have corresponding pre-defined communication protocols.

[0056] The visual test page is used for conducting tests.

[0057] In actual execution, the visual test page can be in HTML webpage format.

[0058] In this application, during the development process, communication protocols corresponding to each process are defined to generate a visual test page. This allows each process to be fully tested according to the agreed communication protocol during subsequent testing, effectively improving the overall software quality and development progress.

[0059] In addition, the software will update accordingly when the communication protocol changes, without requiring manual updates from the user.

[0060] In some embodiments, the visual test page may include: all process modules, interfaces, parameter values, and parameter descriptions, etc.

[0061] The implementation method of step 110 will be explained in detail below.

[0062] like Figure 2 As shown, in some embodiments, step 110 may include:

[0063] Receives a second input from the user for multiple worksheets; the second input is used to enter definition information.

[0064] In response to the second input, multiple communication protocols are defined for multiple processes based on the definition information; wherein, multiple processes correspond one-to-one with multiple communication protocols, and multiple communication protocols correspond one-to-one with multiple worksheets;

[0065] Multiple worksheets are converted using a target file conversion tool to generate a web page file;

[0066] The web page file is loaded based on the target test service process, and the parsed web page file is generated.

[0067] Receive a third input from the user, which is used to enter the test service address;

[0068] In response to the third input, a visual test page is generated based on the test service address and the parsed web page file.

[0069] In this embodiment, the second input is used to input definition information for defining the communication protocol.

[0070] In some embodiments, the definition information may include at least one of the following: process module name, external interface, input / output parameters, and interface description.

[0071] The second input can be in at least one of the following ways:

[0072] Firstly, the second input can be a touch operation, including but not limited to click, swipe, and press operations.

[0073] In this embodiment, receiving the user's second input can be receiving the user's touch operation on the display area of ​​the terminal screen.

[0074] To reduce user error rates, the effective area of ​​the second input can be limited to a specific area, such as the upper middle area of ​​the development interface; or, while the development interface is displayed, a target control can be displayed on the current interface, and touching the target control will enable the second input; or the second input can be set to a series of taps on the display area within a target time interval.

[0075] Secondly, the second input can be physical button input.

[0076] In this embodiment, the terminal is equipped with corresponding physical buttons (such as a mouse or keyboard) to receive the user's second input. This can be receiving the user's operation of pressing the corresponding physical button; the second input can also be a combination operation of pressing multiple physical buttons simultaneously.

[0077] Third, the second input can be voice input.

[0078] In this embodiment, the terminal can trigger the execution of the corresponding operation when it receives a voice command.

[0079] Of course, in other embodiments, the second input may also be in other forms, including but not limited to character input, etc., which can be determined according to actual needs, and this application embodiment does not limit it.

[0080] The worksheet can be an Excel document.

[0081] Using Excel documents can improve the user-friendliness of editing and displaying protocol documents.

[0082] The target file conversion tool can be any available tool.

[0083] In some embodiments, the target file conversion tool can be a self-developed Excel file conversion tool.

[0084] It is understood that in this application, the communication protocol document can be written using an Excel document.

[0085] The communication protocol for each process is defined separately in each worksheet, including but not limited to: process module name, external interface, input and output parameters, and interface description.

[0086] In the actual definition process, users can edit the Excel file, fill it in according to the agreed format (i.e., Excel format), and generate the communication protocol for the multi-process interface of this software development.

[0087] After generating the communication protocol, a target file conversion tool can be used to automatically generate a web page file from the communication protocol in Excel format.

[0088] In some embodiments, the web page file may include at least one of the following: process module name, external interface, input / output parameters, and interface description.

[0089] Before testing, start the target test service process to automatically load the parsed web page file and start the websocket service.

[0090] The target test service process can be a self-developed test service process.

[0091] The third input is used to enter the test service address.

[0092] The third input can be the same as the second input, such as touch input, physical button input, voice input, character input, or any other feasible input, which will not be elaborated here.

[0093] For example, in actual execution, the user enters the test service process address in a browser, opens the parsed web page file, and the test page automatically connects to the test service process's websocket service and automatically generates a visual test page based on the web page file data.

[0094] According to the testing method for multi-process terminal software communication protocols provided in this application, a visual testing tool page is automatically generated based on the communication protocol documentation. This visual testing tool page is used to verify the interface of the process under test, check the completion status of the interface, and detect whether it is developed in accordance with the communication protocol. This allows the system to automatically update based on changes in the communication protocol. Without modifying the process under test, the system can complete the interface protocol check and automatically return the target execution result, effectively simplifying the user's development process and improving testing efficiency.

[0095] Step 120: Receive the user's first input on the visual test page. The first input is used to input the test task.

[0096] In this step, the first input is used to input the test task, and the test task is used to generate test instructions.

[0097] The first input can be the same as the second input, such as touch input, physical button input, voice input, character input, or any other feasible input, which will not be elaborated here.

[0098] Step 130: In response to the first input, based on the test task and multiple communication protocols, return the target execution result.

[0099] In this step, the target execution result is the test result corresponding to this test.

[0100] In actual execution, after the user inputs the test task, the terminal generates test instructions based on the test task to call the corresponding process interface to perform the corresponding operation. For each process, the communication protocol corresponding to that process is used for information transmission, so that each process can be fully tested according to the agreed communication protocol, thereby improving the overall software quality and development progress.

[0101] In some embodiments, returning the target execution result may include displaying the target execution result within a visualization test page.

[0102] In this embodiment, by displaying the target execution result, a visualization service can be provided to the user, which has a high degree of intuitiveness.

[0103] In this application, by combining the documentation corresponding to the communication protocol with the software for development, it is possible to ensure that the interfaces between multiple processes are developed in accordance with the communication protocol during the testing of each provided interface. On the other hand, it is possible to update the corresponding software in a timely and automatic manner when the communication protocol is updated, effectively maintaining the stability of the software. Moreover, unit testing can be performed without modifying the code, making the operation simple and quick.

[0104] In addition, by automatically returning the target execution results, users are not required to manually write unit test reports, which effectively improves testing efficiency.

[0105] According to the testing method for multi-process terminal software communication protocols provided in this application, a visual testing tool page is automatically generated based on the communication protocol documentation. This visual testing tool page verifies the interface of the process under test, checking its completion status and whether it was developed in accordance with the communication protocol. Without modifying the process under test, the interface protocol check can be completed and the target execution result automatically returned. This effectively ensures that interfaces between multiple processes are developed in accordance with the communication protocol, thus achieving the goal of standardizing multi-process communication protocols. It also simplifies the user's development process and effectively improves testing efficiency. Therefore, it solves the technical problems of inconsistencies between communication protocols and process interfaces, and cumbersome self-testing in the development of multi-process software for smart terminals.

[0106] like Figure 3 As shown, in some embodiments, step 130 may include:

[0107] The visual test page sends test tasks to the test service process based on a communication protocol;

[0108] The test service process calls the target interface corresponding to the test task based on the test task;

[0109] The process under test executes the target operation based on the test task and returns the first execution result;

[0110] The test service process parses the first execution result, generates the target execution result, and returns the target execution result to the visualization test page.

[0111] In this embodiment, the target interface is the interface corresponding to the process being tested.

[0112] The first execution result is the test result.

[0113] Continue to refer to Figure 3 In some embodiments, the process under test performs a target operation based on a test task and returns a first execution result, which may include:

[0114] The process under test calls the first interface based on the test task. The first interface is used to execute the test task and generate test results.

[0115] The process under test receives the test result returned by the first interface and returns the test result to the test service process.

[0116] For example, continue to refer to Figure 3 When a user inputs a test task on the visual test page, the visual test page responds to the first input by controlling the test service process to call the specified interface (i.e., the target interface) of the corresponding process according to the received test instructions, and waits for the interface execution result.

[0117] The process under test parses the test instructions, performs the corresponding operations according to the test instructions, and returns the first execution result.

[0118] The test service process parses the first execution result and returns the first execution result and output parameters to the visual test page.

[0119] After receiving the execution results, the visual test page intuitively displays the target execution result of this interface test.

[0120] The target execution result may include, but is not limited to: the execution time of this interface, the overall execution result, the input parameters and the output parameters, and the complete information corresponding to the target execution result will be displayed in the interface console.

[0121] In some embodiments, users can also select multiple interfaces on the visual testing page and input test parameters through the first input to verify and test multiple interfaces at the same time.

[0122] After selecting the interface, users can choose the number of times to perform the test to stress test the interface and verify its stability.

[0123] After the verification test is completed, the target execution results of this round of tests can be displayed in the visual test interface, and the target execution results can be exported to automatically generate a test report.

[0124] The testing method for multi-process terminal software communication protocols provided in the embodiments of this application verifies the interface processes by generating a visual testing tool based on the communication protocol. This ensures that the interfaces between multiple processes are developed in accordance with the communication protocol, thereby achieving the goal of standardizing the multi-process communication protocol.

[0125] The testing method for multi-process terminal software communication protocols provided in this application can be executed by a testing device for multi-process terminal software communication protocols. This application uses an example of a testing device for multi-process terminal software communication protocols executing the testing method for multi-process terminal software communication protocols to illustrate the testing device for multi-process terminal software communication protocols provided in this application.

[0126] This application also provides a testing device for a multi-process terminal software communication protocol.

[0127] like Figure 4 As shown, the test device for the multi-process terminal software communication protocol includes: a first processing module 410, a second processing module 420, and a third processing module 430.

[0128] The first processing module 410 is used to generate a visual test page based on multiple communication protocols corresponding to multiple processes;

[0129] The second processing module 420 is used to receive a first input from the user on the visual test page, the first input being used to input a test task;

[0130] The third processing module 430 is used to respond to the first input and return the target execution result based on the test task and the multiple communication protocols.

[0131] The testing device for multi-process terminal software communication protocols provided in this application automatically generates a visual testing tool page based on the communication protocol documentation. This visual testing tool page verifies the interface of the process under test, checking its completion status and whether it was developed according to the communication protocol. Without modifying the process under test, the device can complete the interface protocol check and automatically return the target execution result. This effectively ensures that the interfaces between multiple processes are developed according to the communication protocol, thus achieving the goal of standardizing multi-process communication protocols. It also simplifies the user's development process and effectively improves testing efficiency. Therefore, it solves the technical problems of inconsistencies between communication protocols and process interfaces, as well as cumbersome self-testing, that exist in the development of multi-process software for smart terminals.

[0132] In some embodiments, the first processing module 410 may also be used for:

[0133] Receives a second input from the user for multiple worksheets; the second input is used to enter definition information.

[0134] In response to the second input, multiple communication protocols are defined for multiple processes based on the definition information; wherein, multiple processes correspond one-to-one with multiple communication protocols, and multiple communication protocols correspond one-to-one with multiple worksheets;

[0135] Multiple worksheets are converted using a target file conversion tool to generate a web page file;

[0136] The web page file is loaded based on the target test service process, and the parsed web page file is generated.

[0137] Receive a third input from the user, which is used to enter the test service address;

[0138] In response to the third input, a visual test page is generated based on the test service address and the parsed web page file.

[0139] In some embodiments, the third processing module 430 can also be used for:

[0140] This enables the visual test page to send test tasks to the test service process based on a communication protocol.

[0141] This enables the test service process to call the target interface corresponding to the test task based on the test task.

[0142] The process under test executes the target operation based on the test task and returns the first execution result;

[0143] The test service process parses the first execution result, generates the target execution result, and returns the target execution result to the visualization test page.

[0144] In some embodiments, the third processing module 430 can also be used to: display the target execution result within the visualization test page.

[0145] The testing device for the multi-process terminal software communication protocol in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the scope of the device.

[0146] The testing device for the multi-process terminal software communication protocol in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system used.

[0147] The testing device for the multi-process terminal software communication protocol provided in this application embodiment can achieve... Figures 1 to 3 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0148] In some embodiments, such as Figure 5As shown, this application embodiment also provides an electronic device 500, including a processor 501, a memory 502, and a computer program stored in the memory 502 and executable on the processor 501. When the program is executed by the processor 501, it implements the various processes of the above-described test method embodiment of the multi-process terminal software communication protocol and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0149] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0150] This application also provides a non-transitory computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described test method embodiment for the multi-process terminal software communication protocol and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0151] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0152] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described test method for the multi-process terminal software communication protocol.

[0153] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0154] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described test method embodiment for the multi-process terminal software communication protocol, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0155] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0156] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0157] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0158] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

[0159] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0160] Although embodiments of this application have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

Claims

1. A testing method for a multi-process terminal software communication protocol, characterized in that, include: A visual test page is generated based on multiple communication protocols corresponding to multiple processes. Receive the user's first input on the visual test page, where the first input is used to input a test task; In response to the first input, based on the test task and the multiple communication protocols, the target execution result is returned; The generation of a visual test page based on multiple communication protocols corresponding to multiple processes includes: Receives a second input from the user for multiple worksheets; the second input is used to enter definition information. In response to the second input, multiple communication protocols corresponding to the multiple processes are defined based on the definition information; wherein, the multiple processes correspond one-to-one with the multiple communication protocols, and the multiple communication protocols correspond one-to-one with the multiple worksheets; The multiple worksheets are converted using a target file conversion tool to generate a web page file. The target test service process loads the webpage file and generates a parsed webpage file. Receive a third input from the user, the third input being used to input the test service address; In response to the third input, the visual test page is generated based on the test service address and the parsed web page file.

2. The testing method for the multi-process terminal software communication protocol according to claim 1, characterized in that, The definition information includes at least one of the following: process module name, external interface, input / output parameters, and interface description.

3. The testing method for the multi-process terminal software communication protocol according to claim 1, characterized in that, The web page file includes at least one of the following: process module name, external interface, input / output parameters, and interface description.

4. The test method for the multi-process terminal software communication protocol according to any one of claims 1-3, characterized in that, Based on the test task and the multiple communication protocols, the target execution result is returned, including: The visual test page sends the test task to the test service process based on the communication protocol; The test service process calls the target interface corresponding to the test task based on the test task; The process under test performs the target operation based on the test task and returns the first execution result; The test service process parses the first execution result to generate the target execution result and returns the target execution result to the visualization test page.

5. The test method for the multi-process terminal software communication protocol according to any one of claims 1-3, characterized in that, The returned target execution result includes: The execution results of the target are displayed on the visualization test page.

6. A testing device for a multi-process terminal software communication protocol, characterized in that, include: The first processing module is used to generate visual test pages based on multiple communication protocols corresponding to multiple processes; The second processing module is used to receive the user's first input on the visual test page, the first input being used to input a test task; The third processing module is used to respond to the first input and return the target execution result based on the test task and the multiple communication protocols; The first processing module is specifically used to receive second input from the user on multiple worksheets; the second input is used to input definition information; In response to the second input, multiple communication protocols corresponding to the multiple processes are defined based on the definition information; wherein, the multiple processes correspond one-to-one with the multiple communication protocols, and the multiple communication protocols correspond one-to-one with the multiple worksheets; The multiple worksheets are converted using a target file conversion tool to generate a web page file. The target test service process loads the webpage file and generates a parsed webpage file. Receive a third input from the user, the third input being used to input the test service address; In response to the third input, the visual test page is generated based on the test service address and the parsed web page file.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the test method for the multi-process terminal software communication protocol as described in any one of claims 1-5.

8. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements a test method for the multi-process terminal software communication protocol as described in any one of claims 1-5.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the test method of the multi-process terminal software communication protocol as described in any one of claims 1-5.

Images