Establishment method of automatic test system, computer readable medium and electronic equipment

Through the construction method of the automated test system, the scheduling framework and UI interface modules are used to solve the problem that the existing technology cannot automatically control multiple devices and software modules, and the control and function combination of multiple devices and software modules of the automated test system is realized. , improves testing efficiency.

CN118897798APending Publication Date: 2024-11-05SHANGHAI SIEMENS CIRCUIT PROTECTION SYST
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410931117.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-11
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

The prior art cannot support the control of multiple devices and/or software modules, and combine their functions to automatically complete the test as needed, resulting in the need to manually set up multiple hardware devices and software in the development of embedded devices to create a test environment, affecting the test. efficiency.

Method used

Provides a method for building an automated test system, using the scheduling framework to convert abstract files of hardware devices/software modules into description files, and implements the execution of user input test cases through the UI interface and data processing module, supporting at least one hardware device, Testing of software modules, hardware device combinations or software module combinations.

Benefits of technology

The automated test system controls and function combination of multiple devices and software modules is realized, which improves testing efficiency, reduces manual intervention, and can automatically execute tests based on test cases entered by users.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118897798A_ABST
    Figure CN118897798A_ABST
Patent Text Reader

Abstract

The invention provides a building method of an automatic test system, a computer readable medium and electronic equipment, a scheduling framework is preset on the automatic test system, and the scheduling framework is used for executing a test according to a test case input by a user; the building method comprises the following steps: storing an abstract file of hardware equipment / software module to a path specified by a scheduling framework, and starting the scheduling framework; the abstract file of the hardware equipment / software module is a control method abstract file related to the control of the hardware equipment / software module; calling a scheduling framework to traverse all the abstract files, and converting the abstract files into description files which can be identified by the scheduling framework, so that the scheduling framework executes the test description files according to the test case input by the user to describe the driving function of the hardware equipment / software module; and receiving the test case input by the user, and executing the test case. Based on the scheme, various devices and / or software modules can be controlled, and the functions of the devices and / or software modules are combined according to needs to automatically complete testing.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of automated testing technology, and in particular to a method for building an automated testing system, a computer-readable medium, and an electronic device. Background Art

[0002] Automated testing methods and automated testing frameworks are widely used in the process of software automated testing. However, for the development of embedded devices, taking the development of residual current detection devices as an example, in order to complete the test of a specific function, it is often necessary to manually set up multiple hardware devices and / or software to create a safe and effective test environment for functional verification. However, the prior art does not have an automated testing method that can support the control of at least one hardware device and / or software module and automatically complete the test by combining its functions as needed, which has become a technical problem that needs to be solved urgently by those skilled in the art. Summary of the invention

[0003] In view of this, the present invention provides a method for building an automated testing system, a computer-readable medium, and an electronic device, which can support the control of multiple devices and / or software modules, and combine their functions as needed to automatically complete testing.

[0004] In a first aspect, an embodiment of the present invention provides a method for building an automated testing system, wherein a scheduling framework is pre-set on the automated testing system, and the scheduling framework is used to execute tests according to test cases input by a user; the building method comprises: storing an abstract file of a hardware device / software module to a path specified by the scheduling framework, and starting the scheduling framework; the abstract file of the hardware device / software module is an abstract file of a control method related to its control; calling the scheduling framework to traverse all the abstract files, and converting the abstract files into description files recognizable by the scheduling framework, so that the scheduling framework executes the test according to the test cases input by the user; the description file is used to describe the driving function of the hardware device / software module; receiving the test cases input by the user, and executing the test cases; wherein the test cases are cases that support at least one hardware device, at least one software module, at least two hardware device combinations, at least two software module combinations, or at least one hardware device and at least one software module combination, and complete the test.

[0005] In one possible implementation, the abstract file of the hardware device / software module includes annotations of the control method abstract file, and the annotations are used by the scheduling framework to identify the control method of the hardware device / software module during the process of traversing all the abstract files, and the annotations include a functional description of the control method, a detailed description of the input variable type, and a description of the return value.

[0006] In a possible implementation, the step of calling the scheduling framework to traverse all the abstract files and converting the abstract files into description files recognizable by the scheduling framework includes: reading all the abstract files to identify the attribute information of the hardware device / software module and the annotations about the attribute information; the categories of the attribute information of the hardware device / software module include the type of the hardware device / software module, the name of the hardware device / software module, the function of the hardware device / software module and the parameters related to the function; using the annotations, generating a description file recognizable by the scheduling framework and filling it into the scheduling framework.

[0007] In a possible implementation, the scheduling framework includes a UI interface module and a data processing module; the UI interface module is used to draw and display the UI interface; the UI interface is provided with a plurality of execution buttons and selection boxes with different attribute information, each of the execution buttons is used to receive and execute different instructions, and each of the attribute information selection boxes is used to receive attribute information input by the user; after the description file is filled into the scheduling framework, the construction method further includes: calling the data processing module to parse the description file, and loading the parsed attribute information into the global data, and classifying the parsed attribute information according to the categories set in the global data, so that the user can select different attribute information through the UI interface; the test case includes at least one test event, and the test event is composed of at least one attribute information extracted by the user.

[0008] In a possible implementation, the scheduling framework further includes a test execution module and a log reporting module; the test execution module is used to execute the test case; and the log reporting module is used to record the test log of the scheduling framework.

[0009] In a possible implementation, the execution button includes a device search button, a test case load button, a test case output button, a test case run button, a device add button and a test case add button; a hardware device / software module type selection box and a hardware device / software module name selection box are provided under the device add button, the hardware device / software module type selection box is provided with a variety of hardware device / software module types for users to choose, and the hardware device / software module name selection box is provided with a variety of hardware device / software module names for users to choose; a hardware device / software module name selection box, a hardware device / software module function selection box and a function-related parameter selection box are provided under the test case add button; wherein, the device search button is used to receive a device search instruction to the scheduling framework so that The scheduling framework traverses all the abstract files and converts the abstract files into description files recognizable by the scheduling framework; the test case loading button is used to receive test case loading instructions; the test case output button is used to receive test case output instructions; the test case running button is used to receive test case running instructions; the device adding button is used to receive device adding instructions and activate the type selection box and name selection box of the hardware device / software module set thereunder; the test case adding button is used to receive several test case adding instructions and activate the name selection box, function selection box and function-related parameter selection box of the hardware device / software module set thereunder; wherein, each time a test case adding instruction is received, a corresponding test event is added, and all test events constitute the implementation steps of the control method of the hardware device / software module.

[0010] In a possible implementation, the steps of receiving a test case input by a user and executing the test case include: receiving a device adding instruction input by the user through the device adding button, activating a type selection box and a name selection box of a hardware device / software module set under the device adding button; receiving a type and a name of a hardware device / software module selected by the user through the type selection box and the name selection box of the hardware device / software module; receiving several test case adding instructions input by the user through the test case adding button, activating a name selection box, a function selection box and a parameter selection box related to the function of the hardware device / software module set under the test case adding button; receiving several test event adding instructions input by the user through the test event adding button (26), activating a name selection box, a function selection box and a parameter selection box related to the function of the hardware device / software module corresponding to each test event; receiving a name, a function and a parameter related to the function of the hardware device / software module corresponding to each test event and corresponding to each test user adding instruction required by the user through the name selection box, the function selection box and the parameter selection box related to the function of the hardware device / software module corresponding to each test event, so as to form a test case; receiving a test case running instruction through the test case running button, and executing the formed test case.

[0011] In a possible implementation, the step of receiving a test case input by a user and executing the test case also includes: receiving a device addition instruction input by the user through the device addition button, activating the type selection box and name selection box of the hardware device / software module set under the device addition button, and receiving the type and name of the hardware device / software module selected by the user through the type selection box and name selection box of the hardware device / software module, receiving a test case loading instruction through the test case loading button, searching whether there is a test case consistent with the type and name of the hardware device / software module, and if so, loading the test case.

[0012] In a possible implementation, the construction method further includes: receiving a test case output instruction input by a user through the test case output button, and outputting a test log of the test case.

[0013] In a second aspect, an embodiment of the present invention provides a computer-readable medium having computer-readable instructions stored thereon. When the computer-readable instructions are executed by a processor, the processor executes the steps in the method for building an automated testing system as described above.

[0014] A third method, an embodiment of the present invention provides an electronic device, comprising: at least one memory configured to store computer-readable code; and at least one processor configured to call the computer-readable code to execute the steps in the method for building an automated testing system as described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 This is a flow chart of a method for building an automated testing system provided in an embodiment of the present application;

[0016] Figure 2 This is a schematic diagram of an implementation process of S12 in the method for building an automated testing system provided in an embodiment of the present application;

[0017] Figure 3 This is an exemplary schematic diagram of the UI interface in the automated testing system provided in an embodiment of the present application.

[0018] List of reference numerals:

[0019] 21 Device search button 22 Test case load button 23 Test case output button 24 Test case run button 25 Device Add Button 26 Test event add button 251 Hardware device / software module type selection box 252 Hardware device / software module name selection box 261 Hardware device / software module name selection box 262 Function selection box for hardware devices / software modules 263 Function-related parameter selection box DETAILED DESCRIPTION

[0020] The drawings in the embodiments clearly and in detail describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the embodiments of the present application should fall within the scope of protection of the embodiments of the present application.

[0021] It should be understood that the terms "first", "second", and "third" in the claims, specifications, and drawings of the present disclosure are used to distinguish different objects rather than to describe a specific order. The terms "include" and "comprise" used in the specifications and claims of the present disclosure indicate the presence of the described features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their collections.

[0022] It should also be understood that the terms used in this disclosure are only for the purpose of describing specific embodiments and are not intended to limit the disclosure. As used in this disclosure and claims, the singular forms of "a", "an", and "the" are intended to include the plural forms unless the context clearly indicates otherwise. It should also be further understood that the term "and / or" used in this disclosure and claims refers to any combination of one or more of the associated listed items and all possible combinations, including these combinations.

[0023] In order to complete the test of a specific function, it is often necessary to manually set up multiple devices and / or software modules to create a safe and effective test environment for function verification. However, the prior art cannot support the control of multiple devices and / or software modules, and automatically complete the test by combining their functions as needed. To solve this technical problem, the present application provides a method for building an automated testing system. In this embodiment, a scheduling framework is pre-set on the automated testing system, and the scheduling framework is used to execute tests according to test cases input by the user, and the test cases are cases that support at least one of the hardware devices, at least one software module, at least two of the hardware devices, at least two software modules, or at least one hardware device and at least one software module, and complete the test.

[0024] See also Figure 1 , which is a flow chart of the method for building an automated test system. Figure 1 As shown, the method for building the automated testing system includes the following steps:

[0025] S11, storing the abstract file of the hardware device / software module in the path specified by the scheduling framework, and starting the scheduling framework. In this embodiment, the abstract file of the hardware device / software module is a control method abstract file related to its control. In other words, the so-called abstract file refers to a hardware device / software module with a communication interface or supporting program control. According to its operation manual or programming manual, the actual device / software module and its supported functions are abstracted through object-oriented programming.

[0026] For example, if the hardware device is a current source device and the program it supports is to support alternating current with an output frequency of 50 Hz and an amplitude of 10 A, then the control program supported by the current source device is written as an abstract file.

[0027] In order to facilitate the scheduling framework to identify abstract files, the abstract file of the hardware device / software module includes comments on the control method abstract file, and the comments are used by the scheduling framework to identify the control method of the hardware device / software module in the process of traversing all the abstract files, and the comments include a functional description of the control method, a detailed description of the input variable type, and a return value description.

[0028] S12, the scheduling framework traverses all the abstract files and converts the abstract files into description files recognizable by the scheduling framework, so that the scheduling framework executes the test according to the test case input by the user. The description file is used to describe the driving function of the hardware device / software module.

[0029] S13, receiving a test case input by a user, and executing the test case. In this embodiment, the test case is a test case that supports at least one of the hardware devices, at least one software module, at least two combinations of the hardware devices, at least two combinations of software modules, or at least one combination of the hardware device and at least one software module, and completes the test.

[0030] In order to facilitate the scheduling framework to recognize the abstract file and separate the scheduling framework from the abstract file in design, see Figure 2 , S12 specifically includes the following steps:

[0031] S121, reading all the abstract files to identify the attribute information of the hardware device / software module and the annotations on the attribute information.

[0032] In this embodiment, the categories of the attribute information of the hardware device / software module include the type of the hardware device / software module, the name of the hardware device / software module, the function of the hardware device / software module and parameters related to the function.

[0033] Take Python as an example; in Python, each control object has some special attributes and methods that make it easier to use and understand the object. The __doc__ attribute is a built-in attribute of an object, which is used to store the object's documentation string. In actual applications, you can read the __doc__ attribute of the control object to get a detailed description of the function, input parameters, and output results in the abstract file.

[0034] Still taking the control current of the current source device as an example, when reading the abstract file, the attribute information of the control current of the current source device and the comments about the attribute information are identified by calling set_current.__doc__.

[0035] S122: Generate a description file that can be recognized by the scheduling framework using the annotation, and fill it into the scheduling framework.

[0036] In practical applications, the description file can be a Json file. Comments are an important means of describing Python module functions and generating module description Json files. All comment requirements should be applied as mandatory requirements in the Python coding process. All comments should be edited in the form of "'comment body'" to support multi-line comments. The comment body can be described according to the pre-set class comment rules and method comment rules according to the categories described.

[0037] Specifically, the class annotation rules require that a brief description of the class's purpose, the author's name, or email address, and the time the class was created should be included, and the description should be mainly in English.

[0038] Specifically, the annotation rules for methods require the method's functional description, input variable types and detailed description, and return value description.

[0039] In order to make the framework design simple, the implementation difficulty low and the test cases easy to execute, the scheduling framework in this embodiment includes a UI interface module, a data processing module, a test execution module and a log reporting module.

[0040] The UI interface module is used to draw and display the UI interface. The UI interface is provided with a plurality of execution buttons and different attribute information selection boxes, each of which is used to receive and execute different instructions, and each of which is used to receive attribute information input by the user.

[0041] In order to make the UI interface easy to implement, in this embodiment, please refer to Figure 3 The execution buttons include a device search button 21, a test case load button 22, a test case output button 23, a test case run button 24, a device add button 25 and a test case add button 26.

[0042] A hardware device / software module type selection box 251 and a hardware device / software module name selection box 252 are provided under the device add button 25. The hardware device / software module type selection box 251 contains a variety of hardware device / software module types for the user to select, and the hardware device / software module name selection box 252 contains a variety of hardware device / software module names for the user to select.

[0043] A hardware device / software module name selection box 261 , a hardware device / software module function selection box 262 , and a function-related parameter selection box 263 are provided under the test case adding button 26 .

[0044] The device search button 21 is used to receive a device search instruction to the scheduling framework, so that the scheduling framework traverses all the abstract files and converts the abstract files into description files recognizable by the scheduling framework.

[0045] The test case loading button 22 is used to receive a test case loading instruction.

[0046] The test case output button 23 is used to receive a test case output instruction.

[0047] The test case execution button 24 is used to receive a test case execution instruction.

[0048] The device adding button 25 is used to receive a device adding instruction and activate the type selection box and name selection box of the hardware device / software module set thereunder.

[0049] The test case addition button 26 is used to receive several test case addition instructions and activate the name selection box, function selection box and function-related parameter selection box of the hardware device / software module set thereunder; wherein, each time a test case addition instruction is received, a corresponding test event is added, and all test events constitute the implementation steps of the control method of the hardware device / software module.

[0050] In order to facilitate users to freely match test cases, after executing S122, the building method further includes:

[0051] S123, the data processing module parses the description file, loads the parsed attribute information into the global data, and classifies the parsed attribute information according to the categories set in the global data, so that the user can select different attribute information through the UI interface. The test case includes at least one test event, and the test event is composed of at least one attribute information extracted by the user. In this embodiment, the category set in the global data is consistent with the category of the attribute information of the hardware device / software module.

[0052] The test execution module is used to execute the test case.

[0053] The log reporting module is used to record the test log of the scheduling framework.

[0054] In order to facilitate users to freely select hardware devices / software modules according to work requirements and form a complete test procedure, S13 specifically includes the following steps:

[0055] S131, receiving a device adding instruction input by a user through the device adding button, and activating a type selection box and a name selection box of a hardware device / software module set under the device adding button.

[0056] S132, receiving the type and name of the hardware device / software module selected by the user through the type selection box and the name selection box of the hardware device / software module.

[0057] S133, receiving several test event adding instructions input by the user through the test event adding button, activating the name selection box, function selection box and function-related parameter selection box of the hardware device / software module corresponding to each test event;

[0058] S134, receiving the user-selected name, function and function-related parameters corresponding to each test user-added instruction corresponding to each test event and required by the user through the name selection box, function selection box and function-related parameter selection box of the hardware device / software module corresponding to each test event, so as to form a test case.

[0059] S135, receiving a test case running instruction through the test case running button, and executing the formed test case.

[0060] S136, receiving a test case output instruction input by a user through the test case output button, and outputting a test log of the test case.

[0061] In order to prevent repeated test cases, after steps S131 and S132, the construction method further includes:

[0062] S133', receiving a test case loading instruction through the test case loading button, and searching whether there is a test case that is consistent with the type and name of the hardware device / software module, if so, loading the test case. If not, proceeding to S133.

[0063] The following mainly describes the test process of test case A, wherein test case A is a test case composed of hardware device B and hardware device C, and test case C is composed of test event 1 and test event 2. The device adding button receives the device adding instruction input by the user, activates the type selection box and name selection box of the hardware device / software module set under the device adding button, and the user selects the name and type corresponding to hardware devices B and C through the name selection box and type selection box of the hardware device / software module. The test case adding button receives several test case adding instructions input by the user, and activates the name selection box, function selection box and function-related parameter selection box of the hardware device / software module set under the test case adding button. The user receives the function and function-related parameters corresponding to the name of the hardware device / software module and required by the user through the name selection box, function selection box and function-related parameter selection box of the hardware device / software module corresponding to test event 1, and receives the function and function-related parameters corresponding to the name of the hardware device / software module and required by the user through the name selection box, function selection box and function-related parameter selection box of the hardware device / software module corresponding to test event 2, thereby forming a test case. The test case running button receives the test case running instruction and executes the formed test case. The test case output button receives the test case output instruction input by the user and outputs the test log of the test case.

[0064] The embodiment of the present application further proposes a computer-readable medium, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor, the processor executes the steps in the method for building an automated testing system as described above.

[0065] At any possible level of technical detail combination, the present application may be a system, method and / or computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present application.

[0066] Computer readable storage medium can be a tangible device that can hold and store instructions used by an instruction execution device. Computer readable storage medium can be, for example, (but not limited to) an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (non-exhaustive list) of computer readable storage medium include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, for example, a punch card or a convex structure in a groove on which instructions are stored, and any suitable combination thereof. The computer readable storage medium used here is not interpreted as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated by a waveguide or other transmission medium (for example, a light pulse by an optical fiber cable), or an electrical signal transmitted by a wire.

[0067] The computer-readable program described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device through a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives a computer-readable program instruction from the network, and forwards the computer-readable program instruction for storage in the computer-readable storage medium in each computing / processing device. The computer program instruction for performing the operation of the present application can be an assembly instruction, an instruction set architecture (ISA) instruction, a machine instruction, a machine-related instruction, a microcode, a firmware instruction, a state setting data, an integrated circuit configuration data, or a source code or object code written in any combination of one or more programming languages, wherein the programming language includes an object-oriented programming language, such as Smalltalk, C++, etc., and a procedural programming language, such as "C" language or similar programming language. Computer readable program instructions can be executed completely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet). In certain embodiments, by using the state information of computer readable program instructions to personalize electronic circuits, such as programmable logic circuits, field programmable gate arrays (FPGAs) or programmable logic arrays (PLAs), the electronic circuits can execute computer readable program instructions, thereby realizing various aspects of the present application.

[0068] The embodiment of the present application also provides an electronic device. The electronic device includes at least one memory and at least one processor, wherein the at least one memory is configured to store computer-readable code. The at least one processor is configured to call the computer-readable code and execute the steps in the method for building an automated test system as described above.

[0069] Among them, at least one processor may include a microprocessor, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), a state machine, etc. Embodiments of computer-readable media include, but are not limited to, floppy disks, CD-ROMs, disks, memory chips, ROMs, RAMs, ASICs, configured processors, all-optical media, all tapes or other magnetic media, or any other medium from which a computer processor can read instructions. In addition, various other forms of computer-readable media can send or carry instructions to a computer, including routers, private or public networks, or other wired and wireless transmission devices or channels. Instructions may include codes in any computer programming language, including C, C++, C language, Visual Basic, java, and JavaScript.

[0070] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary knowledge in the relevant technical field without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application. The nouns and pronouns related to people in this patent application are not limited to specific genders.

Claims

1. A method for building an automated testing system. It is characterized in that The automated testing system is pre-configured with a scheduling framework, which is used to execute tests according to test cases input by a user; the construction method includes: The abstract file of the hardware device / software module is stored in the path specified by the scheduling framework, and the scheduling framework is started; the abstract file of the hardware device / software module is an abstract file of the control method related to its control; Calling the scheduling framework to traverse all the abstract files, converting the abstract files into description files recognizable by the scheduling framework, so that the scheduling framework executes the test according to the test case input by the user. The description file is used to describe the driving function of the hardware device / software module; Receive test cases input by users and execute the test cases; wherein the test cases are test cases that support at least one hardware device, at least one software module, at least two hardware device combinations, at least two software module combinations, or at least one hardware device and at least one software module combination, and complete the test.

2. The method for building an automated testing system according to claim 1, It is characterized in that The abstract file of the hardware device / software module includes comments on the control method abstract file, and the comments are used by the scheduling framework to identify the control method of the hardware device / software module during traversal of all the abstract files, and the comments include a functional description of the control method, a detailed description of the input variable type, and a description of the return value.

3. The method for constructing an automated testing system according to claim 2, It is characterized in that The step of calling the scheduling framework to traverse all the abstract files and converting the abstract files into description files recognizable by the scheduling framework includes: Reading all the abstract files to identify the attribute information of the hardware device / software module and the annotations about the attribute information; the categories of the attribute information of the hardware device / software module include the type of the hardware device / software module, the name of the hardware device / software module, the function of the hardware device / software module and the parameters related to the function; A description file recognizable by the scheduling framework is generated by using the annotations, and is filled into the scheduling framework.

4. The method for constructing an automated testing system according to claim 3, It is characterized in that The scheduling framework includes a UI interface module and a data processing module; The UI interface module is used to draw and display the UI interface; the UI interface is provided with a plurality of execution buttons and different attribute information selection boxes, each of the execution buttons is used to receive and execute different instructions, and each of the attribute information selection boxes is used to receive attribute information input by the user; After the description file is filled into the scheduling framework, the construction method further includes: Call the data processing module to parse the description file, load the parsed attribute information into the global data, and classify the parsed attribute information according to the categories set in the global data, so that the user can select different attribute information through the UI interface; the test case includes at least one test event, and the test event is composed of at least one attribute information extracted by the user.

5. The method for constructing an automated testing system according to claim 4, It is characterized in that The scheduling framework also includes a test execution module and a log reporting module; The test execution module is used to execute the test case; The log reporting module is used to record the test log of the scheduling framework.

6. The method for constructing an automated testing system according to claim 4, It is characterized in that The execution buttons include a device search button (21), a test case load button (22), a test case output button (23), a test case run button (24), a device add button (25) and a test case add button (26); A hardware device / software module type selection box (251) and a hardware device / software module name selection box (252) are provided under the device adding button (25), wherein the hardware device / software module type selection box (251) contains a plurality of hardware device / software module types for the user to select, and the hardware device / software module name selection box (252) contains a plurality of hardware device / software module names for the user to select; A hardware device / software module name selection box (261), a hardware device / software module function selection box (262) and a function-related parameter selection box (263) are provided under the test case adding button (26); The device search button (21) is used to receive a device search instruction to the scheduling framework, so that the scheduling framework traverses all the abstract files and converts the abstract files into description files recognizable by the scheduling framework; the test case load button (22) is used to receive a test case load instruction; the test case output button (23) is used to receive a test case output instruction; the test case run button (24) is used to receive a test case run instruction; the device add button (25) is used to receive a device add instruction and activate the type selection box and name selection box of the hardware device / software module set thereunder; the test event add button (26) is used to receive several test case add instructions and activate the name selection box, function selection box and function-related parameter selection box of the hardware device / software module set thereunder; wherein, each time a test case add instruction is received, a test event is correspondingly added, and all test events constitute the implementation steps of the control method of the hardware device / software module.

7. The method for constructing an automated testing system according to claim 6, It is characterized in that The steps of receiving a test case input by a user and executing the test case include: Receiving a device adding instruction input by a user through the device adding button (25), and activating a type selection box and a name selection box of a hardware device / software module set under the device adding button (25); Receive the type and name of the hardware device / software module selected by the user through the type selection box and name selection box of the hardware device / software module; Receiving a number of test event addition instructions input by the user through the test event addition button (26), activating a name selection box, a function selection box and a parameter selection box related to the function of the hardware device / software module corresponding to each test event; Receive the user-selected name, function and function-related parameters corresponding to each test user-added instruction corresponding to each test event and required by the user through the name selection box, function selection box and function-related parameter selection box of the hardware device / software module corresponding to each test event, so as to form a test case; The test case execution button (24) receives the test case execution instruction and executes the formed test case.

8. The method for constructing an automated testing system according to claim 6, It is characterized in that The step of receiving a test case input by a user and executing the test case also includes: After receiving a device adding instruction input by a user through the device adding button (25), activating a type selection box and a name selection box of a hardware device / software module set under the device adding button (25), and receiving a type and a name of a hardware device / software module selected by a user through the type selection box and the name selection box of the hardware device / software module, A test case loading instruction is received through the test case loading button (22), and a search is performed to determine whether there is a test case that is consistent with the type and name of the hardware device / software module. If so, the test case is loaded.

9. The method for constructing an automated testing system according to claim 7 or 8, It is characterized in that Also includes: The test case output button (23) receives the test case output instruction input by the user, and outputs the test log of the test case.

10. A computer readable medium, It is characterized in that The computer-readable medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the processor executes the steps in the method for building an automated testing system according to any one of claims 1 to 9.

11. An electronic device, include: at least one memory configured to store computer readable code; At least one processor is configured to call the computer readable code to execute the steps in the method for building an automated testing system according to any one of claims 1 to 9.