CN110377520B - Transaction scenario testing method and device, electronic equipment and readable storage medium - Google Patents
Transaction scenario testing method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN110377520B CN110377520B CN201910664165.1A CN201910664165A CN110377520B CN 110377520 B CN110377520 B CN 110377520B CN 201910664165 A CN201910664165 A CN 201910664165A CN 110377520 B CN110377520 B CN 110377520B
- Authority
- CN
- China
- Prior art keywords
- test
- script
- running
- scripts
- executed
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 341
- 238000013515 script Methods 0.000 claims abstract description 342
- 238000000034 method Methods 0.000 claims abstract description 55
- 230000008569 process Effects 0.000 claims description 22
- 230000015654 memory Effects 0.000 claims description 11
- 230000006870 function Effects 0.000 description 17
- 238000010998 test method Methods 0.000 description 12
- 238000004590 computer program Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 238000012546 transfer Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 238000009472 formulation Methods 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 239000000203 mixture Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000000758 substrate Substances 0.000 description 2
- 108010001267 Protein Subunits Proteins 0.000 description 1
- BUGBHKTXTAQXES-UHFFFAOYSA-N Selenium Chemical compound [Se] BUGBHKTXTAQXES-UHFFFAOYSA-N 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 229910052711 selenium Inorganic materials 0.000 description 1
- 239000011669 selenium Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3644—Software debugging by instrumenting at runtime
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/366—Software debugging using diagnostics
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The disclosure provides a method for testing a transaction scenario, comprising the following steps: acquiring a plurality of test scripts of different types, wherein the plurality of test scripts are used for verifying whether a target transaction scene is normal or not; acquiring operation parameters of each test script in a plurality of test scripts, wherein the operation parameters of each test script at least comprise the interdependence relationship between the test script and other test scripts; using an execution machine corresponding to each test script, and running a plurality of test scripts based on the running parameters of each test script to obtain a plurality of running results; and determining whether the target transaction scene is normal according to the operation results. The disclosure also provides a testing device for a transaction scenario, an electronic device and a computer-readable storage medium.
Description
Technical Field
The present disclosure relates to the field of computer technology, and more particularly, to a method and apparatus for testing a transaction scenario, an electronic device, and a computer-readable storage medium.
Background
With the development and popularization of the automatic testing technology and the rapid construction of various software systems, testers need to use different kinds of automatic tools to perform daily version function verification in the daily testing process. With the development of work, the number of automation scripts required to be maintained by each tester is increased, and the types of the scripts are also diversified.
Since the test tools relied upon for each automation script is different, there is some variability in the requirements for the environment configuration at the time of execution of each script. Each functional script cannot be directly and automatically connected in series and mutually carry out parameter transfer, a tester is required to manually intervene in the test process, script execution tasks are manually submitted according to the test step sequence, the output data and the input data after each script execution are copied and pasted, then verification work of input and output items is expanded, the whole running result cannot be automatically verified, the service scene level automatic test process is discontinuous, and the problems of low test work efficiency and the like exist.
Disclosure of Invention
In view of this, the present disclosure provides a method and apparatus for testing a transaction scenario, an electronic device, and a computer-readable storage medium.
One aspect of the present disclosure provides a method for testing a transaction scenario, including: acquiring a plurality of test scripts of different types, wherein the plurality of test scripts are used for verifying whether a target transaction scene is normal or not; acquiring the operation parameters of each test script in the plurality of test scripts, wherein the operation parameters of each test script at least comprise the interdependence relationship between the test script and other test scripts; using an execution machine corresponding to each test script, and running the plurality of test scripts based on the running parameters of each test script to obtain a plurality of running results; and determining whether the target transaction scene is normal according to the operation results.
According to an embodiment of the disclosure, the method for testing a transaction scenario further includes displaying a test scenario editing interface; the obtaining the operation parameters of each test script in the plurality of test scripts comprises the following steps: and acquiring the operation parameters input on the test scene editing interface for each test script.
According to an embodiment of the present disclosure, the dependency relationship between the test script and the other test scripts includes an operation order between the test script and the other test scripts, and the operating the plurality of test scripts based on the operation parameter of each test script includes: in the process of running the test scripts based on the running sequence of each test script, determining whether to adjust the running sequence of the test script to be executed, which is executed after the running test script, based on the running result of the test script which is already run.
According to an embodiment of the present disclosure, determining whether to adjust an execution order of test scripts to be executed, which are executed after the test scripts that have been already executed, based on an execution result of the test scripts that have been already executed, includes: judging whether the running result of the running test script meets the branch condition; and determining a script executed after the test script having been run is the test script corresponding to the branching condition when the branching condition is satisfied.
According to an embodiment of the present disclosure, determining whether to adjust an execution order of test scripts to be executed, which are executed after the test scripts that have been already executed, based on an execution result of the test scripts that have been already executed, includes: checking the running result of the running test script according to the checking rule; and determining whether to adjust the running sequence of the test script to be executed, which is executed after the test script which is already executed, according to the checking result.
According to an embodiment of the present disclosure, determining whether the target transaction scenario is normal according to the plurality of operation results includes: determining whether the operation results are consistent with standard data; and determining that the target transaction scenario is normal when the plurality of operation results are consistent with the standard data.
According to embodiments of the present disclosure, the plurality of test scripts of the different types described above include test scripts developed using different tools, and/or test scripts having different operating environments.
Another aspect of the present disclosure provides a testing device for a transaction scenario, including a first obtaining module, configured to obtain a plurality of test scripts of different types, where the plurality of test scripts are used to verify whether a target transaction scenario is normal; the second acquisition module is used for acquiring the operation parameters of each test script in the plurality of test scripts, wherein the operation parameters of each test script at least comprise the interdependence relationship between the test script and other test scripts; the running module is used for running the plurality of test scripts based on the running parameters of each test script by using an execution machine corresponding to each test script to obtain a plurality of running results; and the determining module is used for determining whether the target transaction scene is normal or not according to the operation results.
According to an embodiment of the disclosure, the testing device of the transaction scenario further comprises a display module for displaying a testing scenario editing interface; the second obtaining module is configured to obtain an operation parameter for each test script input on the test scenario editing interface.
According to an embodiment of the present disclosure, the dependency relationship between the test script and the other test scripts includes an operation order between the test script and the other test scripts, and the operation module is configured to: in the process of running the test scripts based on the running sequence of each test script, determining whether to adjust the running sequence of the test script to be executed, which is executed after the running test script, based on the running result of the test script which is already run.
According to an embodiment of the present disclosure, determining whether to adjust an execution order of test scripts to be executed, which are executed after the test scripts that have been already executed, based on an execution result of the test scripts that have been already executed, includes: judging whether the running result of the running test script meets the branch condition; and determining a script executed after the test script having been run is the test script corresponding to the branching condition when the branching condition is satisfied.
According to an embodiment of the present disclosure, determining whether to adjust an execution order of test scripts to be executed, which are executed after the test scripts that have been already executed, based on an execution result of the test scripts that have been already executed, includes: checking the running result of the running test script according to the checking rule; and determining whether to adjust the running sequence of the test script to be executed, which is executed after the test script which is already executed, according to the checking result.
According to an embodiment of the present disclosure, the determining module is configured to determine whether the plurality of operation results are consistent with standard data; and determining that the target transaction scene is normal under the condition that the operation results are consistent with the standard data.
According to embodiments of the present disclosure, the plurality of test scripts of the different types described above include test scripts developed using different tools, and/or test scripts having different operating environments.
Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed, are configured to implement a method as described above.
Another aspect of the present disclosure provides a computer program comprising computer executable instructions which when executed are for implementing a method as described above.
According to the embodiment of the disclosure, a plurality of test scripts of different types for verifying whether the target transaction scenario is normal can be acquired, the plurality of test scripts are run based on the running parameters of each test script by using an execution machine corresponding to each test script, and whether the target transaction scenario is normal is determined according to a plurality of running results. The test scripts with all functions can be directly and automatically connected in series and mutually carry out parameter transfer, even if test tools relied on by writing the automatic test scripts are different, or the requirements of environment configuration are different when all the scripts are executed, no manual intervention of a tester is needed in the test process, copy and paste of data output after each script is executed and input data are not needed, the technical problem that in the related art, manual intervention is needed when transaction scenes are tested through different types of scripts, and the service scene-level automatic test process is discontinuous is solved, and the test work efficiency is improved.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments thereof with reference to the accompanying drawings in which:
FIG. 1 schematically illustrates an exemplary system architecture of a test method and apparatus in which a transaction scenario may be applied, according to an embodiment of the present disclosure;
FIG. 2 schematically illustrates a flow chart of a method of testing a transaction scenario in accordance with an embodiment of the present disclosure;
FIG. 3 schematically illustrates a flow chart of a method of testing a transaction scenario in accordance with an embodiment of the present disclosure;
FIG. 4 schematically illustrates a block diagram of a testing device of a transaction scenario according to an embodiment of the present disclosure; and
fig. 5 schematically illustrates a block diagram of a computer system suitable for implementing the test methods described above, in accordance with an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.
Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
When an automation test script is compiled, the automation script can be generally decoupled and split according to functions and test intentions to form a modularized public script, so that the multiplexing rate of the automation script is improved, and the maintenance and update cost of the existing automation script when a certain unidirectional function is changed is reduced.
Under the principle of scripting, when an automatic test of a certain business process is performed, the automatic scripts of the functional test are generally required to be assembled in series (or connected in series after logic judgment) to form a test script set, and after all scripts are run, output data in each script is subjected to some logic calculation and then a check formula is written for verification.
Since the test tools relied upon for each automation script is different, there is some variability in the requirements for the environment configuration at the time of execution of each script. The functional scripts cannot be directly and automatically connected in series and mutually carry out parameter transmission, and a tester is required to manually intervene in the test process, and the script execution tasks are manually submitted according to the test step sequence. And the output data and the input data after each script is executed are copied and pasted, and then the checking work of the input and output items is expanded, so that the whole running result cannot be automatically checked, the service scene level automatic testing process is discontinuous, and the problems of low testing work efficiency and the like exist.
The embodiment of the disclosure provides a method for testing a transaction scenario, which comprises the following steps: acquiring a plurality of test scripts of different types, wherein the plurality of test scripts are used for verifying whether a target transaction scene is normal or not; acquiring operation parameters of each test script in a plurality of test scripts, wherein the operation parameters of each test script at least comprise the interdependence relationship between the test script and other test scripts; using an execution machine corresponding to each test script, and running a plurality of test scripts based on the running parameters of each test script to obtain a plurality of running results; and determining whether the target transaction scene is normal according to the operation results.
Fig. 1 schematically illustrates an exemplary system architecture of a test method and apparatus to which a transaction scenario may be applied, according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.
As shown in fig. 1, a system architecture 100 according to this embodiment may include a terminal device 101, execution machines 102, 103, 104, and a network 105. The network 105 serves as a medium providing communication links between the terminal equipment 101 and the execution machines 102, 103, 104. The network 105 may include various connection types, such as wired and/or wireless communication links, and the like.
The terminal device 101 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The execution machines 102, 103, 104 may be computing devices that execute test scripts.
It should be noted that, the method for testing a transaction scenario provided by the embodiments of the present disclosure may be generally performed by the terminal device 101. Accordingly, the testing apparatus for a transaction scenario provided by the embodiments of the present disclosure may be generally disposed in the terminal device 101. The method for testing a transaction scenario provided by the embodiments of the present disclosure may also be performed by other devices that are different from the terminal device 101 and capable of communicating with the terminal device 101. Accordingly, the testing apparatus of the transaction scenario provided by the embodiments of the present disclosure may also be provided in other devices that are different from the terminal device 101 and capable of communicating with the terminal device 101.
It should be understood that the number of terminal devices, networks, and execution machines in fig. 1 are merely illustrative. There may be any number of terminal devices, networks, and executives as desired by the implementation.
Fig. 2 schematically illustrates a flow chart of a method of testing a transaction scenario in accordance with an embodiment of the present disclosure.
As shown in fig. 2, the method includes operations S210 to S240.
In operation S210, a plurality of test scripts of different types are acquired, and the plurality of test scripts are used to verify whether the target transaction scenario is normal.
According to embodiments of the present disclosure, the plurality of test scripts of different types include test scripts developed using different tools, and/or test scripts having different operating environments.
For example, automated test scripts developed based on different tools, such as QTP scripts, selenium scripts, etc., are different tools used for both development and operation.
For example, the test scripts with different running environments can be automated test scripts based on different platforms, such as a test for a desktop application, a test for a Web application, a test for a mobile phone end, and the like. The running environment relates to Web application, client and mobile terminal, etc., and various test environments need to be installed and maintained.
According to embodiments of the present disclosure, the target transaction scenario may be a deposit transaction scenario, a transfer transaction scenario, and so on.
In operation S220, an operation parameter of each test script in the plurality of test scripts is obtained, where the operation parameter of each test script at least includes an interdependence relationship between the test script and other test scripts.
According to embodiments of the present disclosure, the operation parameters of each test script may include operation data of the test script, whether to add a scene branching node or checking node, an order of script configuration, a front-to-back item relationship, a collation relationship of input and output parameters between scripts, and the like. The dependency relationship may be the order of script configuration, the relation of the front and back items, the relation of the contrast of input and output parameters between scripts, and the like.
In operation S230, a plurality of test scripts are run based on the running parameters of each test script using an execution machine corresponding to each test script, resulting in a plurality of running results.
According to embodiments of the present disclosure, test scripts in a scenario may be scheduled for execution. For example, corresponding scripts are distributed to different execution machines to run according to different script execution platforms, and running results, data and screenshot are saved. After all the scripts in the scene are run, a user can check the running result in multiple dimensions and analyze the result.
In operation S240, it is determined whether the target transaction scenario is normal according to the plurality of operation results.
According to the embodiment of the disclosure, whether the plurality of operation results are consistent with the standard data or not can be determined, and in the case that the plurality of operation results are consistent with the standard data, it can be determined that the target transaction scenario is normal.
In the related art, when different types of test scripts are executed, parameter transfer cannot be performed by using an existing method, and after one test script is run, a script developed by another tool cannot be directly called. According to the embodiment of the disclosure, a plurality of test scripts of different types for verifying whether the target transaction scene is normal can be obtained, an execution machine corresponding to each test script is used for running the plurality of test scripts based on the running parameters of each test script, and whether the target transaction scene is normal is determined according to a plurality of running results. The test scripts with all functions can be directly and automatically connected in series and mutually carry out parameter transfer, even if test tools relied on by writing the automatic test scripts are different, or the requirements of environment configuration are different when all the scripts are executed, no manual intervention of a tester is needed in the test process, copy and paste of data output after each script is executed and input data are not needed, the technical problem that in the related art, manual intervention is needed when transaction scenes are tested through different types of scripts, and the service scene-level automatic test process is discontinuous is solved, and the test work efficiency is improved.
According to the embodiment of the disclosure, before the transaction scene is tested, the test scene editing interface can be displayed first, and the user can edit or select the test script required by the transaction scene on the test scene editing interface, so that the operation of the user is facilitated. The electronic device may obtain the operating parameters for each test script entered on the test scenario editing interface.
According to the embodiment of the disclosure, the automatic serial execution of test scripts written by different kinds of end-to-end test tools can be performed in the test scene editing interface. For example, test scripts written by test tools such as a WEB browser end, a mobile phone end, a PC client end and the like solve the problem that manual intervention is needed for collaborative execution when a plurality of types of automatic test scripts are contained in one transaction scene test in the related technology, thereby meeting the requirement of automatic test of complete business processes.
According to an embodiment of the present disclosure, the dependency relationship between the test script and the other test scripts includes an order of execution between the test script and the other test scripts, and executing the plurality of test scripts based on the execution parameters of each test script includes: in running the test scripts based on the running order of each test script, it is determined whether to adjust the running order of the test scripts to be executed, which are executed after the test scripts have been run, based on the running results of the test scripts which have been run.
According to an embodiment of the present disclosure, determining whether to adjust an execution order of test scripts to be executed, which are executed after the test scripts have been executed, based on an execution result of the test scripts which have been executed, includes: judging whether the running result of the running completed test script meets the branch condition, and determining the script executed after the running completed test script as the test script corresponding to the branch condition when the running result of the running completed test script meets the branch condition.
According to the embodiment of the disclosure, in the case that the running result of the already-running completed test script does not satisfy the branching condition, the script executed after the already-running completed test script may be executed according to the preset dependency relationship without changing the script executed after the already-running completed test script.
According to the embodiment of the disclosure, the subsequent script running path can be judged according to the result after the last node script running or the value of a certain output parameter. Judging whether the running result of the running completed test script satisfies the branching condition can be divided into two types: firstly, the corresponding path is selected after the true and false are judged according to the Boolean value. And the other is judged according to the value obtained by actual operation, for example, the current business is obtained as dollars, and then the script path corresponding to the dollars is operated.
According to the embodiment of the disclosure, the automatic test of the multi-branch flow service scene is supported through the mode of the series connection of the scenerized public script assembly and the configuration of the script execution branch flow. The method solves the problems that when the multi-branch flow test coverage service scene is related to the related technology, branch series connection cannot be carried out among common scripts, a plurality of branch flows need to be written in the same automation script, the function flow contained in a single automation script is overlong, and when a certain system function is changed, the maintenance and update workload of all the stored automation scripts related to the function is large, so that the automation workload investment of the coverage service scene is reduced.
According to an embodiment of the present disclosure, determining whether to adjust an execution order of test scripts to be executed, which are executed after the test scripts have been executed, based on an execution result of the test scripts which have been executed, includes: and checking the running result of the running completed test script according to the checking rule, and determining whether to adjust the running sequence of the test script to be executed, which is executed after the running of the completed test script, according to the checking result.
According to the embodiment of the disclosure, in the process of editing the transaction scene, check nodes can be added at the places needing to be checked, one or more check rules and corresponding parameter relations are set in the check nodes, and the function of automatic check is realized. After the scene operation sequence is set, parameter relation mapping of all scripts in the scene can be added, and one or more sets of operation data are added for the scene, so that script preparation and data preparation of the whole automatic test are completed. The check rule may be, for example, comparing the operation result with standard data stored in the background to determine whether the operation result is the same as the standard data.
According to the embodiment of the disclosure, data checking among different types of test scripts can be supported in the same transaction scene mode, and a tester can realize result checking and checking by setting a special result checking node, so that full-flow automatic testing of the business is supported.
The method illustrated in fig. 2 is further described below with reference to fig. 3 in conjunction with an exemplary embodiment.
Fig. 3 schematically illustrates a flow chart of a method of testing a transaction scenario in accordance with an embodiment of the present disclosure.
As shown in fig. 3, the method includes operations S301 to S313.
In operation S301, a scene is newly created and basic information is set.
In operation S302, a plurality of scripts as required are added to a scene.
According to embodiments of the present disclosure, scripts to be run in a transaction scenario test selected by a tester may be added to an automation scenario. Further, the running parameters of different scripts can also be set. For example, a relation between the foreground and the background of script operation and a relation between input and output parameters are set. In operation S303, a scene editing interface is entered.
In operation S304, it is determined whether the branch node needs to be set according to the scene test needs.
In operation S305, in the case where it is determined that the branch node needs to be set, the branch node is added, a branch judgment condition is set, and otherwise, operation S309 is directly performed.
In operation S306, the node positions of the corresponding test scripts are adjusted according to the branch judgment conditions.
In operation S307, it is determined whether the collation node needs to be set according to the scene test needs.
In operation S308, in the case where it is determined that the collation node needs to be set, the collation node is added, and the collation rule is set.
In operation S309, the execution order of each test script is configured according to the scene test needs.
In operation S310, input/output parameters of each test script are configured according to scene test requirements.
In operation S311, it is determined whether to save the scene, and if not, operation S303 is returned, and if the scene is saved, operation S312 is performed.
In operation S312, it is determined whether to submit the scene task, and if not, operation S303 is returned, and if the scene task is submitted, operation S313 is performed.
In operation S313, a scene task is submitted.
According to the embodiment of the disclosure, in the process of executing the test scripts required by the scene, the scripts in the scene can be automatically issued to the background public execution machine corresponding to the execution environment for operation, so that a tester does not need to prepare environment maintenance workload of a plurality of script execution environments. Meanwhile, through the mode of automatic capacity expansion of the background public executor, the number of executors can be increased or reduced automatically according to the condition of the task to be executed, the actual test time is saved, the test efficiency is improved, and the utilization rate of environmental resources is improved.
According to the embodiment of the disclosure, script scene assembly configuration can be performed aiming at different test tools and test platforms, so that functions of script automatic call of different functions according to business processes and input/output parameter transfer among scripts are supported, and the aim of full-process test automation is fulfilled. Meanwhile, the visual scene script assembly and parameter configuration can be realized through a system interface access mode. By providing the execution mode of the background unattended shared execution machine environment, the requirement of different types of scripts on the diversity of the execution machine environment is met, the computer resources of testers are further released, and the working efficiency is improved.
Fig. 4 schematically illustrates a block diagram of a testing device of a transaction scenario according to an embodiment of the present disclosure.
As shown in fig. 4, the testing apparatus 400 of the transaction scenario includes a first acquisition module 410, a second acquisition module 420, an operation module 430, and a determination module 440.
The first obtaining module 410 is configured to obtain a plurality of test scripts of different types, where the plurality of test scripts are used to verify whether the target transaction scenario is normal.
The second obtaining module 420 is configured to obtain an operation parameter of each test script of the plurality of test scripts, where the operation parameter of each test script at least includes an interdependence relationship between the test script and other test scripts.
The operation module 430 is configured to use an execution machine corresponding to each test script to operate a plurality of test scripts based on the operation parameters of each test script, so as to obtain a plurality of operation results.
The determining module 440 is configured to determine whether the target transaction scenario is normal according to the plurality of operation results.
According to an embodiment of the present disclosure, the test apparatus 400 for a transaction scenario further includes a display module for displaying a test scenario editing interface.
According to embodiments of the present disclosure, the second obtaining module 420 may be configured to obtain the operation parameters for each test script input on the test scenario editing interface.
According to an embodiment of the present disclosure, the dependency relationship between the test script and other test scripts includes an execution order between the test script and other test scripts, and the execution module 430 is configured to determine, in executing the test script based on the execution order of each test script, whether to adjust an execution order of the test script to be executed after the test script has been executed based on an execution result of the test script that has been completed.
According to an embodiment of the present disclosure, determining whether to adjust an execution order of a test script to be executed, which is executed after the test script has been executed, based on an execution result of the test script that has been executed, includes determining whether the execution result of the test script that has been executed satisfies a branching condition; in the case where the branching condition is satisfied, a script executed after the completed test script has been run is determined as a test script corresponding to the branching condition.
According to an embodiment of the present disclosure, determining whether to adjust an execution order of test scripts to be executed, which are executed after the test scripts have been executed, based on an execution result of the test scripts which have been executed, includes: checking the running result of the running test script according to the checking rule; and determining whether to adjust the running sequence of the test script to be executed, which is executed after the completed test script has been executed, according to the checking result.
According to an embodiment of the present disclosure, the determining module 440 is configured to determine whether the plurality of operation results are consistent with the standard data; and under the condition that the plurality of operation results are consistent with the standard data, determining that the target transaction scene is normal.
According to embodiments of the present disclosure, the plurality of test scripts of different types include test scripts developed using different tools, and/or test scripts having different operating environments.
According to embodiments of the present disclosure, an execution machine corresponding to each test script may be scheduled before executing the test script using the execution machine.
For example, the present disclosure may provide a scheduling execution module responsible for scheduling and executing a scenario. Firstly, splitting a scene to be executed by taking a script as a unit, and distributing test script execution tasks to execution queues of corresponding execution machines according to overall scene execution conditions, requirements of each test script on execution environments of the execution machines, indexes such as configuration, idle state and the like of each execution machine environment of a background shared execution machine pool. Then, the execution machine acquires the task from the execution queue, prepares an execution environment required by the task, and starts executing the task. The disclosure may further provide an execution machine monitoring module, collect information of the whole execution process, and record information such as a key script node and a final execution result of the execution process to a database for storage.
According to an embodiment of the present disclosure, a scheduling execution module includes a task scheduling unit, a task execution unit, and a result recording unit.
The task scheduling unit is responsible for splitting scenes and distributing tasks. All scenes are split by taking nodes as granularity, and single nodes are executed in sequence. And acquiring node environment information to be executed according to the scene execution information, and then integrating the execution environment and task queuing states of each execution machine in the execution machine pool and the requirements of the scene on factors such as execution time, execution priority and the like, and distributing the requirements to an execution queue of a proper execution machine.
The task execution unit is used for ensuring the smooth execution of the node task. And after the execution of the last task node is finished, the execution machine in the execution machine pool acquires the next task node from the execution queue allocated to the execution machine pool. And judging whether the environment is required to be switched according to the environment information of the next task node, and calling the script to execute after the environment is prepared.
The result recording unit is used for recording the execution process and the execution result. After the script begins to run, the unit begins to monitor the entire execution. The key execution point set at the node and the default key execution point of the unit can be used for saving and recording the execution site. And meanwhile, after the script is executed, the unit transmits key information which is captured in the execution process and needs to be used by a subsequent node in reference to the subsequent node, judges whether a final operation result is correct, and records the operation result, related execution log and other information.
After the operation is finished, the execution result and the output parameters of each script in the scene can be checked through operation screenshot, log and the like.
According to embodiments of the present disclosure, a testing apparatus of a transaction scenario may include a schedule execution module and an execution machine monitoring module.
Any number of modules, sub-modules, units, sub-units, or at least some of the functionality of any number of the sub-units according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented as split into multiple modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or in any other reasonable manner of hardware or firmware that integrates or encapsulates the circuit, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be at least partially implemented as computer program modules, which when executed, may perform the corresponding functions.
For example, any of the first acquisition module 410, the second acquisition module 420, the execution module 430, and the determination module 440 may be combined in one module/unit/sub-unit or any of the modules/units/sub-units may be split into a plurality of modules/units/sub-units. Alternatively, at least some of the functionality of one or more of these modules/units/sub-units may be combined with at least some of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to embodiments of the present disclosure, at least one of the first acquisition module 410, the second acquisition module 420, the execution module 430, and the determination module 440 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging the circuitry, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the first acquisition module 410, the second acquisition module 420, the execution module 430, and the determination module 440 may be at least partially implemented as a computer program module, which when executed, may perform the corresponding functions.
It should be noted that, in the embodiment of the present disclosure, the test device portion corresponds to the test method portion in the embodiment of the present disclosure, and the description of the test device portion specifically refers to the test method portion and is not described herein again.
The present disclosure also provides an electronic device, including: one or more processors; and a memory configured to store one or more instructions that, when executed by the one or more processors, cause the one or more processors to implement the test methods provided by the present disclosure.
In accordance with an embodiment of the present disclosure, an electronic device is taken as an example of a computer system.
Fig. 5 schematically illustrates a block diagram of a computer system suitable for implementing the test methods described above, in accordance with an embodiment of the present disclosure. The computer system illustrated in fig. 5 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present disclosure.
As shown in fig. 5, a computer system 500 according to an embodiment of the present disclosure includes a processor 501, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. The processor 501 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 501 may also include on-board memory for caching purposes. The processor 501 may comprise a single processing unit or a plurality of processing units for performing different actions of the method flows according to embodiments of the disclosure.
In the RAM 503, various programs and data required for the operation of the system 500 are stored. The processor 501, ROM 502, and RAM 503 are connected to each other by a bus 504. The processor 501 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 502 and/or the RAM 503. Note that the program may be stored in one or more memories other than the ROM 502 and the RAM 503. The processor 501 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the present disclosure, the system 500 may further include an input/output (I/O) interface 505, the input/output (I/O) interface 505 also being connected to the bus 504. The system 500 may also include one or more of the following components connected to the I/O interface 505: an input section 506 including a keyboard, a mouse, and the like; an output portion 507 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The drive 510 is also connected to the I/O interface 505 as needed. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as needed so that a computer program read therefrom is mounted into the storage section 508 as needed.
According to embodiments of the present disclosure, the method flow according to embodiments of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 509, and/or installed from the removable media 511. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 501. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.
The present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to implement the test methods provided by the present disclosure.
According to an embodiment of the present disclosure, the computer-readable storage medium may be contained in the apparatus/device/system described in the above embodiment; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 502 and/or RAM 503 and/or one or more memories other than ROM 502 and RAM 503 described above.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.
The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.
Claims (8)
1. A method for testing a transaction scenario, comprising:
acquiring a plurality of test scripts of different types, wherein the plurality of test scripts are used for verifying whether a target transaction scene is normal, the plurality of test scripts of different types comprise test scripts developed by using different tools and/or test scripts with different running environments, and the target transaction scene is a multi-branch flow service scene;
acquiring operation parameters of each test script in the plurality of test scripts, wherein the operation parameters of each test script at least comprise the interdependence relationship between the test script and other test scripts;
Scheduling and executing each test script by using an executing machine corresponding to each test script, running the plurality of test scripts based on the running parameters of each test script, and judging a subsequent script running path according to the branching condition met by the running result of the last node script to obtain a plurality of running results, wherein the branching condition comprises: the Boolean value of the result after operation or the value of the output parameter obtained by actual operation; and
determining whether the target transaction scene is normal according to the operation results;
and judging the running path of the next script according to the branching condition satisfied by the running result of the previous node script to obtain a plurality of running results, wherein the method comprises the following steps:
determining a script executed after the completed test script is executed as a test script corresponding to the branch condition under the condition that the result meets the branch condition;
and executing the script executed after the running test script according to the preset dependency relationship under the condition that the result does not meet the branch condition.
2. The method of claim 1, further comprising:
displaying a test scene editing interface;
Wherein, obtaining the operation parameter of each test script in the plurality of test scripts comprises: and acquiring the operation parameters input on the test scene editing interface for each test script.
3. The method of claim 1, wherein the dependency between the test script and the other test scripts includes an order of execution between the test script and the other test scripts, and executing the plurality of test scripts based on the execution parameters of each test script includes:
in the process of running the test scripts based on the running sequence of each test script, determining whether to adjust the running sequence of the test script to be executed, which is executed after the running test script, based on the running result of the test script which is already run.
4. The method of claim 3, wherein determining whether to adjust the order of execution of test scripts to be executed that are executed after the already-executed test scripts based on the result of execution of the already-executed test scripts comprises:
checking the running result of the running test script according to the checking rule; and
And determining whether to adjust the running sequence of the test script to be executed, which is executed after the test script which is already executed, according to the checking result.
5. The method of claim 1, wherein determining whether the target transaction scenario is normal based on the plurality of operational results comprises:
determining whether the plurality of operation results are consistent with standard data; and
and under the condition that the running results are consistent with the standard data, determining that the target transaction scene is normal.
6. A transaction scenario testing device, comprising:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a plurality of test scripts of different types, the plurality of test scripts are used for verifying whether a target transaction scene is normal, the plurality of test scripts of different types comprise test scripts developed by using different tools and/or test scripts with different running environments, and the target transaction scene is a multi-branch flow service scene;
the second acquisition module is used for acquiring the operation parameters of each test script in the plurality of test scripts, wherein the operation parameters of each test script at least comprise the interdependence relationship between the test script and other test scripts;
The running module is used for scheduling and executing each test script by using an execution machine corresponding to each test script, running the plurality of test scripts based on the running parameters of each test script, judging the running paths of the following scripts according to the branching conditions met by the running result of the last node script, and obtaining a plurality of running results, wherein the branching conditions comprise: the Boolean value of the result after operation or the value of the output parameter obtained by actual operation; and
the determining module is used for determining whether the target transaction scene is normal or not according to the operation results;
and judging the running path of the next script according to the branching condition satisfied by the running result of the previous node script to obtain a plurality of running results, wherein the method comprises the following steps:
determining a script executed after the completed test script is executed as a test script corresponding to the branch condition under the condition that the result meets the branch condition;
and executing the script executed after the running test script according to the preset dependency relationship under the condition that the result does not meet the branch condition.
7. An electronic device, comprising:
One or more processors;
a memory for storing one or more instructions,
wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1 to 5.
8. A computer readable storage medium having stored thereon executable instructions which when executed by a processor cause the processor to implement the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910664165.1A CN110377520B (en) | 2019-07-22 | 2019-07-22 | Transaction scenario testing method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910664165.1A CN110377520B (en) | 2019-07-22 | 2019-07-22 | Transaction scenario testing method and device, electronic equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110377520A CN110377520A (en) | 2019-10-25 |
| CN110377520B true CN110377520B (en) | 2024-03-15 |
Family
ID=68254907
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910664165.1A Active CN110377520B (en) | 2019-07-22 | 2019-07-22 | Transaction scenario testing method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110377520B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110968504A (en) * | 2019-11-07 | 2020-04-07 | 京东数字科技控股有限公司 | Test method, test platform, electronic device and computer storage medium |
| CN111274147B (en) * | 2020-01-21 | 2021-04-27 | 珠海必要工业科技股份有限公司 | Automatic script testing method and device, electronic equipment and readable medium |
| CN111640019A (en) * | 2020-05-12 | 2020-09-08 | 中信银行股份有限公司 | Method and device for acquiring test data, storage medium and electronic device |
| CN111639022B (en) * | 2020-05-16 | 2023-06-06 | 中信银行股份有限公司 | Transaction testing method and device, storage medium and electronic device |
| CN111881025B (en) * | 2020-07-20 | 2023-08-04 | 中国工商银行股份有限公司 | Automatic test task scheduling method, device and system |
| CN114092169A (en) * | 2020-10-20 | 2022-02-25 | 北京沃东天骏信息技术有限公司 | Ordering test method and system and equipment for executing ordering test method |
| CN112887342B (en) * | 2021-04-29 | 2021-07-23 | 湖北亿咖通科技有限公司 | Service scheduling method, vehicle-mounted service processing system, electronic device and storage medium |
| CN113392002B (en) * | 2021-06-15 | 2024-04-12 | 北京京东振世信息技术有限公司 | Test system construction method, device, equipment and storage medium |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1952818A (en) * | 2005-10-22 | 2007-04-25 | 康佳集团股份有限公司 | Testing method of program unit with capability of checking test result automatically |
| CN101212362A (en) * | 2006-12-26 | 2008-07-02 | 中兴通讯股份有限公司 | Automatic testing device and method incorporating a variety of testing tools |
| CN102169455A (en) * | 2010-02-26 | 2011-08-31 | 国际商业机器公司 | Debugging method and system for software performance test |
| CN102789414A (en) * | 2011-04-12 | 2012-11-21 | 埃森哲环球服务有限公司 | Prioritization and assignment manager for an integrated testing platform |
| CN103514088A (en) * | 2012-06-19 | 2014-01-15 | 珠海世纪鼎利通信科技股份有限公司 | Function regression testing method for terminal application software |
| CN106598874A (en) * | 2017-02-08 | 2017-04-26 | 郑州云海信息技术有限公司 | Method and device for automatically testing software |
| CN106844190A (en) * | 2015-12-07 | 2017-06-13 | 中兴通讯股份有限公司 | test script automatic generation method and device |
| CN106874204A (en) * | 2017-02-15 | 2017-06-20 | 广州神马移动信息科技有限公司 | Automatic test method for customizing and custom-built system |
| CN107463500A (en) * | 2017-08-09 | 2017-12-12 | 网易（杭州）网络有限公司 | Adjustment method, medium, system and the computing device of test script |
| CN107608902A (en) * | 2017-10-23 | 2018-01-19 | 中国联合网络通信集团有限公司 | Routine interface method of testing and device |
| CN107766252A (en) * | 2017-11-08 | 2018-03-06 | 平安科技（深圳）有限公司 | Test script automated execution method, apparatus, equipment and storage medium |
| US10210074B1 (en) * | 2018-06-07 | 2019-02-19 | Capital One Services, Llc | Performance testing platform that enables reuse of automation scripts and performance testing scalability |
| CN109522214A (en) * | 2018-10-09 | 2019-03-26 | 广州神马移动信息科技有限公司 | Test method, platform, client and system calculate equipment and readable medium |
| CN109726093A (en) * | 2017-10-27 | 2019-05-07 | 伊姆西Ip控股有限责任公司 | Method, equipment and computer program product for implementation of test cases |
-
2019
- 2019-07-22 CN CN201910664165.1A patent/CN110377520B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1952818A (en) * | 2005-10-22 | 2007-04-25 | 康佳集团股份有限公司 | Testing method of program unit with capability of checking test result automatically |
| CN101212362A (en) * | 2006-12-26 | 2008-07-02 | 中兴通讯股份有限公司 | Automatic testing device and method incorporating a variety of testing tools |
| CN102169455A (en) * | 2010-02-26 | 2011-08-31 | 国际商业机器公司 | Debugging method and system for software performance test |
| CN102789414A (en) * | 2011-04-12 | 2012-11-21 | 埃森哲环球服务有限公司 | Prioritization and assignment manager for an integrated testing platform |
| CN103514088A (en) * | 2012-06-19 | 2014-01-15 | 珠海世纪鼎利通信科技股份有限公司 | Function regression testing method for terminal application software |
| CN106844190A (en) * | 2015-12-07 | 2017-06-13 | 中兴通讯股份有限公司 | test script automatic generation method and device |
| CN106598874A (en) * | 2017-02-08 | 2017-04-26 | 郑州云海信息技术有限公司 | Method and device for automatically testing software |
| CN106874204A (en) * | 2017-02-15 | 2017-06-20 | 广州神马移动信息科技有限公司 | Automatic test method for customizing and custom-built system |
| CN107463500A (en) * | 2017-08-09 | 2017-12-12 | 网易（杭州）网络有限公司 | Adjustment method, medium, system and the computing device of test script |
| CN107608902A (en) * | 2017-10-23 | 2018-01-19 | 中国联合网络通信集团有限公司 | Routine interface method of testing and device |
| CN109726093A (en) * | 2017-10-27 | 2019-05-07 | 伊姆西Ip控股有限责任公司 | Method, equipment and computer program product for implementation of test cases |
| CN107766252A (en) * | 2017-11-08 | 2018-03-06 | 平安科技（深圳）有限公司 | Test script automated execution method, apparatus, equipment and storage medium |
| US10210074B1 (en) * | 2018-06-07 | 2019-02-19 | Capital One Services, Llc | Performance testing platform that enables reuse of automation scripts and performance testing scalability |
| CN109522214A (en) * | 2018-10-09 | 2019-03-26 | 广州神马移动信息科技有限公司 | Test method, platform, client and system calculate equipment and readable medium |
Non-Patent Citations (1)
| Title |
|---|
| 基于BDD的数据驱动自动化测试方法;柳晓华等;《青岛大学学报(自然科学版)》;20160815(第03期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110377520A (en) | 2019-10-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110377520B (en) | Transaction scenario testing method and device, electronic equipment and readable storage medium | |
| CN110389903B (en) | Test environment deployment method and device, electronic equipment and readable storage medium | |
| CN102868573B (en) | Method and device for Web service load cloud test | |
| CN108255707B (en) | Development role creating method, device, equipment and storage medium of test case | |
| CN111563014A (en) | Interface service performance test method, device, equipment and storage medium | |
| CN107045475B (en) | Test method and device | |
| CN111290941A (en) | Method and device for testing multiple interfaces, computing equipment and medium | |
| CN114818565A (en) | Simulation environment management platform, method, equipment and medium based on python | |
| CN112988185A (en) | Cloud application updating method, device and system, electronic equipment and storage medium | |
| CN107038120A (en) | A kind of method for testing software and equipment | |
| CN112346965A (en) | Test case distribution method, device and storage medium | |
| CN114817050A (en) | Task execution method and device, electronic equipment and computer readable storage medium | |
| CN113094081B (en) | Software release method, device, computer system and computer readable storage medium | |
| CN112256588A (en) | Resource allocation method for application program test, computer readable storage medium and tester | |
| CN110717992B (en) | Method, apparatus, computer system and readable storage medium for scheduling model | |
| CN105893233A (en) | Method and system used for automatically testing firmware | |
| CN112199273A (en) | Virtual machine pressure/performance testing method and system | |
| US10176062B2 (en) | Cloud servers and methods for handling dysfunctional cloud services | |
| CN113392002B (en) | Test system construction method, device, equipment and storage medium | |
| CN105868957A (en) | Continuous integration method and device | |
| CN115237441A (en) | Upgrade test method, device and medium based on cloud platform | |
| CN114328196A (en) | Method, device and equipment for testing data leakage prevention system and storage medium | |
| CN112183982A (en) | Workflow creating method and device, computer equipment and storage medium | |
| CN109614295A (en) | A kind of server energy consumption test method and device | |
| CN114741325B (en) | Recording method and device of test script for application system test |
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 |