A test software framework building method, device and equipment and storage medium

Abstract

The application discloses a test software framework building method and device, equipment and a storage medium. The method comprises the following steps: creating a test component interface; the test component interface is used for receiving a software test request sent by a user and sending a test result corresponding to the software test request to the user; adding test tools of multiple target types into a target database; creating a corresponding test component for each type of test tool, so as to generate a calling command of the corresponding test tool according to the software test request by using the test component, so that the test tool generates the corresponding test result by running software test. The test component interface uniformly receives the software test request sent by the user, the differences between various types of test software can be shielded, the calling of various types of test tools can be realized by creating the test component corresponding to the test tool, and efficient and convenient software test is realized.

Description

Technical Field

[0001] This invention relates to the field of computer system technology, and in particular to a method, apparatus, device, and storage medium for building a test software framework. Background Technology

[0002] During the evaluation phase of various projects, engineers from different fields often need to perform basic functional tests on products. For example, after optimizing optical components, optical engineers typically need to test the product's functionality. If customer-specified testing software is unavailable, or if multiple testing software programs need to be used collaboratively, it presents a significant challenge for engineers in each field. The functional testing process can be abstracted into two parts: sending commands and receiving results. However, the specific testing methods differ depending on the chip or product. Examples include customer-specified software, serial port mode, and ADB mode. Sometimes, even within the same product, different manufacturers' chips or software are used, resulting in collaborative development by different companies. This leads to situations where different functions within a project require different testing software, making even standardizing the software version a massive task for each engineer. Therefore, achieving efficient and convenient software testing is a pressing issue that needs to be addressed. Summary of the Invention

[0003] In view of this, the purpose of this invention is to provide a method, apparatus, device, and medium for building a test software framework, which can achieve efficient and convenient software testing. The specific solution is as follows:

[0004] Firstly, this application discloses a method for building a test software framework, including:

[0005] Create a test component interface; the test component interface is used to receive software test requests sent by users and send the test results corresponding to the software test requests to users;

[0006] Add testing tools for multiple target types to the target database;

[0007] A corresponding test component is created for each type of test tool, and the test component is used to generate the corresponding calling command of the test tool according to the software test request, so that the test tool generates the corresponding test result by running the software test.

[0008] Optionally, the interface for creating test components includes:

[0009] Create a generic test component interface and define the input and output formats of the test component interface so that the test results corresponding to the software test request can be sent to the user in accordance with the output format.

[0010] Optionally, the interface for creating test components includes:

[0011] The user interface is designed using the tkinter library in Python so that the user-sent software test requests can be obtained through the designed user interface and the test component interface, and the test results corresponding to the software test requests can be displayed through the user interface and the test component interface.

[0012] Optionally, the method for building the test software framework further includes:

[0013] Configure the user interface, the test component, and the test tool to report logs accordingly, so as to obtain the running logs of the user interface, the test component, and the test tool during the operation of the test software framework.

[0014] Optionally, the addition of multiple target types of testing tools to the target database includes:

[0015] Obtain parameter information for all user-to-be-tested items, and determine the target type testing tool corresponding to each user-to-be-tested item based on the parameter information;

[0016] Add the testing tool to the target database corresponding to the testing software framework.

[0017] Optionally, the step of creating corresponding test components for each type of test tool includes:

[0018] Based on the logical characteristics of the testing tools, define the command sending method for each testing tool;

[0019] Based on the command sending method, the corresponding test component is generated, and according to the name of the test item and the test tool corresponding to the test item, a first mapping relationship between the name of the test item and the corresponding test component, and a second mapping relationship between the test component and the corresponding test tool are created.

[0020] Optionally, the step of using the testing component to generate the corresponding invocation command for the testing tool based on the software testing request includes:

[0021] Extract the names of the items to be tested contained in the software test request;

[0022] Based on the name of the item to be tested, the target test component and target test tool corresponding to the software test request are determined by querying the first mapping relationship and the second mapping relationship;

[0023] The target test component is used to generate the corresponding invocation command and send it to the target test tool.

[0024] Secondly, this application discloses a test software framework construction apparatus, comprising:

[0025] An interface creation module is used to create test component interfaces; the test component interfaces are used to receive software test requests sent by users and send the test results corresponding to the software test requests to users.

[0026] The test tool addition module is used to add test tools of various target types to the target database.

[0027] The test component creation module is used to create a corresponding test component for each type of test tool, so as to use the test component to generate the corresponding calling command of the test tool according to the software test request, so that the test tool can generate the corresponding test result by running the software test.

[0028] Thirdly, this application discloses an electronic device, including:

[0029] Memory, used to store computer programs;

[0030] A processor is used to execute the computer program to implement the aforementioned test software framework construction method.

[0031] Fourthly, this application discloses a computer-readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements the aforementioned test software framework construction method.

[0032] In this application, a test component interface is created. This interface receives software test requests from users and sends the corresponding test results to the users. Multiple target-type test tools are added to the target database. A corresponding test component is created for each type of test tool, and the test component generates a corresponding calling command for the test tool based on the software test request, so that the test tool can generate the corresponding test results by running the software test. As can be seen, by creating a unified test component interface to receive software test requests from users, and then using the test component to generate the corresponding calling command for the software test request, the test tool corresponding to the project to be tested can be called, thus achieving the testing of the project. By uniformly receiving software test requests from users through the test component interface, the differences between various types of test software can be masked, providing users with a unified test software. From the user's perspective, the test software is naturally integrated, improving the convenience of software testing. Furthermore, by creating test components corresponding to the test tools, various test tools can be called, providing software engineers with an easily manageable and extensible design framework, simplifying communication and time costs between different fields, and achieving efficient and convenient software testing. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0034] Figure 1 A flowchart illustrating a method for building a test software framework provided in this application;

[0035] Figure 2 A specific Tkinter library interface diagram is provided for this application;

[0036] Figure 3 This application provides a specific runtime sequence diagram of test software;

[0037] Figure 4 This application provides a specific test software framework structure diagram;

[0038] Figure 5 A schematic diagram of a test software framework building device provided in this application;

[0039] Figure 6 This application provides a structural diagram of an electronic device. Detailed Implementation

[0040] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0041] In existing technologies, test engineers need to find different testing software to test different functions when conducting project testing, which reduces testing efficiency. To overcome the above technical problems, this application proposes a method for building a test software framework, which can achieve efficient and convenient software testing.

[0042] This application discloses a method for building a test software framework. (See also...) Figure 1 As shown, the method may include the following steps:

[0043] Step S11: Create a test component interface; the test component interface is used to receive software test requests sent by users and send the test results corresponding to the software test requests to users.

[0044] In this embodiment, the test software framework is specifically built based on Python. Python, as a weakly typed, interpreted high-level programming language, has low requirements for beginners, excellent cross-platform compatibility, and a short development cycle. Using an object-oriented modular development approach, coupled with Python's weak typing, it exhibits excellent compatibility with various scripting software (*.exe, *.bat, *.sh, etc.). Since Python can directly call other software or scripts, a general-purpose test component interface is designed based on Python. The input of this test component interface is the software test request sent by the user, and the output is the test result corresponding to the software test request.

[0045] In this embodiment, creating a test component interface may include: creating a general test component interface and defining the input and output formats of the test component interface so as to send the test results corresponding to the software test request to the user according to the output format. Specifically, the input format of the test component interface can be defined as the name of the project to be tested, and the output return value is the test result. The output format defaults to outputting a string when not configured. By configuring the output format, the corresponding return value format can be output. For example, if the output format is defined as a quantity value, the corresponding target quantity value can be obtained as the test result output according to a preset threshold. Or, if the output format is defined as a status parameter, the status parameters in the test result data can be extracted as the test result output.

[0046] In this embodiment, creating the test component interface may include: designing a user interface using Python's tkinter library, so as to obtain software test requests sent by users through the designed user interface and the test component interface, and display the test results corresponding to the software test requests through the user interface and the test component interface. That is, the user interface (UI) is mainly developed using Python's built-in Tkinter library, which is lightweight and has good cross-platform compatibility. The software library interface is as follows... Figure 2 As shown, by designing this user interface in conjunction with the aforementioned test component interface, the system can acquire software test requests sent by users and display test results. Specifically, the test component sends test result information to the test framework via return values ​​defined in the interface. The test framework then displays the test results through the UI, forming a closed-loop test process. The specific return value format can be customized by refactoring the component interface and the UI to display a variety of information types.

[0047] Step S12: Add test tools for various target types to the target database.

[0048] In this embodiment, multiple target-type test tools are added to the target database corresponding to the test software framework. Specifically, existing test tools for different functional tests are added to the target database of the test software framework. This can be done by adding the entire test tool to the database, or simply by adding the URL of the test tool to the database; the test tool can then be called locally or online.

[0049] In this embodiment, adding multiple target type testing tools to the target database may include: obtaining parameter information for all user-to-be-tested items, and determining the target type testing tool corresponding to each user-to-be-tested item based on the parameter information; and adding the testing tools to the target database corresponding to the testing software framework. Specifically, this can be achieved by first obtaining parameter information for user-to-be-tested items, determining the target type testing tool corresponding to each user-to-be-tested item based on the parameter information, where one user-to-be-tested item may correspond to one testing tool or multiple testing tools. After determining the testing tools, these testing tools are added to the target database corresponding to the testing software framework.

[0050] Step S13: Create a corresponding test component for each type of test tool, and use the test component to generate the corresponding call command for the test tool according to the software test request, so that the test tool generates the corresponding test result by running the software test.

[0051] In this embodiment, it can be understood that the essence of the testing process is sending commands, receiving results, and analyzing results. The testing software framework needs to know the commands sent and the final results. However, due to the personalized nature of command sending methods, different calling commands are required for different testing tools. Therefore, corresponding testing components are created for each type of testing tool. Each testing component is designed with its own internal business logic tailored to the specific needs of the corresponding testing tool. Version management, test script development and maintenance, and environment configuration are handled by professional software engineers. The specific maintenance of the software is isolated from the user. Furthermore, leveraging Python's characteristics as an interpreted and weakly typed programming language, the testing software is modularized to adapt to the testing software requirements of different projects.

[0052] In this embodiment, creating a corresponding test component for each type of test tool may include: defining a command sending method for each test tool based on its logical characteristics; generating a corresponding test component based on the command sending method; and creating a first mapping relationship between the name of the test item and the corresponding test component, and a second mapping relationship between the test component and the corresponding test tool, based on the name of the test item and the test tool corresponding to the test item. That is, in order to enable the invocation of the test component corresponding to the software test request after receiving a user's software test request, and thus the invocation of the corresponding test tool, it is necessary to establish a first mapping relationship between the name of the test item and the corresponding test component, and a second mapping relationship between the test component and the corresponding test tool. Dynamic expansion of different test tools can be achieved by configuring test components, allowing for the direct expansion of test tools without recompilation.

[0053] In this embodiment, the step of using the testing component to generate the corresponding invocation command for the testing tool based on the software testing request may include: extracting the name of the item to be tested contained in the software testing request; determining the target testing component and target testing tool corresponding to the software testing request based on the name of the item to be tested by querying the first mapping relationship and the second mapping relationship; and generating the corresponding invocation command using the target testing component and sending it to the target testing tool. Figure 3 As shown in the test software runtime diagram, the user sends a software test request to the test component library through the user interface and the test component interface. The test component library queries the mapping relationship according to the test software request to call the corresponding target test component to generate the call command, and then sends the call command to the corresponding personalized test tool. After the test tool generates the test results, it feeds them back to the test component library, which then displays the test results to the user through the user interface and the software test interface.

[0054] In this embodiment, the method for building the test software framework may further include: configuring corresponding log reporting for the user interface, the test components, and the test tools, so as to obtain the running logs of the user interface, the test components, and the test tools during the operation of the test software framework. That is, as follows... Figure 3 As shown, the log records the operation of the user interface, test components, and test tools, and displays the recorded logs to the user through the user interface.

[0055] further, Figure 4The diagram shows the structure of the test software framework in this embodiment, which includes six parts: front-end UI, presentation layer, business layer, data layer, database, and runtime environment. The front-end UI is a user interface designed based on Tkinter. The presentation layer is used for user interaction. The business layer is used for test component management, system settings, and other business operations. The data layer performs data reading and writing. The database is used to store data, including test tools. The runtime environment includes, but is not limited to, Windows and Linux environments.

[0056] As can be seen from the above, this embodiment creates a test component interface; the test component interface is used to receive software test requests sent by users and send the test results corresponding to the software test requests to users; it adds multiple target types of test tools to the target database; and it creates corresponding test components for each type of test tool, so that the test components can generate corresponding calling commands for the test tools according to the software test requests, so that the test tools can generate the corresponding test results by running software tests. As can be seen from the above, by creating a unified test component interface to receive software test requests sent by users, and then using the test components to generate calling commands corresponding to the software test requests, the calling commands can be used to call the test tools corresponding to the projects that need to be tested, thereby realizing the testing of the test projects; by uniformly receiving software test requests sent by users through the test component interface, the differences between various types of test software can be masked, providing users with a unified test software. From the user's perspective, the test software is naturally integrated, improving the convenience of software testing. Furthermore, by creating test components corresponding to the test tools, various test tools can be called, providing software engineers with an easily manageable and extensible design framework, simplifying communication and time costs between different fields.

[0057] Accordingly, this application also discloses a test software framework building device, see [link to relevant documentation]. Figure 5 As shown, the device includes:

[0058] The interface creation module 11 is used to create a test component interface; the test component interface is used to receive software test requests sent by users and send the test results corresponding to the software test requests to users.

[0059] Test tool addition module 12 is used to add test tools of various target types to the target database;

[0060] The test component creation module 13 is used to create a corresponding test component for each type of test tool, so as to use the test component to generate the corresponding calling command of the test tool according to the software test request, so that the test tool generates the corresponding test result by running the software test.

[0061] As can be seen from the above, this embodiment creates a test component interface; the test component interface is used to receive software test requests sent by users and send the test results corresponding to the software test requests to users; it adds multiple target types of test tools to the target database; and it creates corresponding test components for each type of test tool, so that the test components can generate corresponding calling commands for the test tools according to the software test requests, so that the test tools can generate the corresponding test results by running software tests. As can be seen from the above, by creating a unified test component interface to receive software test requests sent by users, and then using the test components to generate calling commands corresponding to the software test requests, the calling commands can be used to call the test tools corresponding to the projects that need to be tested, thereby realizing the testing of the test projects; by uniformly receiving software test requests sent by users through the test component interface, the differences between various types of test software can be masked, providing users with a unified test software. From the user's perspective, the test software is naturally integrated, improving the convenience of software testing. Furthermore, by creating test components corresponding to the test tools, various test tools can be called, providing software engineers with an easily manageable and extensible design framework, simplifying communication and time costs between different fields.

[0062] In some specific embodiments, the interface creation module 11 can be used to create a general test component interface and define the input and output formats of the test component interface so as to send the test results corresponding to the software test request to the user in accordance with the output format.

[0063] In some specific embodiments, the test software framework building device may specifically include:

[0064] The user interface design unit is used to design the user interface using the tkinter library in Python, so as to obtain the software test request sent by the user through the designed user interface and the test component interface, and display the test results corresponding to the software test request through the user interface and the test component interface.

[0065] In some specific embodiments, the test software framework building device may specifically include:

[0066] The log reporting configuration unit is used to configure the user interface, the test component, and the test tool to report logs respectively, so as to obtain the running logs of the user interface, the test component, and the test tool during the operation of the test software framework.

[0067] In some specific embodiments, the test tool adding module 12 may specifically include:

[0068] The test tool determination unit is used to acquire parameter information of all the user's test items and determine the target type of test tool corresponding to each test item based on the parameter information.

[0069] The test tool adding unit is used to add the test tool to the target database corresponding to the test software framework.

[0070] In some specific embodiments, the test component creation module 13 may specifically include:

[0071] The command sending method definition unit is used to define the command sending method for calling the test tool for each test tool according to the logical characteristics of the test tool;

[0072] The mapping relationship creation unit is used to generate the corresponding test component based on the command sending method, and to create a first mapping relationship between the name of the test item and the corresponding test component, and a second mapping relationship between the test component and the corresponding test tool, according to the name of the test item and the test tool corresponding to the test item.

[0073] In some specific embodiments, the testing component is used to extract the name of the item to be tested contained in the software testing request; determine the target testing component and target testing tool corresponding to the software testing request by querying the first mapping relationship and the second mapping relationship based on the name of the item to be tested; and generate a corresponding calling command using the target testing component and send it to the target testing tool.

[0074] Furthermore, this application also discloses an electronic device, see [link to relevant documentation]. Figure 6 As shown, the content in the figure should not be considered as any limitation on the scope of use of this application.

[0075] Figure 6 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the test software framework construction method disclosed in any of the foregoing embodiments.

[0076] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0077] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon include operating system 221, computer program 222 and data 223 including test components, etc., and the storage method can be temporary storage or permanent storage.

[0078] The operating system 221 manages and controls the various hardware devices on the electronic device 20 and the computer program 222 to enable the processor 21 to perform calculations and processing on the massive amounts of data 223 in the memory 22. The operating system 221 can be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the test software framework construction method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0079] Furthermore, this application also discloses a computer storage medium storing computer-executable instructions. When the computer-executable instructions are loaded and executed by a processor, they implement the test software framework construction method steps disclosed in any of the foregoing embodiments.

[0080] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0081] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0082] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, 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 said element.

[0083] The present invention has provided a detailed description of a method, apparatus, device, and medium for building a test software framework. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for building a test software framework, characterized in that, include: Create a test component interface; The test component interface is used to receive software test requests sent by users and send the test results corresponding to the software test requests to users. Add testing tools for multiple target types to the target database; A corresponding test component is created for each type of test tool, and the test component is used to generate the corresponding calling command of the test tool according to the software test request, so that the test tool generates the corresponding test result by running the software test; The software test request includes the name of the item to be tested; The method of adding multiple target types of testing tools to the target database includes: Obtain parameter information for all user-defined test items, and determine the target type testing tool for each test item based on the parameter information; add the testing tool to the target database corresponding to the test software framework; The step of creating corresponding test components for each type of test tool includes: Based on the logical characteristics of the testing tools, define the command sending method for each testing tool; Based on the command sending method, the corresponding test component is generated, and according to the name of the project to be tested and the test tool corresponding to the project to be tested, a first mapping relationship between the name of the project to be tested and the corresponding test component, and a second mapping relationship between the test component and the corresponding test tool are created. The step of using the testing component to generate the corresponding invocation command for the testing tool based on the software testing request includes: Extract the names of the items to be tested contained in the software test request; Based on the name of the item to be tested, the target test component and target test tool corresponding to the software test request are determined by querying the first mapping relationship and the second mapping relationship; The target test component generates a corresponding invocation command and sends it to the target test tool.

2. The method for building a test software framework according to claim 1, characterized in that, The interface for creating test components includes: Create a generic test component interface and define the input and output formats of the test component interface so that the test results corresponding to the software test request can be sent to the user according to the output format.

3. The method for building a test software framework according to claim 1, characterized in that, The interface for creating test components includes: The user interface is designed using the tkinter library in Python so that the user-sent software test requests can be obtained through the designed user interface and the test component interface, and the test results corresponding to the software test requests can be displayed through the user interface and the test component interface.

4. The method for building a test software framework according to claim 3, characterized in that, Also includes: Configure the user interface, the test component, and the test tool with corresponding log reporting settings so that the running logs of the user interface, the test component, and the test tool can be obtained during the operation of the test software framework.

5. A test software framework construction device, characterized in that, include: The interface creation module is used to create test component interfaces; The test component interface is used to receive software test requests sent by users and send the test results corresponding to the software test requests to users. The test tool addition module is used to add test tools of various target types to the target database. The test component creation module is used to create a corresponding test component for each type of test tool, so as to use the test component to generate the corresponding calling command of the test tool according to the software test request, so that the test tool generates the corresponding test result by running the software test; The software test request includes the name of the item to be tested; The test tool adding module includes: The test tool determination unit is used to acquire parameter information of all the user's test items and determine the test tool of the target type corresponding to each test item based on the parameter information; the test tool addition unit is used to add the test tool to the target database corresponding to the test software framework. The test component creation module includes: The command sending method definition unit is used to define the command sending method for calling the test tool for each test tool according to the logical characteristics of the test tool; The mapping relationship creation unit is used to generate the corresponding test component based on the command sending method, and to create a first mapping relationship between the name of the test item and the corresponding test component, and a second mapping relationship between the test component and the corresponding test tool, according to the name of the test item and the test tool corresponding to the test item. The testing component is used to extract the name of the item to be tested contained in the software testing request; determine the target testing component and target testing tool corresponding to the software testing request by querying the first mapping relationship and the second mapping relationship based on the name of the item to be tested; and generate the corresponding calling command using the target testing component and send it to the target testing tool.

6. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the test software framework construction method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, Used to store computer programs; wherein the computer programs, when executed by a processor, implement the test software framework construction method as described in any one of claims 1 to 4.

Images