Method and device for one-band multi-VOIP (Voice over Internet Protocol) equipment linkage test by using ACTION URI (Uniform Resource Identifier)

Abstract

The invention provides a one-band multi-VOIP device linkage test method and device using ACTION URI, and the method comprises the steps: executing a configuration operation on a first to-be-tested VOIP device, the first to-be-tested VOIP device reporting an ACTION event text to a PC client, and the PC client receiving and obtaining the flow change information of the first to-be-tested VOIP device; the PC client extracts interface texts in the ACTION event and records changes between the texts; the PC client extracts state information in the first to-be-tested VOIP equipment and binds the state information with an interface text, the PC client checks a difference part of a change interface in different time periods, carries out gray scale marking, finds out the difference part, and records a differentiation result; and S04, the first VOIP device to be tested sends a key event to the PC client, the PC client converts the key event into device information of other devices to be tested and sends the device information, and the other devices to be tested execute corresponding actions after receiving the device information. In this way, convergent testing can be achieved, N devices can be tested at the same time, the testing process is simplified, and the testing efficiency is improved.

Description

Technical Field

[0001] The embodiments of the present invention generally relate to the technical field of VOIP device testing, and more particularly to a method and apparatus for testing linkage of multiple VOIP devices using ACTION URI. Background Art

[0002] At present, there are more and more product forms in the VOIP industry, including: single-line phones, multi-line phones, color screen phones, video machines, conference machines, etc. The biggest difference is the diversity of interfaces, which leads to the need to cover various models in testing, and the investment of testers and developers is constantly increasing.

[0003] Although automated testing technology is becoming increasingly mature, automation is often performed later and adapted to single models. If real-time testing and testing are to be met at one time, the timeliness is far from enough. In order to ensure the launch of the product, functional testing is prioritized, so testers need to complete functional testing, interface testing, UI testing, etc. first. According to current estimates, if one form product requires one tester, then the limit calculation of one tester is to test 6 products at the same time, and the testing time is 1*(1+0.3). If there are 12 products, then (12 / 6)*(1+0.3) is required. The formula is converted to N when N is greater than 6, and the functional testing input of the tester is N / 6*1.3. At the same time, the problem of redundancy will lead to a rapid increase in test fatigue. At the same time, many test scenarios need to check whether the device interface display logic meets expectations. Multi-device batch operation performs functional testing. When there is no automated coverage, manual verification is required. The current automation-dependent environment needs to be fixed and reduce fluctuations. In any project, automated execution only ensures the return of reliable functions, but many unexpected occurrences still require manual inspection, which is very time-consuming and labor-intensive. Summary of the invention

[0004] To solve the above problems, the present invention controls the terminal device through the VOIP device API, and performs effective text comparison, image feedback, and image difference comparison after texting the interface of the terminal device. It obtains the device interface and other information for labeling, records the device jump process, and compares the before and after difference information. It confirms whether the before and after differences of each device are consistent through the before and after difference information to realize the automatic judgment mechanism, reduce the test personnel to operate multiple batches of different devices at the same time, improve the test efficiency, reduce the problem of redundant construction of the test environment after the test personnel are grouped for testing, and complete the full range of product testing with one deployment, thereby improving work efficiency; by using the ACTION The URI method is used to centrally control the equipment and implement a 1-to-N method. This can converge the test and achieve feedback of N results in one test, which improves the method of remote office. The remote control machine is deployed in the cloud and other places that are accessible from non-office places. The test efficiency of testers can be greatly improved, and redundant testing processes can be simplified. Verification comparison can be achieved through the difference phenomenon before and after the equipment is streamlined, which meets the automatic verification of different button layouts and interface logic, and speeds up the operation inspection of large quantities of equipment. Through the linkage between devices, the smoothness of operation on the real device can be achieved, and other devices can be fed back synchronously to reduce the delay problem of control through intermediate devices.

[0005] According to an embodiment of the present invention, a method and apparatus for one-to-many VOIP device linkage testing using ACTION URI are provided.

[0006] In a first aspect of the present invention, a method for testing multiple VOIP devices in a linked manner using an ACTION URI is provided. The method comprises:

[0007] S01: Performing configuration operations on the first VOIP device to be tested, the first VOIP device to be tested reports the ACTION event text to the PC client through the ACTION URL, the PC client receives the report information of the first VOIP device to be tested, and obtains the process change information of the first VOIP device to be tested;

[0008] S02: PC client extracts the interface text in the ACTION event and records the changes between the texts;

[0009] S03: The PC client extracts the status information of the first VOIP device to be tested and binds it to the interface text. The PC client checks the difference parts of the interface that change in different time periods and marks them in grayscale, finds the difference parts, and records the difference results.

[0010] S04: The first VOIP device under test sends a key event to the PC client according to the key event sequence. The PC client converts the key event into device information of other devices under test through ACTION URI, and sends the device information to other devices under test. After receiving the device information, other devices under test perform corresponding actions. At the same time, other devices under test send their own event information to the PC client.

[0011] S05: After receiving the information returned by other devices under test, the PC client automatically detects whether the before-and-after process differentiation of the jump process of other devices under test is consistent with the before-and-after process differentiation of the jump process of the first VOIP device under test. If they are consistent, a match prompt is displayed; if they are inconsistent, the interface information of the first VOIP device under test presented on the PC client is displayed as a prompt, and further manual inspection and confirmation is performed.

[0012] Furthermore, the ACTION event text in S01 includes the following information: interface information, interface screenshot, button information, interface ID, and configuration information.

[0013] Furthermore, the PC client described in S02 extracts the interface text in the ACTION event and records the changes between the texts, taking the first text as the original comparison text, and records a set of text change character arrays.

[0014] Furthermore, the status information described in S03 includes: interface jump status, call status, LED status and protocol negotiation status.

[0015] Furthermore, the event information described in S04 includes: its own interface ID change logic, key events, LED events, text information characters, and picture names.

[0016] In a second aspect of the present invention, a device for testing multiple VOIP devices in a linked manner using ACTION URI is provided. The device comprises:

[0017] Event reporting module: used to perform configuration operations on the first VOIP device to be tested, the first VOIP device to be tested reports the ACTION event text to the PC client through the ACTION URL, the PC client receives the reporting information of the first VOIP device to be tested, and obtains the process change information of the first VOIP device to be tested;

[0018] Change extraction module: used by the PC client to extract the interface text in the ACTION event and record the changes between the texts;

[0019] Difference recording module: used for the PC client to extract the status information of the first VOIP device to be tested and bind it with the interface text. The PC client checks the difference parts of the interface that change in different time periods and makes grayscale marks, finds the difference parts, and records the difference results;

[0020] Information sharing module: used for the first VOIP device under test to send key events to the PC client according to the key event sequence. The PC client converts the key events into device information of other devices under test through ACTION URI and sends the device information to other devices under test. After receiving the device information, other devices under test perform corresponding actions. At the same time, other devices under test send their own event information to the PC client.

[0021] Difference detection module: used for the PC client to automatically detect whether the before-and-after process differences of the jump process of other devices under test are consistent with the before-and-after process differences of the jump process of the first VOIP device under test after receiving the information returned by other devices under test. If they are consistent, a match prompt will be given; if they are inconsistent, the interface information of the first VOIP device under test presented on the PC client will be prompted, and further manual inspection and confirmation will be required.

[0022] Furthermore, the ACTION event text in the event reporting module includes the following information: interface information, interface screenshot, button information, interface ID, and configuration information.

[0023] Furthermore, the PC client in the change extraction module extracts the interface text in the ACTION event and records the changes between the texts, taking the first text as the original comparison text, and recording a set of text change character arrays.

[0024] Furthermore, the status information in the difference recording module includes: interface jump status, call status, LED status and protocol negotiation status.

[0025] Furthermore, the event information described in S04 includes: its own interface ID change logic, key events, LED event information sharing module, text information characters, and picture names.

[0026] The meanings of the above mentioned English abbreviations:

[0027] VOIP: Voice over Internet Protocol, voice transmission based on IP address

[0028] URI: Uniform Resource Identifier

[0029] ACTION URI: Remote control method

[0030] ACTION URL: Data reporting method

[0031] PC: Computer

[0032] The present invention controls the terminal device through the VOIP device API, and performs effective text comparison, image feedback, and image difference comparison after the interface of the terminal device is texted. The device interface and other information are obtained for labeling, the device jump process is recorded, and the difference information before and after is compared. The difference information before and after is used to confirm whether the difference before and after the operation of each device is consistent to realize the automatic judgment mechanism, reduce the number of testers to operate multiple batches of different devices at the same time, improve the test efficiency, reduce the problem of redundant construction of the test environment after the testers are grouped for testing, and realize that the full series of product tests can be completed by one deployment, thereby improving work efficiency; by using the ACTION URI mode to centrally control the device, a 1-to-N mode is realized, the test can be converged, and the feedback of N results of one test can be achieved, and the remote office method is improved. The remote control machine is deployed in a non-office place such as the cloud, which can greatly improve the test efficiency of the tester and simplify the redundant test process; the difference phenomenon before and after the device process is realized to realize the verification comparison, meet the automatic verification of different button layouts and interface logic, and accelerate the operation inspection of a large number of devices; through the linkage between devices, the smoothness of operation on the real device is realized, and other devices are synchronously fed back, and the delay problem of control through the intermediate device is reduced.

[0033] It should be understood that the contents described in the summary of the invention are not intended to limit the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The above and other features, advantages and aspects of the embodiments of the present invention will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings.

[0035] Figure 1 A flow chart of a method for linkage testing of multiple VOIP devices using ACTION URI according to an embodiment of the present invention is shown;

[0036] Figure 2 A block diagram of an apparatus for testing linkage of multiple VOIP devices using ACTION URI according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0038] According to the implementation mode of the present invention, a method and apparatus for joint testing of multiple VOIP devices using ACTION URI are proposed, the terminal device is controlled through the VOIP device API, and the interface of the terminal device is textualized for effective text comparison, image feedback, and image difference comparison. The device interface and other information are obtained for labeling, the device jump process is recorded, and the before and after difference information is compared. The before and after difference information is used to confirm whether the before and after difference of each device is consistent to realize the automatic judgment mechanism, reduce the test personnel to operate multiple batches of different devices at the same time, improve the test efficiency, reduce the problem of redundant construction of the test environment after the test personnel are grouped for testing, and complete the test of the whole series of products with one deployment, thereby improving the work efficiency. By using ACTION The URI method is used to centrally control the equipment and implement a 1-to-N method. This can converge the test and achieve feedback of N results in one test, which improves the method of remote office. The remote control machine is deployed in the cloud and other places that are accessible from non-office places. The test efficiency of testers can be greatly improved, and redundant testing processes can be simplified. Verification comparison can be achieved through the difference phenomenon before and after the equipment is streamlined, which meets the automatic verification of different button layouts and interface logic, and speeds up the operation inspection of large quantities of equipment. Through the linkage between devices, the smoothness of operation on the real device can be achieved, and other devices can be fed back synchronously to reduce the delay problem of control through intermediate devices.

[0039] The principle and spirit of the present invention are explained in detail below with reference to several representative embodiments of the present invention.

[0040] Figure 1 The present invention is a flowchart of a method for testing multiple VOIP devices in a linked manner using an ACTION URI according to an embodiment of the present invention. The method includes:

[0041] S01: Performing configuration operations on the first VOIP device to be tested, the first VOIP device to be tested reports the ACTION event text to the PC client through the ACTION URL, the PC client receives the report information of the first VOIP device to be tested, and obtains the process change information of the first VOIP device to be tested;

[0042] S02: PC client extracts the interface text in the ACTION event and records the changes between the texts;

[0043] S03: The PC client extracts the status information of the first VOIP device to be tested and binds it to the interface text. The PC client checks the difference parts of the interface that change in different time periods and marks them in grayscale, finds the difference parts, and records the difference results.

[0044] S04: The first VOIP device under test sends a key event to the PC client according to the key event sequence. The PC client converts the key event into device information of other devices under test through ACTION URI, and sends the device information to other devices under test. After receiving the device information, other devices under test perform corresponding actions. At the same time, other devices under test send their own event information to the PC client.

[0045] S05: After receiving the information returned by other devices under test, the PC client automatically detects whether the before-and-after process differentiation of the jump process of other devices under test is consistent with the before-and-after process differentiation of the jump process of the first VOIP device under test. If they are consistent, a match prompt is displayed; if they are inconsistent, the interface information of the first VOIP device under test presented on the PC client is displayed as a prompt, and further manual inspection and confirmation is performed.

[0046] It should be noted that, although the operations of the method of the present invention are described in a specific order in the above embodiments and the accompanying drawings, this does not require or imply that the operations must be performed in the specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0047] In order to explain more clearly the method of using ACTION URI for linkage testing of multiple VOIP devices, a specific embodiment is described below. However, it should be noted that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation to the present invention.

[0048] The following is a specific example to further explain the method of using ACTION URI to test the linkage of multiple VOIP devices:

[0049] Device A, device B, device C...device N need to be updated and tested for commercial versions, and the functional logic of the new versions of the devices need to be re-verified to be normal.

[0050] Create device A as DUT1 device for action URL reporting and connect it to the PC to report information to the PC when an event is generated on the device.

[0051] Perform configuration operations on DUT1: Enter Menu-Configure Function 1-Enable Function 1.

[0052] DUT1 reports the ACTION event text: interface information, interface screenshot, key information, interface ID and configuration information to the PC client through the ACTION URL. The reporting format is as follows:

[0053] {

[0054] Interface information: "Function 1 configuration interface, switch: off";

[0055] Interface screenshot: function1.jpg;

[0056] Button information: 00:01, menu; 00:02, function 1; 00:05, start;

[0057] Interface ID: ID-002 (Function 1 interface);

[0058] Configuration information: Function 1: On, Function 2: Off;

[0059] Event information: Configuration is updating;

[0060] }

[0061] The PC client receives the reporting information of DUT1 and displays the interface screenshot function 1 information and event information on the PC.

[0062] The PC client extracts the interface text in the ACTION event, uses the first text as the original comparison text, and records a set of text change character arrays.

[0063] The PC client extracts the status information of the first VOIP device to be tested: the interface jump status, call status, LED status and protocol negotiation status are bound to the interface text. The PC client checks the different parts of the interface that change in different time periods and marks them in grayscale, finds the different parts, and records the differentiation results.

[0064] The first VOIP device under test sends a key event to the PC client according to the key event timing. The PC client parses the ACTION URL reported by DUT1, obtains the key information, converts the key event into the device information of device B-device N through ACTION URI, and sends the device information to device B-device N in the time sequence of DUT1 and then to other devices under test. After receiving the action uri information from the PC, device B-device N performs the corresponding key operation. After completing the operation, device B-device N reports the ACTION URL information to the PC client in the same format as the device A information.

[0065] The PC client presents the screenshots and key event information of device B-device N. The PC client compares the information reported by device A-device N ACTION URL to verify whether the differentiation is consistent. On the PC client, if the device operation differentiation of device B-device N is the same as that of device A, it is marked as passed. If it is different from that of device A, it is marked as failed, and the tester is reminded to check whether there is any device test abnormality.

[0066] Based on the same inventive concept, the present invention also proposes a device for testing multiple VOIP devices in a linked manner using ACTION URI. The implementation of the device can refer to the implementation of the above method, and the repeated parts will not be repeated. Figure 2 As shown, the device 100 includes:

[0067] Event reporting module 101: used to perform configuration operations on the first VOIP device to be tested, the first VOIP device to be tested reports the ACTION event text to the PC client through the ACTION URL, the PC client receives the reporting information of the first VOIP device to be tested, and obtains the process change information of the first VOIP device to be tested;

[0068] Change extraction module 102: used by the PC client to extract the interface text in the ACTION event and record the changes between the texts;

[0069] Difference recording module 103: used for the PC client to extract the state information of the first VOIP device to be tested and bind it with the interface text, the PC client checks the difference parts of the interface changed in different time periods and makes grayscale marks, finds the difference parts, and records the difference results;

[0070] Information sharing module 104: used for the first VOIP device under test to send a key event to the PC client according to the key event sequence, the PC client converts the key event into device information of other devices under test through ACTION URI, and sends the device information to other devices under test, and other devices under test perform corresponding actions after receiving the device information, and at the same time, other devices under test send their own event information to the PC client;

[0071] Difference detection module 105: After the PC client receives the information returned by other devices under test, it automatically detects whether the before-and-after process differences of the jump process of other devices under test are consistent with the before-and-after process differences of the jump process of the first VOIP device under test. If they are consistent, a match prompt is given; if they are inconsistent, the interface information of the first VOIP device under test presented on the PC client is presented as a prompt, and further manual inspection and confirmation is performed.

[0072] The present invention proposes a device for joint testing of multiple VOIP devices using ACTION URI, which controls the terminal device through the VOIP device API, and performs effective text comparison, image feedback, and image difference comparison after texting the interface of the terminal device. It obtains information such as the device interface for labeling, records the device jump process, and compares the before and after difference information. It confirms whether the before and after differences of each device are consistent through the before and after difference information to implement an automatic judgment mechanism, reduce the number of testers operating multiple batches of different devices at the same time, improve test efficiency, reduce the problem of redundant construction of test environment after testers are grouped for testing, and complete the test of the entire series of products with one deployment, thereby improving work efficiency. By using ACTION The URI method is used to centrally control the equipment and implement a 1-to-N method. This can converge the test and achieve feedback of N results in one test, which improves the method of remote office. The remote control machine is deployed in the cloud and other places that are accessible from non-office places. The test efficiency of testers can be greatly improved, and redundant testing processes can be simplified. Verification comparison can be achieved through the difference phenomenon before and after the equipment is streamlined, which meets the automatic verification of different button layouts and interface logic, and speeds up the operation inspection of large quantities of equipment. Through the linkage between devices, the smoothness of operation on the real device can be achieved, and other devices can be fed back synchronously to reduce the delay problem of control through intermediate devices.

[0073] Although the spirit and principle of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements contained in the spirit and scope of the attached claims.

[0074] Regarding the limitation of the protection scope of the present invention, those skilled in the art should understand that, based on the technical solution of the present invention, various modifications or variations that can be made by those skilled in the art without creative work are still within the protection scope of the present invention.

Claims

1. A method for testing multiple VOIP devices using ACTION URI, characterized in that: The method includes: S01: Performing configuration operations on the first VOIP device to be tested, the first VOIP device to be tested reports the ACTION event text to the PC client through the ACTION URL, the PC client receives the report information of the first VOIP device to be tested, and obtains the process change information of the first VOIP device to be tested; S02: PC client extracts the interface text in the ACTION event and records the changes between the texts; S03: The PC client extracts the status information of the first VOIP device to be tested and binds it to the interface text. The PC client checks the difference parts of the interface that change in different time periods and marks them in grayscale, finds the difference parts, and records the difference results. S04: The first VOIP device under test sends a key event to the PC client according to the key event sequence. The PC client converts the key event into device information of other devices under test through ACTION URI, and sends the device information to other devices under test. After receiving the device information, other devices under test perform corresponding actions. At the same time, other devices under test send their own event information to the PC client. S05: After receiving the information returned by other devices under test, the PC client automatically detects whether the before-and-after process differentiation of the jump process of other devices under test is consistent with the before-and-after process differentiation of the jump process of the first VOIP device under test. If they are consistent, a match prompt is displayed; if they are inconsistent, the interface information of the first VOIP device under test presented on the PC client is displayed as a prompt, and further manual inspection and confirmation is performed.

2. A method for testing multiple VOIP devices in a linked manner using ACTION URI according to claim 1, characterized in that: The ACTION event text described in S01 includes the following information: interface information, interface screenshot, button information, interface ID, and configuration information.

3. The method for testing multiple VOIP devices in a linked manner using ACTION URI according to claim 1, characterized in that: The PC client described in S02 extracts the interface text in the ACTION event and records the changes between the texts, takes the first text as the original comparison text, and records a set of text change character arrays.

4. The method for testing multiple VOIP devices in a linked manner using ACTION URI according to claim 1, characterized in that: The status information described in S03 includes: interface jump status, call status, LED status and protocol negotiation status.

5. The method for testing multiple VOIP devices in a linked manner using ACTION URI according to claim 1, characterized in that: The event information described in S04 includes: its own interface ID change logic, key events, LED events, text information characters, and picture names.

6. A device for testing multiple VOIP devices in linkage using ACTION URI, characterized in that: The device includes: Event reporting module: used to perform configuration operations on the first VOIP device to be tested, the first VOIP device to be tested reports the ACTION event text to the PC client through the ACTION URL, the PC client receives the reporting information of the first VOIP device to be tested, and obtains the process change information of the first VOIP device to be tested; Change extraction module: used by the PC client to extract the interface text in the ACTION event and record the changes between the texts; Difference recording module: used for the PC client to extract the status information of the first VOIP device to be tested and bind it with the interface text. The PC client checks the difference parts of the interface that change in different time periods and makes grayscale marks, finds the difference parts, and records the difference results; Information sharing module: used for the first VOIP device under test to send key events to the PC client according to the key event sequence. The PC client converts the key events into device information of other devices under test through ACTION URI and sends the device information to other devices under test. After receiving the device information, other devices under test perform corresponding actions. At the same time, other devices under test send their own event information to the PC client. Difference detection module: used for the PC client to automatically detect whether the before-and-after process differences of the jump process of other devices under test are consistent with the before-and-after process differences of the jump process of the first VOIP device under test after receiving the information returned by other devices under test. If they are consistent, a match prompt will be given; if they are inconsistent, the interface information of the first VOIP device under test presented on the PC client will be prompted, and further manual inspection and confirmation will be required.

7. The device for testing multiple VOIP devices in linkage using ACTION URI according to claim 6, characterized in that: The ACTION event text described in the event reporting module includes the following information: interface information, interface screenshot, button information, interface ID, and configuration information.

8. The device for testing multiple VOIP devices in linkage using ACTION URI according to claim 6, characterized in that: The PC client described in the change extraction module extracts the interface text in the ACTION event and records the changes between the texts, takes the first text as the original comparison text, and records a set of text change character arrays.

9. The device for testing multiple VOIP devices in linkage using ACTION URI according to claim 6, characterized in that: The status information described in the difference recording module includes: interface jump status, call status, LED status and protocol negotiation status.

10. The device for testing multiple VOIP devices in linkage using ACTION URI according to claim 6, characterized in that: The event information described in S04 includes: its own interface ID change logic, key events, LED event information sharing module, text information characters, and picture names.

Images