CN217825010U

CN217825010U - Communication test system

Info

Publication number: CN217825010U
Application number: CN202221236993.9U
Authority: CN
Inventors: 任永红
Original assignee: Xian Fibocom Wireless Software Inc
Current assignee: Xian Fibocom Wireless Software Inc
Priority date: 2022-05-19
Filing date: 2022-05-19
Publication date: 2022-11-15
Anticipated expiration: 2032-05-19

Abstract

The application discloses a communication test system. The communication test system comprises a first server and at least two execution machines; the first server is used for generating a test case; at least two executors are respectively connected with the first server, the communication module is connected with the executors, and each executor is independently used for initiating a test application to the first server to obtain a test case and controlling the communication module which is respectively connected to execute the test case. Each execution machine and the accessed communication module operate independently, and when any execution machine fails, the test process of other execution machines cannot be influenced, so that the test progress can be smoothly carried out; in addition, the multiple execution machines allow the communication test system to have multiple types of operating systems at the same time, and test requirements under different operating systems can be met.

Description

Communication test system

Technical Field

The application relates to the field of communication testing, in particular to a communication testing system.

Background

Electronic products generally need to be tested in various ways, such as software version upgrade testing, during the development process and before the product is shipped. The existing test item only supports connection of one executive machine, namely, one executive machine can only execute one test case at the same time, and the next test case can be executed only after the current test case is completed. After the server starts and constructs the test cases, one executive machine can acquire all the test cases at one time, the test cases are distributed to the accessed communication modules one by one through a scheduling algorithm, and if the executive machine fails, not only is the test of the current test case failed, but also other test cases can not be executed, and the test progress is influenced. In addition, one execution machine is usually installed with only one type of operating system, and it is obviously difficult to meet the test requirements under different operating systems.

SUMMERY OF THE UTILITY MODEL

In view of this, the present application provides a communication test system, so as to improve the influence of a single executor failing on other test cases, and meet test requirements under different operating systems.

The application provides a communication test system, which comprises a first server and at least two execution machines. The first server is used for generating a test case. At least two executors are respectively connected with the first server, the communication module is connected with the executors, and each executor is independently used for initiating a test application to the first server to obtain a test case and controlling the communication module which is respectively connected to execute the test case.

Optionally, the first server is further configured to manage the test cases distributed to the execution machines.

Optionally, the communication test system further includes a second server, where the second server is connected between the first server and each of the execution machines, and is configured to manage the test cases distributed to each of the execution machines.

Optionally, the second server includes a fault detection unit, each of the execution machines is connected to the fault detection unit, and the fault detection unit is configured to detect whether a communication module accessed by the execution machine fails.

Optionally, the second server includes a backup memory, each of the execution machines is connected to the backup memory, and the backup memory is at least used for storing data generated by the failed communication module when executing the test case.

Optionally, a single execution machine accesses one communication module, or multiple communication modules.

Optionally, the operating systems on which at least some of the execution machines are installed are different.

Optionally, the operating system comprises at least two of: windows system, linux system, mac system, android system.

Optionally, at least some of the actuators are of different types.

Optionally, the type of execution machine comprises at least one of: desktop computer, notebook computer, PAD, smart mobile phone, wearable equipment.

As described above, the communication test system of the present application includes the first server and at least two execution machines connected to the first server, where each execution machine independently initiates a test application to the first server to obtain a test case and controls the communication module accessed to execute the test case, that is, each execution machine and the accessed communication module operate independently, and when any execution machine fails, the test process of other execution machines is not affected, which is beneficial to smooth progress of the test process; in addition, the multiple executors allow the communication test system to have multiple types of operating systems at the same time, so that test requirements under different operating systems can be met, for example, test requirements of the same test case under different operating systems or test requirements of different test cases under the same operating system.

Drawings

Fig. 1 is a schematic view of a scenario of a communication testing system testing a communication module according to an embodiment of the present application;

FIG. 2 is a test flow diagram of the communication test system shown in FIG. 1;

FIG. 3 is a schematic view of a scenario of testing a communication module by a communication testing system according to another embodiment of the present application;

fig. 4 is a test flow diagram of the communication test system shown in fig. 3.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described below with reference to specific embodiments and accompanying drawings. It should be apparent that the embodiments described below are only some embodiments of the present application, and not all embodiments. In case of conflict, the following embodiments and their technical features may be combined with each other and also belong to the technical solutions of the present application.

It should be understood that in the description of the embodiments of the present application, the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only used for convenience of describing technical solutions and simplifying the description of the respective embodiments of the present application, but do not indicate or imply that a device or an element must have a specific orientation, be constructed and operated in a specific orientation, and thus, should not be construed as limiting the present application.

Example 1

Referring to fig. 1, a communication test system 1 includes a first server 10 and a plurality of execution machines 20.

The first server 10 is used to generate test cases. The specific representation form of the test case may be a test version package or a link address of the test version package, and is used for, but not limited to, an upgrade test, for example, a version upgrade test of software such as an operating system or APP installed in the communication module 2.

The communication module 2 may be a communication terminal, such as a mobile terminal, e.g., a mobile phone, a tablet computer, a notebook computer, a palm computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and a fixed terminal, e.g., a Digital TV, a radio, a desktop computer, and the like.

The communication module 2 may be an electronic module with communication function, which may be produced, transported and sold as a separate electronic component, but will be assembled with other components to form a finished product. For example, the electronic module may be a wireless communication module of a product such as an automobile.

The first server 10 generates the test case including at least two scenarios: 1. as shown in fig. 2, a third party such as a manufacturer (for example, an APP developer) selects information construction parameters such as a project to be constructed, a version phase, and the like on an operation interface, and the first server 10 generates a test case according to the construction parameters; 2. a third party such as a manufacturer selects information construction parameters such as a project to be constructed and a version stage, a test case is generated according to the construction parameters, and the first server 10 acquires the test case from the third party such as the manufacturer.

Optionally, the first server 10 may also be used to manage test cases, for example, for multiple test cases, which test cases need to be allocated to which execution machines 20; for example, the time when each test case is issued to each execution unit 20, the time when each test case is executed, and the like.

At least two execution machines 20 are respectively connected with the first server 10, and the functions mainly include two aspects: 1. the test application is used for initiating a test application to the first server 10 to obtain a test case; 2. the state of each communication module 2 is checked (for example, whether the communication module is successfully accessed currently) and a test case is issued to the accessed communication module 2, so that the accessed communication module 2 is controlled to execute the test case, and related data generated by the communication module 2 executing the test case is uploaded to the first server 10.

In a single test event, a single execution machine 20 may access one communication module 2, or may access a plurality of communication modules 2, and the access of the single execution machine 20 to 2 communication modules 2 shown in fig. 1 is only an exemplary illustration, and may also access 3 or more than 3 in an actual scenario.

In the embodiment of the present application, predetermined communication modules 2 may be preset for each of the execution machines 20, and whether the predetermined communication modules 2 are connected to the execution machines 20 in each test event needs to be determined according to the actual required adaptability, that is, in a certain test event, not all the predetermined communication modules 2 are connected to the execution machines 20 to execute the test case.

The reference dimension of the communication module 2 is set for the execution engine 20, including but not limited to at least one of type, operating system, etc. For example, various types of communication modules 2 may be provided for a single execution machine 20, optionally one for each type of communication module 2, including but not limited to a mobile phone, a computer, and a smart watch; for another example, the same type of communication module 2 of various different operating systems may be provided for a single execution machine 20, including but not limited to a mobile phone with a Windows system installed, a mobile phone with a Linux system installed, and a mobile phone with an android system installed.

The execution machines 20 can operate completely independently, so that the communication modules 2 accessed by the execution machines 20 also operate independently, and even if any execution machine 20 fails, the test process of other execution machines 20 is not affected, thereby being beneficial to the smooth progress of the test process.

In addition, all the test cases can be executed synchronously by each execution machine 20, that is, the next test case does not need to be executed after the execution of a certain test case is finished, so that the execution time can be shortened. Of course, a part of the test cases may be allocated to the corresponding execution machines 20, and after the execution is finished, another part of the test cases may be allocated to the corresponding execution machines 20.

The types of test cases executed between the execution machines 20 may be partially the same or completely different, for example, three execution machines 20 execute the version upgrade test of "XX weather forecast" APP, and the other two execution machines 20 execute the audio play test of "XX video player" APP.

Further, the plurality of execution machines 20 are arranged, so that the communication test system 1 can have a plurality of types of operating systems at the same time, and can meet test requirements under different operating systems, for example, test requirements of the same test case under different operating systems or test requirements of different test cases under the same operating system.

For example, in some scenarios, at least some of the operating systems installed by the execution machines 20 are different. Optionally, operating systems that are currently developed or mainstream in the market are included, such as at least two of: windows system, linux system, mac system, android system.

The types of at least some of the execution machines 20 may also be different to meet the management requirements of the test cases for the same or different types of execution machines 20. Optionally, the types of actuators 20 include at least one of: desktop computer, notebook computer, PAD, smart mobile phone, wearable equipment. For the mobile terminal type execution machine 20, the test scenario can be wider and the operability can be stronger, and for the fixed terminal type execution machine 20, the security of the test scenario can be higher and the test result can be more accurate.

Example 2

The same reference numerals are used to identify the same named structural elements in the present application. Based on the description of the foregoing embodiments, please refer to fig. 3 and fig. 4, the communication test system 1 of this embodiment 2 further includes a second server 30, the second server 30 is connected between the first server 10 and each of the execution machines 20, and the second server 30 manages the test cases distributed to each of the execution machines 20.

In this embodiment 2, the second server 30 shares a part of the functions of the first server 10 in embodiment 1, so that the computing capacity or the maximum load capacity of the first server 10 in this embodiment 2 may be smaller than that of the first server 10 in embodiment 1. The server in various embodiments may be a software program integrated into the execution machine 20, or other electronic device.

Alternatively, the second server 30 may include a failure detection unit, and each of the execution machines 20 is connected to the failure detection unit, and the failure detection unit is configured to detect whether the communication module 2 accessed by the execution machine 20 fails. That is, the state of the communication module 2 is detected by the failure detection unit.

Optionally, the second server 30 may include a backup memory, and each execution machine 20 is connected to the backup memory, and the backup memory is at least used for storing data generated by the failed communication module 2 when executing the test case. In other words, the second server 30 is integrated with a disaster recovery backup mechanism, so that once a certain execution machine 20 or a certain communication module 2 fails, related data before the failure and after the failure can be backed up in time, thereby facilitating subsequent troubleshooting and solution of the problem.

It should be understood that the above-mentioned embodiments are only some examples of the present application, and not intended to limit the scope of the present application, and all structural equivalents made by those skilled in the art using the contents of the present specification and the accompanying drawings are also included in the scope of the present application.

Although the terms "first, second, etc. are used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. In addition, the singular forms "a", "an" and "the" are intended to include the plural forms as well. The terms "or" and/or "are to be construed as inclusive or meaning any one or any combination. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some way.

Claims

1. A communication test system is used for testing a communication module and is characterized by comprising a first server and at least two execution machines;

the first server is used for generating a test case;

the at least two executors are respectively connected with the first server, the communication modules are connected with the executors, and each executor is independently used for initiating a test application to the first server to obtain a test case and controlling the communication modules connected with the executor to execute the test case.

2. The communication test system of claim 1,

the first server is also used for managing the test cases distributed to the execution machines;

alternatively, the first and second electrodes may be,

the communication test system also comprises a second server which is connected between the first server and each execution machine and used for managing the test cases distributed to each execution machine.

3. The communication test system according to claim 2, wherein the second server includes a failure detection unit, each of the execution machines is connected to the failure detection unit, and the failure detection unit is configured to detect whether a communication module accessed by the execution machine fails.

4. The communication test system according to claim 3, wherein the second server comprises a backup memory, each of the execution machines is connected to the backup memory, and the backup memory is at least used for storing data generated by the failed communication module when executing the test case.

5. The communication test system according to any one of claims 1 to 4, wherein a single one of the execution machines accesses one of the communication modules or a plurality of the communication modules.

6. The communication test system according to any of claims 1 to 4, wherein at least some of the execution machines are installed with different operating systems.

7. The communication test system of claim 6, wherein the operating system comprises at least two of: windows system, linux system, mac system, android system.

8. The communication test system according to any of claims 1 to 4, wherein at least some of the execution machines are of different types.

9. The communication test system of claim 8, wherein the type of the execution engine comprises at least one of: desktop computer, notebook computer, PAD, smart mobile phone, wearable equipment.