CN115687162B - Software testing device and method and electronic device - Google Patents

Abstract

The application provides a software testing device, a method, an electronic device and a computer program product, which relate to the technical field of software testing, wherein the software testing device comprises an analysis module and an execution module, wherein the analysis module is used for receiving an input user interface related to a configuration file of a testing scene, analyzing the configuration file, obtaining an operation corresponding to the testing scene, a step corresponding to the operation and a first configuration attribute of the step, and transmitting the operation, the step corresponding to the operation and the first configuration attribute of the step to the execution module; the execution module is used for receiving the operation corresponding to the test scene, the step corresponding to the operation and the first configuration attribute of the step, receiving an input user interface related to target test information, determining the target step corresponding to the target operation and the target operation, and executing software test according to the first configuration attribute of the step, the second configuration attribute of the pre-stored step and the execution function of the target step. The application improves the software testing efficiency.

Description

Software testing equipment, method and electronic equipment

technical field

The present application relates to the technical field of software testing, in particular to a software testing equipment, method, electronic equipment and computer program product.

Background technique

At present, during the development or use of software middleware (hereinafter referred to as middleware), relevant tests need to be carried out, such as smoke test, benchmark test, load test, interface test, stress test and bottleneck test, etc., but considering that middleware needs to support A large number of complex scenarios, therefore, in addition to the above tests, scenario-based tests are also required.

Scenario-based testing includes manual scenario-based testing and automatic scenario-based testing. Manual scenario-based testing is performed by manually inputting options in the terminal, which has the problems of low test efficiency and a waste of a lot of manpower and material resources. However, automatic scenario-based testing has the problem of limited test scenarios. If testers want to add test scenarios, they need to rewrite the code. Therefore, as the number of test scenarios increases, the coupling between the test interface and the test scenario becomes higher. Maintenance costs will also increase.

Contents of the invention

The application provides a software testing device, method, electronic device and computer program product, which are used to solve the problem of low test efficiency in the manual scenario testing of middleware in the prior art and the coupling degree between the testing interface and the testing scenario in the automatic scenario testing high question.

According to the first aspect of the present application, a software testing device is provided, including an analysis module and an execution module, and the execution module is connected to the analysis module;

The parsing module is used to receive the input user interface related to the configuration file of the test scenario, and is also used to parse the configuration file to obtain the operation corresponding to the test scenario, the step corresponding to the operation, and the first step of the step. A configuration attribute, further used to transmit the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step to the execution module;

The execution module is used to receive the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step, and is also used to receive the input user interface related to the target test information, and is also used to The operation corresponding to the test scenario, the step corresponding to the operation, and the target test information determine the target operation and the target step corresponding to the target operation, and is also used to determine the target operation according to the first configuration attribute of the step, the pre-stored A second configuration attribute of the step and an execute function of the target step execute software testing.

According to a second aspect of the present application, a software testing method is provided, including:

a user interface for receiving input related to configuration files for test scenarios and a user interface for input related to target test information;

Parse the configuration file to obtain the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step;

determining a target operation and a target step corresponding to the target operation according to the operation corresponding to the test scenario, the steps corresponding to the operation, and the target test information;

The software test is executed according to the first configuration attribute of the step, the pre-stored second configuration attribute of the step, and the execution function of the target step.

According to a third aspect of the present application, an electronic device is provided, including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute the software testing method as described in the second aspect.

According to a fourth aspect of the present application, a computer program product is provided, including computer programs/instructions, and when the computer programs/instructions are executed by a processor, the software testing method as described in the second aspect is implemented.

In the embodiment of the present application, the parsing module can parse the configuration file of the built test scenario to obtain the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step, and the execution module can The steps and the first configuration attributes of the steps realize automated software testing, improve test efficiency, reduce debugging costs, and save manpower and material resources; and by inputting the configuration files of test scenarios in the analysis module, the construction of rich test scenarios is realized without rewriting Code, and realize the separation of the test interface and the test scene, without adaptation, the coupling between the test interface and the test scene is reduced, and the later maintenance cost will also be reduced.

It should be understood that what is described in this section is not intended to identify key or important features of the embodiments of the application, nor is it intended to limit the scope of the application. Other features of the present application will be easily understood from the following description.

Description of drawings

The accompanying drawings are used to better understand the solution, and do not constitute a limitation to the application. in:

Fig. 1 is one of the schematic structural diagrams of the software testing equipment provided by the embodiment of the present application;

Fig. 2 is the second structural diagram of the software testing equipment provided by the embodiment of the present application;

Fig. 3 is the third structural diagram of the software testing equipment provided by the embodiment of the present application;

Fig. 4 is one of the schematic flow charts of the software testing method provided by the embodiment of the present application;

FIG. 5 is the second schematic flow diagram of the software testing method provided by the embodiment of the present application.

Detailed ways

Exemplary embodiments of the present application are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present application to facilitate understanding, and they should be regarded as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Before proceeding to the description of specific embodiments of the present application, the following description will be made first.

Test scene (scene): A test scene consists of one or more operations.

Action: It is used to represent the specific operation that the client and server need to perform. An operation consists of one or more steps and is the basic unit for building a test scenario.

Step: It is used to represent the smallest execution unit that the server or client can operate, and is the basic unit of construction operations. In general, each step has some configuration properties.

It should be noted that the following embodiments of the present application are applicable to scenario-based testing of middleware, and the specific content of the testing scenarios, operations, and steps involved can be designed by those skilled in the art according to testing requirements, and are not limited here.

Among them, middleware is a general-purpose service software located between platforms such as hardware and operating systems and applications. It provides an environment for running and developing applications on the upper layer, and can help users develop and integrate complex applications flexibly and efficiently. software. Common middleware includes a software development kit (Software Development Kit, SDK), which can be compiled together with some application software, so as to provide some functional interfaces to support the function realization of the application software. For example, the software development kit is compiled into the video software to support the video output function. Therefore, the performance of the software kit (that is, middleware) directly affects the performance of the application software, so in order to ensure the performance of the application software, it is necessary to test the middleware.

An embodiment of the present application provides a software testing device.

As shown in Figure 1, the software testing equipment includes: an analysis module 101 and an execution module 102, and the execution module 102 is connected with the analysis module 101;

The parsing module 101 is used to receive the input user interface related to the configuration file of the test scenario, and is also used to parse the configuration file to obtain the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step, and is also used to submit the configuration file to the execution Module 102 transmits the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step;

The execution module 102 is used to receive the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step, and is also used to receive the input user interface related to the target test information, and is also used to perform the corresponding operation and operation according to the test scenario. The corresponding steps and target test information determine the target operation and the target step corresponding to the target operation, and are also used to execute software testing according to the first configuration attribute of the step, the second configuration attribute of the pre-stored step, and the execution function of the target step.

Among them, the configuration file of the test scenario can be input by the tester in the user interface according to the test requirement. In this way, when the test scenario increases, the tester can modify the configuration file according to the test requirement, so as to build a rich test scenario without rewriting the code , greatly improving test efficiency and reducing debugging costs.

The target test information may be input by the tester on the user interface according to the requirements of this software test.

It should be noted that the user interface for the tester to input the configuration file of the test scenario and the user interface for inputting the target test information may be the same user interface, or they may be different user interfaces. Wherein, the user interface is used to select the address of the configuration file of the test scenario, so that the configuration file of the test scenario can be loaded into the parsing module 101, and is also used to input the specific information content of the target test information at the corresponding option, so that the target test information can be loaded into the execution module 102 .

The second configuration attribute of the step may be an initialization configuration attribute of the step stored in advance by the tester, and specifically may involve configuration attributes of the steps of the server and the client. Likewise, the first configuration attribute of the step may also relate to the configuration attributes of the steps of the server and the client.

Among them, the configuration attribute can be the input parameter of the actual test interface, which is confirmed by the test interface; or it is also used to indicate how to test the configuration item of the actual test interface, such as the number of threads that concurrently call the actual test interface, the actual test interface call and the interval between two test interface calls. The operations corresponding to the test scenario can be understood as the operations that need to be performed in the test scenario; and the steps corresponding to the operations can be understood as the steps that need to be performed in the operation.

It should also be noted that a test scenario can correspond to one or more operations, and an operation can correspond to one or more steps. That is to say, an operation corresponding to a test scenario can be understood as an operation sequence corresponding to a test scenario, and the steps corresponding to an operation can be understood as is the sequence of steps corresponding to the operation.

Wherein, the execution module 102 selects the first configuration attribute and the second configuration attribute corresponding to the target step from the first configuration attribute and the second configuration attribute of the step, so that according to the first configuration attribute and the second configuration attribute of the target step , corresponding to the execution function of the execution target step, to realize the software scenario test set by the tester.

In related technologies, software needs to support scenario-based testing, and scenario-based testing is divided into manual scenario-based testing and automatic scenario-based testing. Among them, manual scenario-based testing has the problems of low test efficiency, increased debugging costs, and waste of manpower and material resources; With the increase of test scenarios, there is a problem of high coupling between test interfaces and test scenarios.

In view of this, an embodiment of the present application provides a software testing device, including an analysis module and an execution module, and the execution module can realize automated software testing according to the operation corresponding to the test scenario obtained by the analysis module, the steps corresponding to the operation, and the first configuration attribute of the step , improve test efficiency, reduce debugging costs, and save manpower and material resources; and by inputting configuration files of test scenarios in the analysis module, the construction of rich test scenarios is realized without rewriting codes, and the separation of test interfaces and test scenarios is achieved without Adaptation, the coupling degree between the test interface and the test scene is reduced, and the maintenance cost in the later stage will also be reduced.

In some optional implementation manners, the target test information includes at least one of the following:

Target test scene identification (SceneID);

target domain identification (DomainID);

The target process ID (ProcessName).

In this embodiment of the present application, the target test scenario identifier may be the name of the target test scenario, which is used to represent the identifier of the test scenario, and the target test scenario identifier determines the test content of the test case and the participating domain controller process.

The target domain identifier can be the name of the target domain, and is used to indicate the domain controller on which the software testing program runs. It should be noted that the software testing program can run on the domain controller of the vehicle, and the domain controller of the vehicle includes the gateway domain controller controller, intelligent driving domain controller and intelligent cockpit domain controller, etc.

The target process ID can be the name of the target process. Since the software test program has a test scenario composed of multiple processes in the same domain, the target process ID is used to indicate the running process of the software test program, so as to distinguish the software test program that currently needs to be run. process.

In some optional implementation manners, a test interface module is also included. As shown in FIG. 2 , the test interface module 103 is connected to the parsing module 101 and the execution module 102 respectively;

The parsing module 101 is used to transmit the first configuration attribute of the step to the test interface module 103;

The test interface module 103 is used to receive the first configuration attribute of the step, is also used to store the second configuration attribute of the step in advance, and is also used to execute one of the following:

transmitting the first configuration attribute and the second configuration attribute of the step to the execution module 102;

According to the first configuration attribute and the second configuration attribute of the step, the configuration attribute of the step is determined, and the configuration attribute of the step is transmitted to the execution module 102 .

It should be noted that the parsing module 101 is configured to parse the configuration file of the test scenario, obtain the first configuration attribute of the step, and cache the first attribute of the step to the test interface module 103 .

Wherein, the first configuration attribute of the step may be the configuration attribute of the step that the tester wants to test. If testers want to add test scenarios for software testing, they can do so by modifying the configuration files of the test scenarios. In other words, testers can build rich test scenarios according to their needs through the configuration files of the test scenarios.

The second configuration attribute of the step can be understood as the initial configuration attribute of the step, and the tester caches the initial configuration attribute of the step to the test interface module 103 .

The test interface module 103 is used to transmit the first configuration attribute and the second configuration attribute of the step to the execution module 102, and the execution module 102 is used to perform the software test according to the first configuration attribute of the step and the second configuration attribute of the step. Update the configuration of the step, determine the configuration attribute of the step; or, the test interface module 103 is used to update the configuration of the step according to the first configuration attribute and the second configuration attribute of the step, determine the configuration attribute of the step, and transmit it to the execution module 102 Configuration properties for this step.

In some optional implementation manners, the execution module 102 is specifically configured to:

Receive the operation corresponding to the test scenario, the step corresponding to the operation, the first configuration attribute of the step, the input user interface related to the target test information, the second configuration attribute of the step, the first mapping relationship between the test information and the operation, and the step the second mapping relationship between the configuration attributes and the first interface related to the execution function of the step;

Determine the target operation according to the operation corresponding to the test scenario, the target test information and the first mapping relationship;

Determine the target step corresponding to the target operation according to the steps corresponding to the operation and the target operation;

determining the first configuration attribute and the second configuration attribute of the target step according to the first configuration attribute of the step, the second configuration attribute of the step, the second mapping relationship and the target step;

Determine the execution function of the target step according to the first interface and the target step;

Software testing is performed according to the first configuration attribute, the second configuration attribute, and the execution function of the target step.

It should be noted that the execution module 102 is configured to receive the first interface, and the first interface is an interface related to the execution function of the step, or an interface providing the registration step. In addition, the execution module 102 is also used to receive a second interface, whether the second interface provides an interface for registering operations or obtains an interface related to operations, which can be used as a bridge between test scenarios and steps, and is specifically used according to the second interface. The interface registers the target operation to determine the target step corresponding to the target operation.

As shown in Figure 3, in the embodiment of the present application, the parsing module 101 includes a test scene parser (represented by SceneParser); the execution module 102 includes a test scene executor (represented by SceneExecutor), an operation manager (represented by ActionManager) and steps Manager (represented by StepManager), the test scenario executor is connected to the operation manager, the operation manager is connected to the analysis module 101 and the step manager respectively, and the step manager is connected to the test interface module 103; the test interface module 103 includes a configuration manager (Denoted by ConfigManager), the configuration manager pre-stores the configuration attributes of the steps, and the configuration attributes may include the configuration attributes of the steps that the server and the client need to execute. Here, the pre-stored configuration attributes of the steps are the steps in the embodiment of this application The second configuration property for .

Wherein, the test scenario resolver is used to cache the operation corresponding to the test scenario to the test scenario executor, cache the steps corresponding to the operation to the operation manager, and cache the first configuration attribute of the step to the configuration manager.

The test scenario executor is used to receive the target test information input by the tester on the user interface and the first mapping relationship between the test information and the operation, and receive the operation corresponding to the test scenario cached by the test scenario parser; according to the target test information, the first The mapping relationship and the operation corresponding to the test scenario determine the target operation and transmit the target operation to the operation manager.

The operation manager is used to receive the target operation transmitted by the test scenario executor and the second interface registered by the tester; according to the second interface and the steps corresponding to the operation cached by the test scenario parser, the target step corresponding to the target operation is obtained; and the target step Transfer to Step Manager.

The step manager is used to obtain the second mapping relationship between the steps input by the tester and the configuration attributes, obtain the first interface registered by the tester and obtain the target steps transmitted by the operation manager; according to the first interface and the second mapping relationship, obtain The first configuration attribute of the target step cached by the configuration manager, the second configuration attribute of the target step pre-stored by the configuration manager, and the execution function of the target step; according to the first configuration attribute, the second configuration attribute and the execution function of the target step, Perform software testing.

In some optional implementation manners, the data types of the configuration file and the target test information are both string types.

Wherein, the data type of the configuration file is a string, and the data type of the operation corresponding to the test scenario obtained by parsing the configuration file, the step corresponding to the operation, and the first configuration attribute of the step are also of the string type, and the first configuration attribute of the pre-stored step The data types of the second configuration attribute, the target test information, the first mapping relationship between the test information and the operation, and the second mapping relationship between the step and the configuration attribute are all string types. The string type has good readability, and the coupling between test scenarios is greatly reduced through the string adaptation method.

To sum up, the software testing equipment of the embodiment of the present application is based on modularization, has the advantages of high cohesion and low coupling, and can greatly avoid the problems of higher coupling degree and later maintenance cost caused by the increase of test scenarios. Specifically, testers can build configuration files for test scenarios according to test requirements, realize rich test scenarios, and realize the separation of test scenarios and test interfaces without additional adaptation operations; the data type of the configuration file is a string type. Reduce the coupling between test scenarios and test interfaces, thereby reducing debugging costs and post-maintenance costs; and load the configuration files of test scenarios through the parsing module, and parse the configuration files, so that the execution module can analyze the corresponding corresponding test scenarios obtained by the parsing module The operation, the steps corresponding to the operation, and the first configuration attribute of the steps execute software testing to realize automated testing, especially for automated testing of middleware, improve testing efficiency, and have higher flexibility than hard-coded methods.

The embodiment of the present application also provides a software testing method.

As shown in Figure 4, the software testing method includes the following steps:

Step 401, receiving an input user interface related to a configuration file of a test scenario and an input user interface related to target test information;

Step 402, parsing the configuration file to obtain the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step;

Step 403, according to the operation corresponding to the test scenario, the step corresponding to the operation and the target test information, determine the target operation and the target step corresponding to the target operation;

Step 404: Execute software testing according to the first configuration attribute of the step, the pre-stored second configuration attribute of the step, and the execution function of the target step.

The embodiment of the present application provides a software testing method, which can analyze the configuration file of the test scenario, obtain the corresponding operation of the test scenario, the corresponding step of the operation, and the first configuration attribute of the step, so that according to the corresponding operation of the test scenario, the operation corresponding The steps and the first configuration attributes of the steps realize automated software testing, improve test efficiency, reduce debugging costs, and save manpower and material resources; and through the configuration files of test scenarios, the construction of rich test scenarios is realized, and the separation of test interfaces and test scenarios is realized. , no adaptation is required, the coupling between the test interface and the test scenario is reduced, and the later maintenance cost is also reduced.

In some optional implementation manners, the target test information includes at least one of the following:

Target test scene identification;

Target Domain ID;

Target process ID.

In some optional implementation manners, step 403 includes:

receiving a first mapping relationship between test information and operations;

determining the target operation according to the operation corresponding to the test scenario, the target test information, and the first mapping relationship;

According to the step corresponding to the operation and the target operation, the target step corresponding to the target operation is determined.

In some optional implementation manners, step 404 includes:

receiving a second mapping relationship between a step and a configuration attribute and a first interface related to an execution function of the step;

determining a first configuration attribute and a second configuration attribute of the target step according to the first configuration attribute of the step, the second configuration attribute of the step, the second mapping relationship, and the target step;

determining an execution function of the target step according to the first interface and the target step;

Software testing is performed according to the first configuration attribute, the second configuration attribute and the execution function of the target step.

In some optional implementation manners, data types of the configuration file and the target test information are character strings.

Next, the implementation flow of the software testing method in the embodiment of the present application will be described with reference to FIG. 5 .

Step 501 , the step manager in the test interface module registers the first interface, and loads the second configuration attribute of the step pre-stored by the configuration manager.

Step 502, the test scenario parser in the parsing module parses the configuration file of the test scenario, obtains the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step, and caches the operation corresponding to the test scenario into the execution module. A test scenario executor, an operation manager that caches the steps corresponding to the operation in the execution module, and a step manager that caches the first configuration attribute of the step in the execution module.

Step 503, the test scenario executor determines the target operation according to the target test information and the operation corresponding to the test scenario, and transmits the target operation to the operation manager.

Step 504, the operation manager registers the second interface, determines the target step corresponding to the target operation according to the second interface and the steps corresponding to the operation, and transmits the target step to the step manager.

Step 505, the step manager executes software testing according to the first configuration attribute, the second configuration attribute and the execution function of the target step.

The embodiment of the present application also provides an electronic device, including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute any one of the above software testing methods.

The embodiments of the present application further provide a computer program product, including computer programs/instructions, and when the computer programs/instructions are executed by a processor, various processes in the foregoing software testing method embodiments are implemented.

The methods in this application may be fully or partially implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on the computer, the processes or functions described in this application are executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, network equipment, user equipment, core network equipment, OAM or other programmable devices.

The computer program or instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be downloaded from a website, computer, A server or data center transmits to another website site, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrating one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; and it may also be a semiconductor medium, such as a solid state disk. The computer readable storage medium may be a volatile or a nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

The above specific implementation methods are not intended to limit the protection scope of the present application. It should be apparent to those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of this application shall be included within the protection scope of this application.

Claims (8)

1. A software testing device, characterized in that, comprises an analysis module and an execution module, and the execution module is connected with the analysis module; The parsing module is used to receive the input user interface related to the configuration file of the test scenario, and is also used to parse the configuration file to obtain the operation corresponding to the test scenario, the step corresponding to the operation, and the first step of the step. A configuration attribute, further used to transmit the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step to the execution module; The execution module is configured to receive the operation corresponding to the test scenario, the step corresponding to the operation, the first configuration attribute of the step, the second mapping relationship between the step and the configuration attribute, and the execution function related to the step. The first interface is also a user interface for receiving input related to target test information, and is also used for determining the target operation and the target test information according to the operation corresponding to the test scenario, the steps corresponding to the operation, and the target test information. The target step corresponding to the target operation is further used to determine the target step according to the first configuration attribute of the step, the pre-stored second configuration attribute of the step, the second mapping relationship and the target step The first configuration attribute and the second configuration attribute are also used to determine the execution function of the target step according to the first interface and the target step, and are also used to determine the execution function of the target step according to the first configuration attribute, the second Configure properties and execute functions to perform software testing. 2. The software testing device according to claim 1, wherein the target testing information comprises at least one of the following: Target test scene identification; Target Domain ID; Target process ID. 3. The software testing device according to claim 1, further comprising a test interface module, the test interface module being connected to the parsing module and the execution module respectively; The parsing module is configured to transmit the first configuration attribute of the step to the test interface module; The test interface module is used to receive the first configuration attribute of the step, is also used to pre-store the second configuration attribute of the step, and is also used to perform one of the following: transmitting a first configuration attribute and a second configuration attribute of the step to the execution module; According to the first configuration attribute and the second configuration attribute of the step, the configuration attribute of the step is determined, and the configuration attribute of the step is transmitted to the execution module. 4. The software testing device according to claim 1, wherein the execution module is specifically used for: receiving a first mapping relationship between test information and operations; determining the target operation according to the operation corresponding to the test scenario, the target test information, and the first mapping relationship; According to the step corresponding to the operation and the target operation, the target step corresponding to the target operation is determined. 5. The software testing device according to claim 1, wherein the data type of the configuration file and the target testing information is a character string. 6. A software testing method, characterized in that, comprising: A user interface for receiving input related to configuration files of test scenarios, a user interface for input related to target test information, a second mapping relationship between steps and configuration attributes, and a first interface related to execution functions of steps; Parse the configuration file to obtain the operation corresponding to the test scenario, the step corresponding to the operation, and the first configuration attribute of the step; determining a target operation and a target step corresponding to the target operation according to the operation corresponding to the test scenario, the steps corresponding to the operation, and the target test information; determining the first configuration attribute and the second configuration attribute of the target step according to the first configuration attribute of the step, the pre-stored second configuration attribute of the step, the second mapping relationship, and the target step; determining an execution function of the target step according to the first interface and the target step; Software testing is performed according to the first configuration attribute, the second configuration attribute and the execution function of the target step. 7. The software testing method according to claim 6, characterized in that, according to the operation corresponding to the test scenario, the steps corresponding to the operation, and the target test information, determine the target operation and the target corresponding to the target operation steps, including: receiving a first mapping relationship between test information and operations; determining the target operation according to the operation corresponding to the test scenario, the target test information, and the first mapping relationship; According to the step corresponding to the operation and the target operation, the target step corresponding to the target operation is determined. 8. An electronic device, characterized in that it comprises: at least one processor; and a memory communicatively coupled to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions are executed by the at least one processor, so that the at least one processor can perform the operation described in any one of claims 6 to 7 The software testing method described above.

Images