CN115687162B - Software testing device and method and electronic device - Google Patents
Software testing device and method and electronic device Download PDFInfo
- Publication number
- CN115687162B CN115687162B CN202310000634.6A CN202310000634A CN115687162B CN 115687162 B CN115687162 B CN 115687162B CN 202310000634 A CN202310000634 A CN 202310000634A CN 115687162 B CN115687162 B CN 115687162B
- Authority
- CN
- China
- Prior art keywords
- target
- test
- configuration attribute
- configuration
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000013522 software testing Methods 0.000 title claims abstract description 37
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000012360 testing method Methods 0.000 claims abstract description 230
- 230000006870 function Effects 0.000 claims description 25
- 238000013507 mapping Methods 0.000 claims description 22
- 230000008569 process Effects 0.000 claims description 13
- 238000004590 computer program Methods 0.000 abstract description 15
- 230000008878 coupling Effects 0.000 description 10
- 238000010168 coupling process Methods 0.000 description 10
- 238000005859 coupling reaction Methods 0.000 description 10
- 238000012423 maintenance Methods 0.000 description 6
- 239000000463 material Substances 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 4
- 238000010276 construction Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000000926 separation method Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Debugging And Monitoring (AREA)
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
Technical Field
The present application relates to the field of software testing technologies, and in particular, to a software testing device, a software testing method, an electronic device, and a computer program product.
Background
At present, in the development or use process of a software middleware (hereinafter referred to as middleware), relevant tests such as a smoke test, a benchmark test, a load test, an interface test, a pressure test, a bottleneck test and the like need to be performed, but considering that the middleware needs to support a large number of complex scenes, a scene test is also needed in addition to the tests.
The scene test comprises a manual scene test and an automatic scene test, wherein the manual scene test is performed in a mode of manually inputting options at a terminal, and the problems of low test efficiency and large waste of manpower and material resources exist. The problem of limited test scenes exists in automatic scene test, and if a tester wants to increase the test scenes, the tester needs to rewrite codes, so that the coupling degree between a test interface and the test scenes is increased along with the increase of the test scenes, and the later maintenance cost is increased.
Disclosure of Invention
The application provides software testing equipment, a software testing method, electronic equipment and a computer program product, which are used for solving the problems that in the prior art, manual scene testing of middleware has low testing efficiency and automatic scene testing has high coupling degree between a testing interface and a testing scene.
According to a first aspect of the application, a software testing device is provided, which comprises an analysis module and an execution module, wherein the execution module is connected with the analysis module;
the analysis module is used for receiving an input user interface related to a configuration file of a test scene, analyzing the configuration file, obtaining an operation corresponding to the test scene, a step corresponding to the operation and a first configuration attribute of the step, and transmitting the operation corresponding to the test scene, 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 an operation corresponding to the test scenario, a step corresponding to the operation, and a first configuration attribute of the step, and further configured to receive an input user interface related to target test information, and further configured to determine a target operation and a target step corresponding to the target operation according to the operation corresponding to the test scenario, the step corresponding to the operation, and the target test information, and further configured to execute a software test according to the first configuration attribute of the step, a pre-stored second configuration attribute of the step, and an execution function of the target step.
According to a second aspect of the present application, there is provided a software testing method comprising:
receiving an input user interface related to a configuration file of a test scenario and an input user interface related to target test information;
analyzing the configuration file to obtain the operation corresponding to the test scene, 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 scene, the step corresponding to the operation and the target test information;
and executing software test according to the first configuration attribute of the step, the second configuration attribute of the step stored in advance and the execution function of the target step.
According to a third aspect of the present application, there is provided an electronic device comprising:
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 to enable the at least one processor to perform the software testing method of the second aspect.
According to a fourth aspect of the present application, there is provided a computer program product comprising computer programs/instructions which, when executed by a processor, implement the software testing method according to the second aspect.
In the embodiment of the application, the analysis module can analyze the configuration file of the constructed test scene to obtain the operation corresponding to the test scene, the step corresponding to the operation and the first configuration attribute of the step, and the execution module realizes automatic software test according to the operation corresponding to the test scene, the step corresponding to the operation and the first configuration attribute of the step, so that the test efficiency is improved, the debugging cost is reduced, and manpower and material resources are saved; and the configuration file of the test scene is input in the analysis module, so that the construction of rich test scenes is realized, codes do not need to be rewritten, the separation of the test interface and the test scene is realized, adaptation is not needed, the coupling degree between the test interface and the test scene is reduced, and the later maintenance cost is also reduced.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present application, nor do they limit the scope of the present application. Other features of the present application will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
FIG. 1 is a schematic structural diagram of a software testing device provided in an embodiment of the present application;
FIG. 2 is a second schematic structural diagram of a software testing apparatus according to an embodiment of the present application;
FIG. 3 is a third schematic structural diagram of a software testing apparatus according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating a software testing method according to an embodiment of the present disclosure;
fig. 5 is a second flowchart of a software testing method according to an embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application to assist in understanding, which are to be considered 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 present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Before the description of the specific embodiments of the present application, the following description is first made.
Test scenario (scene): a test scenario consists of one or more operations.
Operation (action): the method is used for representing specific operations required to be executed by a client and a server, and one operation consists of one or more steps and is a basic unit for constructing a test scenario.
Step (step): the minimum execution unit used for representing the operation of the server or the client is a basic unit for constructing the operation, and generally, each step has some configuration attributes.
It should be noted that the following embodiments of the present application are applicable to scenario testing of middleware, and specific contents of related test scenarios, operations, and steps can be designed by those skilled in the art according to test requirements, which is not limited herein.
The middleware is general service software between platforms such as hardware and an operating system and application programs, provides an environment for running in development for application software on an upper layer, and can help users to develop and integrate complex application software flexibly and efficiently. A common middleware is Software Development Kit (SDK), which can be compiled with some application Software to provide some functional interfaces to support the functional implementation of the application Software. For example, a software development kit is compiled into video software to support a video output function, and thus, the performance of the software development kit (i.e., middleware) directly affects the performance of application software, so in order to ensure the performance of the application software, the middleware needs to be tested.
The embodiment of the application provides software testing equipment.
As shown in fig. 1, the software testing apparatus includes: the analysis module 101 and the execution module 102, wherein the execution module 102 is connected with the analysis module 101;
the analysis module 101 is configured to receive an input user interface related to a configuration file of a test scenario, analyze the configuration file, obtain an operation corresponding to the test scenario, a step corresponding to the operation, and a first configuration attribute of the step, and 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 102;
the execution module 102 is configured to receive an operation corresponding to a test scenario, a step corresponding to the operation, and a first configuration attribute of the step, and is further configured to receive an input user interface related to target test information, determine a target step corresponding to the target operation and the target operation according to the operation corresponding to the test scenario, the step corresponding to the operation, and the target test information, and execute a software test according to the first configuration attribute of the step, a second configuration attribute of the pre-stored step, and an execution function of the target step.
The configuration file of the test scene can be input by a tester at a user interface according to test requirements, so that when the test scenes are increased, the tester can modify the configuration file according to the test requirements, abundant test scenes are constructed, codes do not need to be rewritten, the test efficiency is greatly improved, and the debugging cost is reduced.
The target test information can be input by a tester on a user interface according to the test requirement of the software.
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 may be different user interfaces. The user interface is configured to select an address of a configuration file of a test scenario, so that the configuration file of the test scenario can be loaded to the parsing module 101, and further configured to input specific information content of target test information at a corresponding option, so that the target test information can be loaded to the executing module 102.
The second configuration attribute of the step may be an initialization configuration attribute of the step pre-stored by the tester, and specifically may relate to the 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.
The configuration attribute can be an input parameter of an actual test interface, and the input parameter is confirmed by the test interface; or configuration items which are also used for indicating how to test the actual test interface, such as the number of threads which call the actual test interface concurrently, the number of calls of the actual test interface, the interval between two calls of the test interface, and the like. The operation corresponding to the test scenario can be understood as the operation to be executed by the test scenario; and the steps corresponding to the operations can be understood as the steps required to be executed by the operations.
It should be further noted that the test scenario may correspond to one or more operations, and the operation may correspond to one or more steps, that is, the operation corresponding to the test scenario may be understood as an operation sequence corresponding to the test scenario, and the step corresponding to the operation may be understood as a step sequence corresponding to the operation.
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 as to correspondingly execute the execution function of the target step according to the first configuration attribute and the second configuration attribute of the target step, thereby implementing the software scenario test set by the tester.
In the related art, software needs to support scene testing, and the scene testing is divided into manual scene testing and automatic scene testing, wherein the manual scene testing has the problems of low testing efficiency, increased debugging cost and waste of manpower and material resources; the automatic scene test is increased along with the increase of test scenes, and the problem of high coupling degree between a test interface and the test scenes exists.
In view of this, an embodiment of the present application provides a software testing device, which includes an analysis module and an execution module, where the execution module can implement an automated software test according to an operation corresponding to a test scenario obtained by the analysis module, a step corresponding to the operation, and a first configuration attribute of the step, so as to improve testing efficiency, reduce debugging cost, and save manpower and material resources; and the configuration file of the test scene is input in the analysis module, so that the construction of rich test scenes is realized, codes do not need to be rewritten, the separation of the test interface and the test scene is realized, adaptation is not needed, the coupling degree between the test interface and the test scene is reduced, and the later maintenance cost is also reduced.
In some optional embodiments, the target test information comprises at least one of:
target test scenario identification (SceneID);
target domain identification (DomainID);
the target process identification (ProcessName).
In the embodiment of the application, the target test scenario identifier may be a name of the target test scenario and is used to represent an identifier of the test scenario, and the target test scenario identifier determines test content of the test case and a participating domain controller process.
The target domain identifier may be a name of a target domain, and is used to indicate a domain controller on which the software test program runs, and it should be noted that the software test program may run on a domain controller of a vehicle, where the domain controller of the vehicle includes a gateway domain controller, an intelligent driving domain controller, an intelligent cockpit domain controller, and the like.
The target process identifier may be a target process name, and since the software test program has a test scenario formed by a plurality of processes in the same domain, the target process identifier is used to represent the process in which the software test program operates, so as to distinguish the process in which the software test program currently needs to operate.
In some optional embodiments, the test system further includes a test interface module, as shown in fig. 2, the test interface module 103 is connected to the parsing module 101 and the executing module 102 respectively;
the analysis module 101 is configured to transmit the first configuration attribute of the step to the test interface module 103;
the test interface module 103 is configured to receive the first configuration attribute of the step, pre-store the second configuration attribute of the step, and execute one of the following:
transmitting the first configuration attribute and the second configuration attribute of the step to the execution module 102;
the configuration attributes of the step are determined based on the first configuration attribute and the second configuration attribute of the step, and are 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 in the test interface module 103.
The first configuration attribute of the step may be a configuration attribute of the step that the tester wants to test. If the tester wants to add the test scenario of the software test, the software test can be realized by modifying the configuration file of the test scenario. That is to say, the tester can construct rich test scenes according to the requirements through the configuration files of the test scenes.
The second configuration attribute of a step may be understood to be the initialized configuration attribute of the step that the tester caches to the test interface module 103.
The test interface module 103 is configured 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 configured to update and configure the step according to the first configuration attribute of the step and the second configuration attribute of the step when executing the software test, and determine the configuration attribute of the step; or, the test interface module 103 is configured to update and configure 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 the configuration attribute of the step to the execution module 102.
In some alternative embodiments, the execution module 102 is specifically configured to:
receiving an operation corresponding to a test scene, a step corresponding to the operation, a first configuration attribute of the step, an input user interface related to target test information, a second configuration attribute of the step, a first mapping relation between the test information and the operation, a second mapping relation between the step and the configuration attribute and a first interface related to an execution function of the step;
determining target operation according to the operation corresponding to the test scene, the target test information and the first mapping relation;
determining a target step corresponding to the target operation according to the step corresponding to the operation and the target operation;
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 mapping relation and the target step;
determining an execution function of the target step according to the first interface and the target step;
and executing the software test 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 a first interface, where the first interface is an interface related to an execution function of the step, or an interface providing the registration step. In addition, the execution module 102 is further configured to receive a second interface, where the second interface is an interface for providing a registration operation, or an interface related to an acquisition operation, and may be used as a bridge between a test scenario and a step, and specifically, is configured to register a target operation according to the second interface, so as to determine a target step corresponding to the target operation.
As shown in fig. 3, in the embodiment of the present application, the parsing module 101 includes a test scenario parser (denoted by SceneParser); the execution module 102 comprises a test scene executor (represented by a SceneExecutor), an operation manager (represented by an ActionManager), and a step manager (represented by a StepManager), wherein the test scene executor is connected with the operation manager, the operation manager is respectively connected with the analysis module 101 and the step manager, and the step manager is connected with the test interface module 103; the test interface module 103 includes a configuration manager (denoted by ConfigManager), which stores the configuration attributes of the steps in advance, where the configuration attributes may include the configuration attributes of the steps that the server and the client need to execute, and here, the configuration attributes of the steps in advance are the second configuration attributes of the steps in the embodiment of the present application.
The test scenario parser is used for caching the operation corresponding to the test scenario executor, caching the step corresponding to the operation manager, and caching the first configuration attribute of the step to the configuration manager.
The test scene executor is used for receiving target test information input by a tester on the user interface and a first mapping relation between the test information and operation, and receiving operation corresponding to the test scene cached by the test scene parser; and determining target operation according to the target test information, the first mapping relation and the operation corresponding to the test scene, and transmitting the target operation to the operation manager.
The operation manager is used for receiving target operation transmitted by the test scene executor and a second interface registered by a tester; acquiring a target step corresponding to the target operation according to the steps corresponding to the operations cached by the second interface and the test scene analyzer; and transmits the target step to the step manager.
The step manager is used for acquiring a second mapping relation between the step input by the tester and the configuration attribute, acquiring a first interface registered by the tester and acquiring a target transmitted by the operation manager; according to the first interface and the second mapping relation, acquiring a first configuration attribute of a target step cached by a configuration manager, a second configuration attribute of the target step prestored by the configuration manager and an execution function of the target step; and executing the software test according to the first configuration attribute, the second configuration attribute and the execution function of the target step.
In some alternative embodiments, the data types of the configuration file and the target test information are both string types.
The data type of the configuration file is a character string, the operation corresponding to the test scenario obtained by analyzing the configuration file, the step corresponding to the operation and the data type of the first configuration attribute of the step are all character string types, and the data types of the second configuration attribute of the pre-stored step, the target test information, the first mapping relation between the test information and the operation and the second mapping relation between the step and the configuration attribute are all character string types. The type readability of the character strings is good, and the coupling degree between test scenes is greatly reduced through the adaptation mode of the character strings.
To sum up, the software test equipment of this application embodiment, based on the modularization, has the advantage of high cohesion, low coupling, can greatly avoid the problem that the degree of coupling that the test scenario increases and lead to becomes high, later maintenance cost increases. Specifically, a tester can construct a configuration file of a test scene according to test requirements, rich test scenes are realized, the test scenes are separated from a test interface, and no additional adaptive operation is needed; the data type of the configuration file is a character string type, so that the coupling degree between a test scene and a test interface is greatly reduced, and the debugging cost and the later maintenance cost are reduced; and the analysis module loads the configuration file of the test scene and analyzes the configuration file, so that the execution module can execute software test according to the operation corresponding to the test scene obtained by analysis of the analysis module, the step corresponding to the operation and the first configuration attribute of the step, the automatic test is realized, the method and the device are particularly suitable for the automatic test of the middleware, the test efficiency is improved, and the method and the device have higher flexibility compared with a hard coding mode.
The embodiment of the application also provides a software testing method.
As shown in fig. 4, the software testing method includes the following steps:
The embodiment of the application provides a software testing method, which can analyze a configuration file of a testing scene to obtain an operation corresponding to the testing scene, a step corresponding to the operation and a first configuration attribute of the step, so that an automatic software test is realized according to the operation corresponding to the testing scene, the step corresponding to the operation and the first configuration attribute of the step, the testing efficiency is improved, the debugging cost is reduced, and manpower and material resources are saved; and the construction of rich test scenes is realized through the configuration files of the test scenes, the separation of the test interface and the test scenes is realized, adaptation is not needed, the coupling degree between the test interface and the test scenes is reduced, and the later maintenance cost is also reduced.
In some optional embodiments, the target test information comprises at least one of:
identifying a target test scene;
a target domain identification;
and identifying the target process.
In some alternative embodiments, step 403 includes:
receiving a first mapping relation between test information and operation;
determining the target operation according to the operation corresponding to the test scene, the target test information and the first mapping relation;
and determining a target step corresponding to the target operation according to the step corresponding to the operation and the target operation.
In some alternative embodiments, step 404 includes:
receiving a second mapping relation between the step and the 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 mapping relation and the target step;
determining an execution function of the target step according to the first interface and the target step;
and executing the software test according to the first configuration attribute, the second configuration attribute and the execution function of the target step.
In some optional embodiments, the data type of the configuration file and the target test information is a character string.
Next, an implementation flow of the software testing method according to the embodiment of the present application is described with reference to fig. 5.
An embodiment of the present application further 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 to enable the at least one processor to perform any of the software testing methods described above.
Embodiments of the present application further provide a computer program product, which includes a computer program/instruction, and when the computer program/instruction is executed by a processor, the computer program/instruction implements the processes of the software testing method embodiments.
The methods in the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions is loaded and executed on a computer, the processes or functions described herein are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network device, a user equipment, a core network device, OAM, or other programmable apparatus.
The computer program or instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer program or instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire or wirelessly. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that integrates one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; optical media such as digital video disks; but also semiconductor media such as solid state disks. The computer readable storage medium may be volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (8)
1. The software testing equipment is characterized by comprising an analysis module and an execution module, wherein the execution module is connected with the analysis module;
the analysis module is used for receiving an input user interface related to a configuration file of a test scene, analyzing the configuration file, obtaining an operation corresponding to the test scene, a step corresponding to the operation and a first configuration attribute of the step, and transmitting the operation corresponding to the test scene, 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 an operation corresponding to the test scenario, a step corresponding to the operation, a first configuration attribute of the step, a second mapping relationship between the step and the configuration attribute, and a first interface related to an execution function of the step, and further configured to receive an input user interface related to target test information, and further configured to determine a target operation and a target step corresponding to the target operation according to the operation corresponding to the test scenario, the step corresponding to the operation, and the target test information, and further configured to determine a first configuration attribute and a second configuration attribute of the target step according to the first configuration attribute of the step, a second configuration attribute of the step stored in advance, the second mapping relationship, and the target step, and further configured to determine an execution function of the target step according to the first configuration attribute, the second configuration attribute, and the execution function of the target step, and further configured to execute a software test according to the first configuration attribute, the second configuration attribute, and the execution function of the target step.
2. The software testing device of claim 1, wherein the target test information comprises at least one of:
identifying a target test scene;
a target domain identification;
and identifying the target process.
3. The software testing device of claim 1, further comprising a testing interface module, wherein the testing interface module is connected to the parsing module and the executing module respectively;
the analysis module is used for transmitting the first configuration attribute of the step to the test interface module;
the test interface module is configured to receive the first configuration attribute of the step, pre-store the second configuration attribute of the step, and execute one of the following:
transmitting the first configuration attribute and the second configuration attribute of the step to the execution module;
and determining the configuration attribute of the step according to the first configuration attribute and the second configuration attribute of the step, and transmitting the configuration attribute of the step to the execution module.
4. The software testing device of claim 1, wherein the execution module is specifically configured to:
receiving a first mapping relation between test information and operation;
determining the target operation according to the operation corresponding to the test scene, the target test information and the first mapping relation;
and determining a target step corresponding to the target operation according to the step corresponding to the operation and the target operation.
5. The software testing device of claim 1, wherein the data type of the configuration file and the target test information is a character string.
6. A software testing method, comprising:
receiving an input user interface related to a configuration file of a test scenario, an input user interface related to target test information, a second mapping relationship between steps and configuration attributes, and a first interface related to an execution function of the steps;
analyzing the configuration file to obtain the operation corresponding to the test scene, 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 scene, the step corresponding to the operation and the target test information;
determining a first configuration attribute and a second configuration attribute of the target step according to the first configuration attribute of the step, a pre-stored second configuration attribute of the step, the second mapping relation and the target step;
determining an execution function of the target step according to the first interface and the target step;
and executing the software test according to the first configuration attribute, the second configuration attribute and the execution function of the target step.
7. The software testing method of claim 6, wherein the step of determining a target operation and a target corresponding to the target operation according to the operation corresponding to the test scenario, the step corresponding to the operation, and the target test information comprises:
receiving a first mapping relation between test information and operation;
determining the target operation according to the operation corresponding to the test scene, the target test information and the first mapping relation;
and determining a target step corresponding to the target operation according to the step corresponding to the operation and the target operation.
8. An electronic device, comprising:
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 to enable the at least one processor to perform the software testing method of any one of claims 6 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310000634.6A CN115687162B (en) | 2023-01-03 | 2023-01-03 | Software testing device and method and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310000634.6A CN115687162B (en) | 2023-01-03 | 2023-01-03 | Software testing device and method and electronic device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115687162A CN115687162A (en) | 2023-02-03 |
| CN115687162B true CN115687162B (en) | 2023-03-21 |
Family
ID=85057423
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310000634.6A Active CN115687162B (en) | 2023-01-03 | 2023-01-03 | Software testing device and method and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115687162B (en) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10015072B2 (en) * | 2016-07-07 | 2018-07-03 | Netscout Systems, Inc. | Consolidation of network test automation tools |
| CN108108297B (en) * | 2016-11-25 | 2021-05-18 | 腾讯科技（深圳）有限公司 | Method and device for automatic testing |
| CN108614770B (en) * | 2018-04-09 | 2021-08-27 | 中国工商银行股份有限公司 | Automatic test assertion method, device, storage medium and equipment |
| CN110704306B (en) * | 2019-09-09 | 2024-03-22 | 武汉安辰鑫信息科技有限公司 | Assertion processing method, device, equipment and storage medium in test |
| CN113986768A (en) * | 2021-11-30 | 2022-01-28 | 中国平安人寿保险股份有限公司 | Application stability testing method, device, equipment and medium |
| CN115470101A (en) * | 2022-08-12 | 2022-12-13 | 西安万像电子科技有限公司 | Data testing method and device, computer equipment and storage medium |
-
2023
- 2023-01-03 CN CN202310000634.6A patent/CN115687162B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN115687162A (en) | 2023-02-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107979508B (en) | Micro-service test method and device | |
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| US10705811B2 (en) | Method and system for automated, static instrumentation for applications designed for execution in environments with restricted resources, like mobile devices or TV set top boxes | |
| CN105303112B (en) | The detection method and device of component call loophole | |
| CN105159833A (en) | Automatic testing device and method | |
| CN110013672B (en) | Method, device, apparatus and computer-readable storage medium for automated testing of machine-run games | |
| CN109144533A (en) | A kind of method, system and the computer installation of update and the load of application program | |
| CN111447227A (en) | Protocol analysis method and device of Internet of things equipment | |
| US11422917B2 (en) | Deriving software application dependency trees for white-box testing | |
| JP2008176793A (en) | Software test system, method, and computer-readable recording medium having program stored for executing this method | |
| US9189223B2 (en) | Connecting method and apparatus for connecting a component included in an application with an external service | |
| CN111324619B (en) | Object updating method, device, equipment and storage medium in micro-service system | |
| CN108021357B (en) | Optimization method and device for program call | |
| CN112241360A (en) | Test case generation method, device, equipment and storage medium | |
| CN109492181B (en) | Page jump method, device, computer equipment and storage medium | |
| CN107045475B (en) | Test method and device | |
| CN108664270A (en) | Environment dynamic switching method, device, computer equipment and storage medium | |
| CN110381101A (en) | API gateway control system, control method, equipment and medium | |
| CN107391362A (en) | Application testing method, mobile terminal and storage medium | |
| CN109032705B (en) | Application program execution method and device, electronic equipment and readable storage medium | |
| CN113434405A (en) | Method and device for determining test file, storage medium and electronic device | |
| CN111930625B (en) | Log acquisition method, device and system based on cloud service platform | |
| CN115687162B (en) | Software testing device and method and electronic device | |
| KR100930962B1 (en) | Remote security testing device and method of RPC-based software | |
| CN110297639B (en) | Method and apparatus for detecting code |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |