WO2017113912A1

WO2017113912A1 - Physical layer software automation test method and device

Info

Publication number: WO2017113912A1
Application number: PCT/CN2016/100086
Authority: WO
Inventors: 李金凤
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-12-30
Filing date: 2016-09-26
Publication date: 2017-07-06
Also published as: CN106933734A

Abstract

A physical layer software automation test method and device. The method comprises: a parameter generator generating a plurality of groups of case parameters in batches (S110); an algorithm simulator respectively generating a test case corresponding to each group of case parameters (S120); a test agent testing physical layer software to be tested based on the test case (S130); and a test client publishing a test result (S140).

Description

Physical layer software automated test method and device

Technical field

The present disclosure relates to the field of automated testing techniques, for example, to a physical layer software automated testing method and apparatus.

Background technique

The physical layer (Physical Layer, PHY for short) software is generally carried on the digital signal processor (DSP), and the physical layer software mainly performs the modulation and demodulation function of the physical layer digital signal.

The physical layer of Long Term Evolution (LTE) is complex. The downlink needs to handle various transmission modes of TM1 to TM9. The uplink needs to deal with various scenarios such as normal, MIMO, super cell, high-speed rail, and collaboration. The update of the system, the improvement of the system requirements, the physical layer software need to be continuously optimized, the code changes are especially frequent, the development and maintenance of the physical layer software is huge; and the agile development needs to be as agile as possible, so the automated test is to ensure the change can The only way to converge as quickly as possible is to develop an automated test method that is reliable and easy to locate and solve problems.

There are two types of automated testing of physical layer software. 1, PC UT test, this test operation is simple, the positioning problem is fast, but the single test case is limited to each module, the test is not comprehensive; 2, the board test, this test hardware test, can test the whole software code, but The problem of positioning and solving problems is limited, the test period is long, and the problem is not comprehensive enough.

Summary of the invention

The present disclosure provides a physical layer software automated testing method and apparatus for solving the problem that the physical layer software automated testing in the related art is not comprehensive enough.

The present disclosure provides a physical layer software automated testing method, including: a parameter generator batch generating multiple sets of use case parameters; an algorithm simulator respectively generating test cases corresponding to each set of use case parameters; the test agent is based on the test case to measure the physical The layer software is tested; the test client publishes the test results.

Optionally, before the test agent tests the physical layer software to be tested based on the test case, the method further includes: the parameter converter, according to an interface format between the physical layer and the upper layer, an interface in each test case Use case parameters for format conversion.

Optionally, the parameter generator generates a plurality of sets of use case parameters in batches, including: the parameter generator respectively generates each application scenario corresponding to each channel according to parameters of each channel of the physical layer traversed in each application scenario. Use case parameters.

Optionally, the test case includes: input data, a set of use case parameters, and an output reference; the algorithm emulator respectively generates test cases corresponding to each set of use case parameters, including: the algorithm emulator is based on the set of use cases The parameters are run and the input data and output reference corresponding to the set of use case parameters are generated during the running process.

Optionally, the test agent tests the physical layer software to be tested based on the test case, and the test agent performs the physical layer software to be tested running on the physical layer or the simulated physical layer based on the test case. Test and output test results.

Optionally, the test agent tests the physical layer software to be tested based on the test case, including: the test agent reads in input data and use case parameters in the test case; and the test agent calls the test to be tested. Physical layer software, performs testing, and generates an output result; the test agent compares the output result with an output reference in the test case, if the output result and the If the output reference is the same, the test result is the test pass. If the output result is not the same as the output reference, the test result is that the test fails.

The present disclosure also provides a physical layer software automatic testing device, comprising: a parameter generator, configured to generate multiple sets of use case parameters in batches; and an algorithm simulator configured to respectively generate test cases corresponding to each set of use case parameters; a test agent, It is set to test the physical layer software to be tested based on the test case; the test client is set to publish the test result.

Optionally, the apparatus further includes a parameter converter; the parameter converter is configured to: according to an interface format between the physical layer and the upper layer, before the test agent tests the physical layer software to be tested based on the test case, Format conversion of interface use case parameters in each test case.

Optionally, the parameter generator is configured to generate use case parameters corresponding to each application scenario of each channel according to parameters of each channel of the physical layer traversed in each application scenario.

Optionally, the test case includes: input data, a set of use case parameters, and an output reference; the algorithm simulator is configured to run based on the set of use case parameters, and generate the set of use case parameters during operation Corresponding input data and output reference.

Optionally, the test agent is configured to invoke a test case to test the physical layer software to be tested running on the physical layer or the simulated physical layer, and output the test result.

Optionally, the test agent is configured to read input data and use case parameters in the test case, call the physical layer software to be tested, execute the test, and generate an output result; and output the result and the test The output reference in the use case is compared. If the output result is the same as the output reference, the test result is test pass. If the output result is not the same as the output reference, the test result is test fail.

The present disclosure also provides a non-transitory storage medium storing computer executable instructions arranged to perform the physical layer software automated test method described above.

The present disclosure also provides a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer, The computer is caused to perform the above-described physical layer software automated test method.

The present disclosure also provides an electronic device comprising at least one processor and a memory communicatively coupled to the at least one processor, the memory for storing instructions executable by the at least one processor, the instructions being The at least one processor, when executed, causes the at least one processor to perform the physical layer software automated test method described above.

According to an embodiment of the present disclosure, all software-related problems can be found and solved on a PC in a physical layer software development phase by batch generation of test cases for testing all functions of the physical layer software; in the physical layer software maintenance phase, each can be The day builds the test and generates a test log to achieve continuous integration of the physical layer software with high reliability.

DRAWINGS

The one or more embodiments are exemplified by the accompanying drawings in the accompanying drawings, and FIG. The figures in the drawings do not constitute a scale limitation unless otherwise stated.

1 is a flow chart of a physical layer software automated testing method in accordance with an embodiment of the present disclosure;

2 is a specific flowchart of a physical layer software automated testing method according to an embodiment of the present disclosure;

3 is a structural diagram of a physical layer software automated test apparatus according to an embodiment of the present disclosure;

FIG. 4 is a structural diagram of an electronic device according to an embodiment of the present disclosure.

detailed description

The present disclosure is used to test all the functions of the physical layer software, and can find and solve all software-related problems on the PC in the physical layer software development phase; in the physical layer software maintenance phase, the daily build can be tested and a test log can be generated. Realize continuous integration of physical layer software and high reliability. The present disclosure can directly test the physical layer software, and can completely strip or partially strip the underlying hardware, which is a basic guarantee for continuous integration, and can significantly shorten the delivery cycle of the physical layer software.

The present disclosure will be further described in detail below in conjunction with the drawings and embodiments. It should be understood that the features of the following embodiments and examples may be combined with each other without conflict.

Embodiments of the present disclosure provide a physical layer software automated testing method. 1 is a flow chart of a physical layer software automated test method in accordance with an embodiment of the present disclosure. This embodiment can be executed on the PC side, so that full-function testing of the physical layer software does not require on-board testing.

In step S110, the parameter generator generates a plurality of sets of use case parameters in batches.

The parameter generator batch generates multiple sets of use case parameters for testing all functions of the physical layer software.

Each set of use case parameters is a key parameter used to generate test cases. Key parameters include: interface use case parameters. Each set of use case parameters can generate test cases for testing physical layer software.

In step S120, the algorithm simulator respectively generates test cases corresponding to each set of use case parameters.

Each set of use case parameters can be used to generate a test case.

The algorithm simulator can generate test cases in batches according to multiple sets of use case parameters, or generate test cases corresponding to each set of use case parameters according to multiple sets of use case parameters.

Multiple test cases generated by the algorithm simulator are used to test the full functionality of the physical layer software.

In step S130, the test agent tests the physical layer software to be tested based on the test case.

The test agent tests the physical layer software to be tested based on a plurality of test cases generated by the algorithm simulator, and outputs the test results.

In step S140, the test client announces the test result.

The test client obtains the test result outputted by the test agent and publishes it, so that the user sees the test result, and debugs the physical layer software to be tested according to the test result.

The test type of the present disclosure is a software test, and the software test is at least 3 times more efficient in locating and solving the problem than the hardware test. Therefore, the test of the present disclosure is highly efficient. The present disclosure can generate test cases for testing all functions of the physical layer software, and can find and solve all software-related problems on the PC in the physical layer software development stage, and can test the daily build in the physical layer software maintenance stage with high reliability. .

2 is a flow chart of a physical layer software automated testing method in accordance with an embodiment of the present disclosure.

In step S210, an automated test system is initialized.

An automated test system is used to test the full functionality of the physical layer software.

The automated test system includes: a parameter generator, an algorithm simulator, a parameter converter, a test agent, a test code (physical layer software to be tested), and a test client.

In step S220, the parameter generator generates a plurality of sets of use case parameters in batches.

In each set of use case parameters, including key parameters such as interface use case parameters and scene use case parameters.

The parameter generator traverses the parameters of each channel in each application scenario according to each application scenario of each channel, and generates a set of use case parameters corresponding to each application scenario of each channel respectively; respectively input each set of use case parameters into corresponding use cases. Stored in the parameter file. How many sets of use case parameters are how many sets of user parameter files.

In this step, the parameter generator generates multiple sets of use case parameters offline. The parameter generator separately customizes the parameters to be traversed and the traversal values of the parameters for each application scenario of each channel, and generates a corresponding .txt format for the parameters of each application scene of each channel and its traversal values. The file generator traverses each file in .txt format and writes the traversed parameters and their traversal values to the corresponding files. In the example parameter file.

Optionally, the parameter generator generates a use case parameter to generate a configuration file, where the use case parameter generates a configuration file, respectively, a design parameter and an ergodic value thereof for each application scenario of each channel, and respectively stores the file in a .txt format file, and the parameter generator traverses The .txt file is used to generate the use case parameter files for each channel in each application scenario.

Taking the common application scenario of the traffic channel as an example, the parameter generator batch generates an Atp_Params_Fdd_Pusch_Normal_00000x.dat file, which contains parameters required by the algorithm simulator to generate test cases. Among them, some of the parameters required for implementation are optional. The Atp_Params_Fdd_Pusch_Normal_00000x.dat file is an interface between the parameter generator and the algorithm simulator. Each use case parameter file can generate a test case correspondingly, and the naming and storage path of the use case parameter file follows a predetermined rule.

The use case generator can be a use case generation application written in a programmable language on a PC.

Step S230, the algorithm simulator respectively generates test cases corresponding to each set of use case parameters.

Test cases include: input data, use case parameters, and output references.

The input data in the test case includes: receive antenna data.

A set of use case parameters in a test case can be a use case parameter file containing the set of use case parameters.

The output reference in the test case means that the algorithm simulator obtains a set of use case parameters and runs based on the set of use case parameters. During the running process, the algorithm simulator generates input data and output data corresponding to the set of use case parameters. This output data is the output reference. This output reference can be used as a criterion for determining whether the physical layer software has passed the test.

In this step, multiple sets of use case parameters generated in batches are input into an algorithm simulator, and the algorithm simulator generates test cases according to each set of use case parameters, and forms a test package based on the generated multiple test cases.

Each set of use case parameters can generate a static test case. Batch generated use case parameter file Input to the algorithm simulator, where each use case parameter file can be used as a complete input to the algorithm simulator. In the process of inputting the use case parameter file, the algorithm simulator can sequentially generate test cases according to a single use case parameter file, or batch generate test cases according to multiple use case parameter files.

Optionally, the algorithm simulator reads the use case parameter file one by one from the storage path of the use case parameter file and generates test cases one by one. The test case includes an input data file, an output reference file, and a use case parameter file. The input data file and the output reference file are both in .bin format, and the output use case parameter file is in .txt format.

The algorithm simulator can also process or transparently pass the use case parameters.

Processing refers to: simulating high-level, calculating the parameters required to generate the PHY layer according to the high-level protocol parameters in the test case.

Transparent transmission means that some parameters that are not concerned by the algorithm simulator are output according to the input format, in order to facilitate subsequent parameter format conversion.

The algorithm simulator can achieve Bit True with the application code. The parameter generator is written in matlab, and the algorithm simulator can be matlab simulator, so the parameter generator and algorithm simulator are all carried on matlab.

Step S240, the parameter converter performs format conversion on the interface use case parameters in each test case according to the interface format between the physical layer and the upper layer.

The upper layers of the physical layer are the data link layer and the user plane.

The parameter converter processes the parameters in the use case parameter file, and converts the interface use case parameters of each test case into an interface format between the physical layer and the upper layer. The parameter converter reads the use case parameter file in the test case, identifies the interface use case parameter in the use case parameter file, and converts the interface use case parameter into an interface format between the PHY and the upper layer. The parameter converter can be handled flexibly according to different interfaces.

The parameter converter can be a program written in a programmable language. Parameter converter in this embodiment Loaded on the compiler VC, the compiler VC reads each parameter in the use case parameter file one by one, and generates a high-level and PHY interface according to the PHY-side interface, and saves it in a .bin format. The converted interface is identical to the interface of the upper layer and the PHY.

The formatted test case constitutes a complete use case for testing the physical layer software.

In step 250, the test agent tests the physical layer software to be tested based on the test case.

The test agent tests the physical layer software to be tested running on the physical layer or the simulated physical layer based on the test case, and outputs the test result.

Further, the test agent reads the input data and use case parameters in the test case, calls the physical layer software to be tested, executes the test, and generates an output result; the test agent compares the output result with the output reference in the test case, If the output result is the same as the output reference, the test result is the test pass. If the output result is not the same as the output reference, the test result is the test fail.

In this step, the test agent is carried on the DSP chip softener or carried on the PC. The DSP chip softener can simulate the operation of the DSP chip.

The input data file and output reference file in .bin format, and the use case parameter file in formatted .bin format form a complete set of test cases. Put the test case in the specified directory of the test agent, call the test agent to test, and the test agent calls the application dispatch main function to test.

If the test agent is running on the DSP chip softener, the underlying function pile that needs to be tested is removed for on-chip emulation testing.

If the test agent is running on a PC, all the underlying layers need to be piled up, and the stub function is also part of the test agent.

The test agent builds an automated test system on the PC, adds the underlying layer, and writes the use case read and match code. The stub function sets up the test packages that need to be tested, and each test package can contain several test sets. Tests are performed by the test client launching the test agent, which requires all of the test packages Test cases need to call the hook function to perform the following steps:

Step 1: Read the use case parameter file and the input data file in the test case;

In step 2, the application layer of the tested code (physical layer software) of the physical layer is called and the main function is processed, and all the output results are collected.

In step 3, the output reference file is read, the collected test and the reference output are compared, and the comparison result is output. The result of the comparison is the test result. Further, the test result is compared with the output reference. If the test result and the output reference are the same, the test result is the test pass. If the test result is different from the output reference, the test fails.

In step S260, the test client issues the test result.

The test client can test the client with Jenkins.

The test client can implement distributed testing and publish the test results in the form of emails. The results of the release can be displayed directly in the email, or you can set the way to get the test results in the email.

After all test cases have been executed, the test client collects the test results and publishes the test results to the testers.

The present disclosure traverses all combinations of physical layer parameters by using a use case generator, sub-channels, and application scenarios, and generates test cases in batches. Based on the present disclosure, test cases can be constructed more complex than in an actual environment, and the test cases are fully covered, and the test cases are significantly improved. The reliability of the test.

The disclosure overcomes the drawbacks of the previous full-function test based on the DSP board test by partially and completely stripping the hardware, and achieves the effect of solving all software problems in the PC and DSP chip soft-mold test, thereby effectively improving the test efficiency and reducing the efficiency. Problem positioning and resolution costs, shortening the version convergence cycle.

By testing the client, the present invention performs real-time automatic testing and publishes test results as needed, so that it is convenient to test and release the results for the first time, reduce the cost of testing and maintenance, and find problems as soon as possible to improve the effectiveness of continuous integration.

The embodiment of the present disclosure further provides a physical layer software automatic testing device. 3 is a structural diagram of a physical layer software automated test apparatus according to an embodiment of the present disclosure. The physical layer software automated test apparatus includes a parameter generator 310, an algorithm simulator 320, a test agent 330, and a test client 340.

The parameter generator 310 is configured to generate a plurality of sets of use case parameters in batches.

The algorithm simulator 320 is configured to generate test cases corresponding to each set of use case parameters.

The test agent 330 is configured to test the physical layer software to be tested based on the test case.

Test client 340 is set to publish test results.

In one embodiment, the apparatus further includes a parameter converter (not shown); the parameter converter is configured to be between the physical layer and the upper layer before the test agent tests the physical layer software to be tested based on the test case Interface format for format conversion of interface use case parameters in each test case.

The parameter generator 310 is configured to generate a set of use case parameters corresponding to each application scenario of each channel according to the parameters of each channel of the physical layer traversed in each application scenario.

The test case includes: input data, a set of use case parameters, and an output reference, the test case being obtained by inputting a use case parameter into an algorithm simulator; the algorithm emulator 320 being configured to operate based on the set of use case parameters And generating input data and output reference corresponding to the set of use case parameters during operation. In this way, a test case corresponding to the set of use case parameters is formed.

The test agent 330 is configured to test the physical layer software to be tested running on the physical layer or the simulated physical layer based on the test case, and output the test result.

The test agent 330 is configured to read the input data and the use case parameters in the test case, call the physical layer software to be tested, execute the test, and generate an output result; compare the output result with the output reference in the test case If the output result is the same as the output reference, the test result is a test pass. If the output result is not the same as the output reference, the test result is a test fail.

The functions of the device in this embodiment have been described in the method embodiments shown in FIG. 1 to FIG. 2, and therefore, in the description of the present embodiment, reference may be made to the related description in the foregoing embodiments. This will not be repeated.

The present disclosure also provides a non-transitory storage medium storing computer executable instructions arranged to perform the physical layer software automated test method of the above embodiments.

The present disclosure also provides a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions, when the program instructions are executed by a computer, The computer is caused to perform the physical layer software automated test method of the above embodiment.

The present disclosure also provides an electronic device. FIG. 4 is a structural block diagram of an electronic device according to an embodiment of the present disclosure. The electronic device may include a processor 51, a communication interface 52, a memory 53 and a bus 54, wherein the processor 51, the communication interface 52, and the memory 53 complete communication with each other through the bus 54. . Communication interface 52 can be used for information transfer between the electronic device and the outside. The processor 51 can call the logic instructions in the memory 53 to perform the physical layer software automated test method of the above embodiment.

In addition, the logic instructions in the memory 53 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network) The device or the like) performs all or part of the steps of the method described in various embodiments of the present disclosure. The foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. a medium that can store program code, or It is a transient storage medium.

While the preferred embodiment of the present disclosure has been disclosed for purposes of illustration, those skilled in the art will recognize that various modifications, additions and substitutions are possible, and the scope of the present disclosure should not be limited to the embodiments described above.

Industrial applicability

The physical layer software automatic testing method and device of the present disclosure can complete comprehensive physical layer software automated testing, realize continuous integration of physical layer software, and high reliability.

Claims

A physical layer software automated test method, comprising:

The parameter generator batch generates multiple sets of use case parameters;

The algorithm simulator respectively generates test cases corresponding to each set of use case parameters;

The test agent tests the physical layer software to be tested based on the test case;

The test client announces the test results.
The method of claim 1 wherein before the test agent tests the physical layer software to be tested based on the test case, the method further comprises:

The parameter converter formats the interface use case parameters in each test case according to the interface format between the physical layer and the upper layer.
The method of claim 1 or 2, wherein the parameter generator batch generates a plurality of sets of use case parameters, including:

The parameter generator respectively generates use case parameters corresponding to each application scenario of each channel according to parameters of each channel of the physical layer traversed in each application scenario.
The method of claim 1 or 2, wherein

The test case includes: input data, a set of use case parameters, and an output reference;

The algorithm simulator respectively generates test cases corresponding to each set of use case parameters, including:

The algorithm simulator runs based on the set of use case parameters and generates input data and output references corresponding to the set of use case parameters during operation.
The method of claim 4 wherein said test agent tests based on said test case physical layer software to be tested, comprising:

The test agent tests the physical layer software to be tested running on the physical layer or the simulated physical layer based on the test case, and outputs the test result.
The method of claim 5 wherein said test agent tests based on said test case physical layer software to be tested, comprising:

The test agent reads in input data and use case parameters in the test case;

The test agent invokes the physical layer software to be tested, performs testing, and generates an output result;

The test agent compares the output result with an output reference in the test case, and if the output result is the same as the output reference, the test result is a test pass if the output result and the output The reference is not the same, the test result is that the test does not pass.
A physical layer software automated test device comprising:

Parameter generator, set to batch generate multiple sets of use case parameters;

The algorithm simulator is configured to respectively generate test cases corresponding to each set of use case parameters;

a test agent configured to test the physical layer software to be tested based on the test case;

Test the client and set it to publish the test results.
The apparatus of claim 7 wherein said apparatus further comprises a parameter converter;

The parameter converter is configured to format the interface use case parameters in each test case according to an interface format between the physical layer and the upper layer before the test agent tests the physical layer software to be tested according to the test case .
The apparatus according to claim 7 or 8, wherein

The parameter generator is configured to generate use case parameters corresponding to each application scenario of each channel according to parameters of each channel of the physical layer traversed in each application scenario.
The apparatus according to claim 7 or 8, wherein

The test case includes: input data, a set of use case parameters, and an output reference;

The algorithm simulator is configured to run based on the set of use case parameters, and generate input data and an output reference corresponding to the set of use case parameters during operation.
The device of claim 10, wherein

The test agent is configured to invoke a test based on the test case to test the physical layer software to be tested running on the physical layer or the simulated physical layer, and output the test result.
The device of claim 11 wherein

The test agent is configured to read input data and use case parameters in the test case, call the physical layer software to be tested, execute the test, and generate an output result; and output the output and the test case Referring to the comparison, if the output result is the same as the output reference, the test result is a test pass, and if the output result is not the same as the output reference, the test result is a test fail.
A non-transitory storage medium storing computer executable instructions, the computer executable instructions being arranged to perform the physical layer software automated test method of any of claims 1-6.
A computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions that, when executed by a computer, cause the computer to execute The physical layer software automated test method according to any one of claims 1-6.
An electronic device comprising at least one processor and a memory communicatively coupled to the at least one processor, the memory for storing instructions executable by the at least one processor, the instructions being processed by the at least one When executed, the at least one processor is caused to perform the physical layer software automated test method of any one of claims 1-6.