CN117407280A - Determination method and device of test result, storage medium and electronic device - Google Patents
Determination method and device of test result, storage medium and electronic device Download PDFInfo
- Publication number
- CN117407280A CN117407280A CN202311119092.0A CN202311119092A CN117407280A CN 117407280 A CN117407280 A CN 117407280A CN 202311119092 A CN202311119092 A CN 202311119092A CN 117407280 A CN117407280 A CN 117407280A
- Authority
- CN
- China
- Prior art keywords
- identification code
- test
- determining
- application software
- tested
- 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.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 218
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000006870 function Effects 0.000 claims description 111
- 238000004590 computer program Methods 0.000 claims description 14
- 230000008569 process Effects 0.000 description 17
- 238000012544 monitoring process Methods 0.000 description 10
- 238000012795 verification Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 238000004519 manufacturing process Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000013522 software testing Methods 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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
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)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method and a device for determining a test result, a storage medium and an electronic device, wherein the method comprises the following steps: responding to a test instruction of a target object, and performing target transaction function test on the application software to be tested; determining an execution result of the identification transaction code when the application software to be tested performs the transaction function test target function test; and under the condition that the execution result is determined to be the execution failure, determining the test result of the application software to be tested based on the transaction code identification code white list. By adopting the technical scheme, the problem of how to improve the determination efficiency of the test result is solved.
Description
Technical Field
The present invention relates to the field of software testing, and in particular, to a method and apparatus for determining a test result, a storage medium, and an electronic apparatus.
Background
At present, before the development version of the application software is formally put into production, the transaction function of the put-to-production version needs to be tested in a version check stage, and only the transaction function passing the check can be put into production. However, in the actual version verification test, verification failure is often caused by the fact that part of the transaction codes cannot be monitored. In the related art, a mode of manually monitoring a transaction code is generally adopted to determine a test result of a transaction function so as to finish functional test calibration, but a manual monitoring mode cannot automatically determine a test result, and particularly under the conditions of more production systems and frequent version production, the workload required to be processed is greatly increased, and the number of workers is limited, so that the determination efficiency of the test result is lower.
Aiming at the problem of how to improve the determination efficiency of the test result in the related art, no effective solution is proposed at present.
Accordingly, there is a need for improvements in the related art to overcome the drawbacks of the related art.
Disclosure of Invention
The embodiment of the invention provides a method and a device for determining a test result, a storage medium and an electronic device, which are used for at least solving the problem of how to improve the determination efficiency of the test result.
According to an aspect of the embodiment of the present invention, there is provided a method for determining a test result, including: responding to a test instruction of a target object, and performing target function test on the application software to be tested; determining an execution result of the identification code when the application software to be tested performs the target function test; and under the condition that the execution result is determined to be the execution failure, determining the test result of the application software to be tested based on the identification code white list.
In an exemplary embodiment, determining the execution result of the identification code when the application software to be tested performs the target function test includes: determining a first identification code required by the application software to be tested when performing target function test; acquiring a second identification code monitored when the application software to be tested performs target function test; if the second identification code is determined to be consistent with the first identification code, if the execution result of the second identification code is failure, determining that the execution result of the identification code when the application software to be tested performs the target function test is failure; and if the execution result of the second identification code is successful, determining that the execution result of the identification code when the application software to be tested performs the target function test is successful.
In an exemplary embodiment, determining the first identification code required by the application software to be tested in performing the target function test includes: determining a target transaction type indicated by the target object from the test instruction; acquiring a target identification code database matched with the target transaction type from a preset identification code database; the preset identification code database is stored with a plurality of sub-databases, and each sub-database of the plurality of sub-databases is used for storing identification codes of different transaction types; and determining the identification code in the target identification code database as a first identification code required by the application software to be tested when the target function test is carried out.
In an exemplary embodiment, the identification code whitelist is determined by one of the following means: determining a first identification code required by the application software to be tested when performing target function test; acquiring a second identification code monitored when the application software to be tested performs target function test; under the condition that the second identification code is inconsistent with the first identification code, an initial identification code white list is obtained, and the initial identification code white list is updated based on the first identification code to obtain the identification code white list; and under the condition that the second identification code is consistent with the first identification code, acquiring an initial identification code white list, and updating the initial identification code white list by using the second identification code with the execution result of failure to acquire the identification code white list.
In an exemplary embodiment, before determining the test result of the application software to be tested based on the generated identifier code white list, the method further comprises: determining all identification codes corresponding to the application software to be tested from the history test record of the application software to be tested; wherein, each identification code of all the identification codes corresponds to a test result; determining the identification code with the failed test result from all the identification codes, and generating the identification code white list by using the identification code with the failed test result; wherein, the identification codes in the identification code white list at least comprise: the identification codes that have been executed and failed to be executed, and the identification codes that have not been executed.
In an exemplary embodiment, after generating the identification code whitelist for failed identification codes using the test result, the method further comprises: acquiring a third identification code with an execution result of successful execution from the monitored identification code of the application software to be tested; deleting the third identification code from the identification code whitelist if it is determined that the third identification code exists in the identification code whitelist; and setting the third identification code as an identification code required by the application software to be tested when the target function test is performed.
In an exemplary embodiment, determining the test result of the application software to be tested based on the identifier code white list includes: determining the execution result as a fourth identification code of execution failure; for a plurality of fourth identification codes, acquiring default execution results set for the fourth identification codes from the identification code white list under the condition that the fourth identification codes are determined to exist in the identification code white list; wherein the default execution result comprises an execution result of successful execution; and determining the default execution result as the execution result of the plurality of fourth identification codes, and determining the test result of the application software to be tested as the test success.
According to another aspect of the embodiment of the present invention, there is also provided a device for determining a test result, including: the target function test module is used for responding to the test instruction of the target object and carrying out target function test on the application software to be tested; the execution result determining module is used for determining the execution result of the identification code when the application software to be tested performs the target function test; and the test result determining module is used for determining the test result of the application software to be tested based on the identification code white list under the condition that the execution result is determined to be the execution failure.
According to a further aspect of embodiments of the present invention, there is also provided a computer-readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the above-described method of determining test results when run.
According to still another aspect of the embodiments of the present invention, there is further provided an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the method for determining the test result by the computer program.
According to the method and the device, after the test instruction of the target object is responded, the target function test is carried out on the application software to be tested, the identification code execution result when the application software to be tested carries out the target function test is further obtained, and the identification code white list is used for determining that the execution result is the test result of the application software to be tested with the execution failure. By adopting the technical scheme, the problem of how to improve the determination efficiency of the test result in the related technology is solved. And further, the effect of improving the function test efficiency can be realized.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a block diagram of the hardware architecture of a computer terminal that performs a method of determining test results according to an embodiment of the present invention;
FIG. 2 is a flow chart of a method of determining test results according to an embodiment of the invention;
FIG. 3 is a block diagram of a transaction code whitelisting apparatus according to an embodiment of the invention;
FIG. 4 is a schematic flow chart of transaction code whitelist generation and maintenance in accordance with an embodiment of the invention;
FIG. 5 is a schematic flow chart diagram (one) of transaction code verification in accordance with an embodiment of the present invention;
FIG. 6 is a schematic flow chart diagram (II) of a transaction code verification in accordance with an embodiment of the invention;
fig. 7 is a block diagram of a configuration of a determination device of a test result according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms and "first," "second," and the like in the description and claims of the present invention and the above-described drawings are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The method embodiments provided in the embodiments of the present invention may be executed in a computer terminal or similar computing device. Taking the example of running on a computer terminal, fig. 1 is a block diagram of the hardware structure of the computer terminal for executing the method for determining the test result according to the embodiment of the present invention. As shown in fig. 1, the computer terminal may include one or more processors 102 (only one is shown in fig. 1), which processor 102 may include, but is not limited to, a microprocessor (Microprocessor Unit, abbreviated MPU) or programmable logic device (Programmable logic device, abbreviated PLD) and a memory 104 configured to store data, and in one exemplary embodiment, a transmission device 106 configured to communicate with an input/output device 108.
The memory 104 may be configured to store a computer program, for example, a software program of application software and a module, such as a computer program corresponding to a method for determining a test result in an embodiment of the present invention, and the processor 102 executes the computer program stored in the memory 104, thereby performing various functional applications and data processing, that is, implementing the above-described method. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located relative to the processor 102, which may be connected to the computer terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 106 is arranged to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of a computer terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module configured to communicate wirelessly with the internet.
In this embodiment, a method for determining a test result is provided, and fig. 2 is a flowchart of a method for determining a test result according to an embodiment of the present invention, where the flowchart includes the following steps:
step S202, responding to a test instruction of a target object, and performing target function test on the application software to be tested;
step S204, determining an execution result of the identification code when the application software to be tested performs the target function test;
step S206, determining the test result of the application software to be tested based on the identifier code white list if the execution result is determined to be the execution failure.
Through the steps, responding to the test instruction of the target object, and performing target function test on the application software to be tested; determining an execution result of the identification code when the application software to be tested performs the target function test; and under the condition that the execution result is determined to be the execution failure, determining the test result of the application software to be tested based on the identification code white list. The embodiment solves the problem of how to improve the determination efficiency of the test result in the related technology, and further can realize the effect of improving the function test efficiency.
Optionally, in step S202, the target function test includes a transaction function test, and the transaction function includes: the online transaction and batch transaction are that user requests are received and processed in real time, transaction data are required to be updated in real time after the processing is completed, and processing results are sent to users; batch transactions refer to the centralized processing of a batch of transaction data, e.g., batch settlement of various transactions by a user at the end of each day, followed by updating of the transaction data.
Optionally, in step S204, the identification code may include a transaction code of the online transaction, that is, a serial number of the online transaction.
Optionally, in step S206, the identifier code whitelist is automatically created by the program, and the whitelist is dynamically changed.
Optionally, in step S206, the initializing the identifier whitelist includes: and automatically adding the identification code to the identification code white list when the identification code execution result at the time of target function test in the test environment does not exist as the successful execution within the last year.
Optionally, for the case that the execution result of the identifier code is an execution failure, in addition to directly monitoring that the execution result of the identifier code is an execution failure, the method may further include: the execution result of the identification code is not monitored, or the execution record of the identification code is not monitored; the reason why the execution record of the identification code is not monitored is that the execution record is not monitored due to the fact that the execution record cannot be normally tested when the execution record is tested by a third party.
Optionally, in the above embodiment, the reason for the failure of executing the identification code, such as that the returned status value is not unique, results in that the monitoring rule cannot be configured.
In an exemplary embodiment, for the implementation process of determining the execution result of the identification code when the application software to be tested performs the target function test in the step S204, the implementation process may further include: step S11, determining a first identification code required by the application software to be tested for performing target function test; step S12, acquiring a second identification code monitored when the application software to be tested performs target function test; step S13, if the second identification code is determined to be consistent with the first identification code, if the execution result of the second identification code is failure, determining that the execution result of the identification code when the application software to be tested performs the target function test is failure; step S14, if the execution result of the second identification code is successful, determining that the execution result of the identification code when the application software to be tested performs the target function test is successful.
In this embodiment, the target function test is exemplified by a transaction function test, the identification code corresponds to a transaction code of the transaction function test, and when the execution result of the transaction code is monitored to be successful, the test result of the transaction function regression test is passed. And when the transaction code execution result is monitored to be successful, the check result of the transaction function regression test is passed. When the execution result of the transaction code is monitored to be failed or not tested, the test result of the transaction function regression test is failed.
In an exemplary embodiment, for the implementation process of determining the first identifier required for the target function test of the application software to be tested in step S11, the implementation process may specifically include: determining a target transaction type indicated by the target object from the test instruction; acquiring a target identification code database matched with the target transaction type from a preset identification code database; the preset identification code database is stored with a plurality of sub-databases, and each sub-database of the plurality of sub-databases is used for storing identification codes of different transaction types; and determining the identification code in the target identification code database as a first identification code required by the application software to be tested when the target function test is carried out.
Optionally, in the above embodiment, the transaction type may include a transaction function applied offline, such as code scanning payment, card swiping payment, and the like, and the transaction type may also include a transaction function applied online, such as internet banking payment, third party platform payment, and the like, which is not limited in this embodiment.
In an exemplary embodiment, the identification code whitelist is determined by one of the following means: determining a first identification code required by the application software to be tested when performing target function test; acquiring a second identification code monitored when the application software to be tested performs target function test; under the condition that the second identification code is inconsistent with the first identification code, an initial identification code white list is obtained, and the initial identification code white list is updated based on the first identification code to obtain the identification code white list; and under the condition that the second identification code is consistent with the first identification code, acquiring an initial identification code white list, and updating the initial identification code white list by using the second identification code with the execution result of failure to acquire the identification code white list.
Alternatively, in the above embodiment, the case where the second identifier is determined to be inconsistent with the first identifier may be understood that the first identifier is not monitored and the second identifier is monitored when the application software to be tested performs the target function test. At this time, the updating of the initial identification code whitelist may be achieved by adding the second identification code to the initial identification code whitelist.
Optionally, in the foregoing embodiment, the determining that the second identifier is inconsistent with the first identifier may also be understood that the second identifier monitored when the application software to be tested performs the target function test is not the first identifier required when the application software to be tested performs the target function test, and at this time, the execution result of the second identifier is manually confirmed.
Optionally, in the foregoing embodiment, the case where it is determined that the second identifier is identical to the first identifier may be understood that the second identifier monitored when the application software to be tested performs the target function test is the first identifier required when the application software to be tested performs the target function test. At this time, if the execution result of the second identification code is monitored to be the execution failure, the initial identification code white list is updated by using the second identification code with the execution failure, and the identification code white list is obtained.
Alternatively, in the above embodiment, the identifier code whitelist may be generated by: if the identification codes which do not belong to the history execution record are monitored in the test process, adding the identification codes which do not belong to the history execution record to an initial identification code white list to generate an identification code white list; if the identification code with the execution result of failure is present in the test process, the identification code with the execution result of failure is added to the initial identification code white list to generate the identification code white list.
In an exemplary embodiment, before performing the above step S13, the method further includes the following process: determining all identification codes corresponding to the application software to be tested from the history test record of the application software to be tested; wherein, each identification code of all the identification codes corresponds to a test result; determining the identification code with the failed test result from all the identification codes, and generating the identification code white list by using the identification code with the failed test result; wherein, the identification codes in the identification code white list at least comprise: the identification codes that have been executed and failed to be executed, and the identification codes that have not been executed.
In an exemplary embodiment, after generating the identification code whitelist for the failed identification codes using the test result, the following is also performed: acquiring a third identification code with an execution result of successful execution from the monitored identification code of the application software to be tested; deleting the third identification code from the identification code whitelist if it is determined that the third identification code exists in the identification code whitelist; and setting the third identification code as an identification code required by the application software to be tested when the target function test is performed.
In one exemplary embodiment, the above step S206 may be performed by: determining the execution result as a fourth identification code of execution failure; for a plurality of fourth identification codes, acquiring default execution results set for the fourth identification codes from the identification code white list under the condition that the fourth identification codes are determined to exist in the identification code white list; wherein the default execution result comprises an execution result of successful execution; and determining the default execution result as the execution result of the plurality of fourth identification codes, and determining the test result of the application software to be tested as the test success.
It will be apparent that the embodiments described above are merely some, but not all, embodiments of the invention. In order to better understand the determination method of the test result, the following description will explain the above process with reference to the embodiments, but is not intended to limit the technical solution of the embodiments of the present invention, specifically:
in an alternative embodiment, fig. 3 provides a transaction code whitelisting apparatus for implementing some or all of the functions of the above-described determination apparatus for test results. As shown in fig. 3, the transaction code whitelist device 300 specifically includes a transaction code storage unit 301, a transaction code history execution result obtaining unit 302, and a transaction code whitelist generating unit 303, where the transaction code storage unit 301 is configured to store transaction codes (corresponding to identification codes) corresponding to all functions of the application software to be tested that need to be tested for the target function, and when operations such as adding, modifying, or deleting the functions of the application software to be tested that need to be tested for the target function occur, the transaction code storage unit 301 adds, modifies, or deletes the transaction codes corresponding to the target function synchronously.
Through the transaction code white list device, transaction codes corresponding to all functions of the application software to be tested, which need to be subjected to target function test, can be obtained, and the transaction code white list (equivalent to the identification code white list) is automatically generated and maintained based on the historical execution record of the transaction codes in the test environment.
Fig. 4 is a schematic flowchart of generating and maintaining a transaction code whitelist according to an embodiment of the present invention, and the following descriptions are provided for describing the operations of each unit in the transaction code whitelist device of fig. 3 and the flow of generating and maintaining the transaction code, as shown in fig. 4, specifically including the following steps:
step S402: the transaction code whitelist device 300 begins operation.
Step S404: the transaction code white list generation unit 303 eventually polls the transaction codes stored in the transaction code storage unit 301.
Step S406: the transaction code history execution result acquisition unit 302 acquires the history execution result of the polled transaction code in the test environment in the last year from the transaction code monitoring platform. The transaction code execution results comprise success, failure and untested three execution results, wherein the transaction code with the success or failure result is not obtained, namely the untested transaction code (equivalent to the unexecuted identification code).
Through the steps, an example of determining the test results of all the identification codes corresponding to the application software to be tested from the historical test records of the application software to be tested is provided.
Step S408: judging whether the transaction code polled in the step S404 has a history of successful execution in the last year in the test environment, if the transaction code has no history of successful execution, executing the step S410. Otherwise, step S412 is performed.
Step S410: and adding the transaction code which is successful in the result of the history execution record in the step S408 to the transaction code white list.
Step S412: whether the transaction code white list already exists or not is determined, in step S408, the history execution record includes a transaction code whose execution result is successful, and if the transaction code white list already exists, step S414 is executed. Otherwise, step S416 is performed.
Step S414: and deleting the transaction code which is judged to be successful in the execution result in the history execution record and exists in the transaction code white list in the step S412 from the transaction code white list, and resetting the transaction code as the transaction code required by the application software to be tested when the target function test is carried out.
Step S416: ending the operation.
The automatic creation process of the identification code white list can be realized through the steps, and the effect of dynamically updating the identification code white list range is achieved.
In an alternative embodiment, fig. 5 is a schematic flow chart (one) of a transaction code verification according to an embodiment of the present invention, as shown in fig. 5, and specifically includes the following steps:
step S502, obtaining transaction codes (corresponding to the first identification codes) corresponding to all functions of the application software to be tested, which need to be subjected to the target function test.
Step S504, judging whether the transaction code is in a transaction code white list.
Step S506, judging the execution result of the transaction code.
In an alternative embodiment, the transaction code verification process may be specifically described with reference to fig. 6, where fig. 6 is a schematic flow chart (two) of a transaction code verification according to an embodiment of the present invention, and the steps shown in fig. 6 are specifically as follows:
step S602: the transaction code verification process begins.
Step S604: and acquiring transaction codes corresponding to all functions of the application software to be tested, which need to be subjected to target function test.
Step S606: whether the transaction code in step S604 is in the transaction code white list or not is determined, and if the transaction code is not in the transaction code white list, step S608 is executed. Otherwise, step S612 is performed.
Step S608: and acquiring an actual test execution result of the transaction codes which are not in the transaction code monitoring white list and are judged in the step S606 in the test process from the transaction code monitoring platform.
Step S610: if the status of the transaction code execution result is successful, step S612 is executed. If the transaction code execution result is failure or not tested, step S614 is performed.
Step S612: and setting the execution result of the transaction code as successful.
Step S614: and setting the transaction code check result as failure.
Step S616: and ending the transaction code checking flow.
The method can realize the effect of automatically judging the execution result of the identification code based on the identification code white list, does not need manual monitoring and intervention on the execution result of the transaction code, and improves the determination efficiency of the test result.
From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of the various embodiments of the present invention.
The embodiment also provides a device for determining a test result, which is used for implementing the above embodiment and the preferred implementation, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware, are also possible and contemplated.
Fig. 7 is a block diagram of a test result determining apparatus according to an embodiment of the present invention, the apparatus including:
a target function test module 72, configured to perform a target function test on the application software to be tested in response to a test instruction of the target object;
an execution result determining module 74, configured to determine an execution result of the identification code when the application software to be tested performs the target function test;
and the test result determining module 76 is configured to determine a test result of the application software to be tested based on the identifier code white list, if the execution result is determined to be the execution failure.
By the aid of the device for determining the test result, after the test instruction of the target object is responded, the target function test can be conducted on the application software to be tested, the identification code execution result when the application software to be tested conducts the target function test is further obtained, and the identification code white list is used for determining that the execution result is the test result of the application software to be tested, which fails to be executed. The problem of how to improve the determination efficiency of the test result is solved in the related art, and the effect of improving the function test efficiency can be realized.
Optionally, the target function test includes a transaction function test, and the transaction function includes: the online transaction and batch transaction are that user requests are received and processed in real time, transaction data are required to be updated in real time after the processing is completed, and processing results are sent to users; batch transactions refer to the centralized processing of a batch of transaction data, e.g., batch settlement of various transactions by a user at the end of each day, followed by updating of the transaction data.
Alternatively, the identification code may include a transaction code of an online transaction, i.e., a serial number of the online transaction.
Optionally, the identification code whitelist is automatically created by a program, and the whitelist is dynamically changed.
Optionally, the execution result determining module 74 is further configured to determine a first identifier required when the application software to be tested performs the target function test; acquiring a second identification code monitored when the application software to be tested performs target function test; if the second identification code is determined to be consistent with the first identification code, if the execution result of the second identification code is failure, determining that the execution result of the identification code when the application software to be tested performs the target function test is failure; and if the execution result of the second identification code is successful, determining that the execution result of the identification code when the application software to be tested performs the target function test is successful.
Optionally, the execution result determining module 74 is further configured to determine, from the test instruction, a target transaction type indicated by the target object; acquiring a target identification code database matched with the target transaction type from a preset identification code database; the preset identification code database is stored with a plurality of sub-databases, and each sub-database of the plurality of sub-databases is used for storing identification codes of different transaction types; and determining the identification code in the target identification code database as a first identification code required by the application software to be tested when the target function test is carried out.
Optionally, the transaction type may include a transaction function applied offline, such as code-scanning payment, card-swiping payment, etc., and the transaction type may also include a transaction function applied online, such as internet banking payment, third party platform payment, etc., which is not limited in this embodiment.
Optionally, the test result determining module 76 is further configured to determine a first identifier required when the application software to be tested performs the target function test; acquiring a second identification code monitored when the application software to be tested performs target function test; under the condition that the second identification code is inconsistent with the first identification code, an initial identification code white list is obtained, and the initial identification code white list is updated based on the first identification code to obtain the identification code white list; and under the condition that the second identification code is consistent with the first identification code, acquiring an initial identification code white list, and updating the initial identification code white list by using the second identification code with the execution result of failure to acquire the identification code white list.
Alternatively, in the case that the second identifier is inconsistent with the first identifier, it may be understood that the application software to be tested does not monitor the first identifier but monitors the second identifier when performing the target function test. At this time, updating the initial identification code whitelist may be achieved by adding the second identification code to the initial identification code whitelist.
Optionally, in the case that the second identifier is inconsistent with the first identifier, it may also be understood that the second identifier monitored when the application software to be tested performs the target function test is not the first identifier required when the application software to be tested performs the target function test, and at this time, the execution result of the second identifier is manually confirmed.
Optionally, for the case that the second identifier is determined to be consistent with the first identifier, it may be understood that the second identifier monitored when the application software to be tested performs the target function test is the first identifier required when the application software to be tested performs the target function test. At this time, if the execution result of the second identification code is monitored to be the execution failure, the initial identification code white list is updated by using the second identification code with the execution failure, and the identification code white list is obtained.
Alternatively, the identification code whitelist may be generated by: if the identification codes which do not belong to the history execution record are monitored in the test process, adding the identification codes which do not belong to the history execution record to an initial identification code white list to generate an identification code white list; if the identification code with the execution result of failure is present in the test process, the identification code with the execution result of failure is added to the initial identification code white list to generate the identification code white list.
Optionally, the test result determining module 76 is further configured to initialize the identifier whitelist by: and automatically adding the identification code to the identification code white list when the identification code execution result at the time of target function test in the test environment does not exist as the successful execution within the last year.
Optionally, for the case that the execution result of the identifier code is an execution failure, in addition to directly monitoring that the execution result of the identifier code is an execution failure, the method may further include: the execution result of the identification code is not monitored, or the execution record of the identification code is not monitored; the reason why the execution record of the identification code is not monitored is that the execution record is not monitored due to the fact that the execution record cannot be normally tested when the execution record is tested by a third party.
Optionally, the reasons for the failure of the execution of the identification code, such as the non-unique return status value, may not enable the configuration of the monitoring rule.
Optionally, the test result determining module 76 is further configured to update the identifier whitelist by: and adding the identification code which is not in the range of the identification code white list to the identification code white list under the condition that the execution result of the identification code cannot be detected in the test process.
Optionally, the above-mentioned test result determining module 76 is further configured to determine all identification codes corresponding to the application software to be tested from the historical test record of the application software to be tested; wherein, each identification code of all the identification codes corresponds to a test result; determining the identification code with the failed test result from all the identification codes, and generating the identification code white list by using the identification code with the failed test result; wherein, the identification codes in the identification code white list at least comprise: the identification codes that have been executed and failed to be executed, and the identification codes that have not been executed.
Optionally, the test result determining module 76 is further configured to obtain a third identifier with a successful execution result from the monitored identifier of the application software to be tested; deleting the third identification code from the identification code whitelist if it is determined that the third identification code exists in the identification code whitelist; and setting the third identification code as an identification code required by the application software to be tested when the target function test is performed.
Optionally, the test result determining module 76 is further configured to determine that the execution result is a fourth identification code that fails to execute; for a plurality of fourth identification codes, acquiring default execution results set for the fourth identification codes from the identification code white list under the condition that the fourth identification codes are determined to exist in the identification code white list; wherein the default execution result comprises an execution result of successful execution; and determining the default execution result as the execution result of the plurality of fourth identification codes, and determining the test result of the application software to be tested as the test success.
Alternatively, in the present embodiment, the above-described storage medium may be configured to store a computer program for performing the steps of:
s1, responding to a test instruction of a target object, and performing target function test on application software to be tested;
s2, determining an execution result of the identification code when the application software to be tested performs the target function test;
and S3, determining the test result of the application software to be tested based on the identification code white list under the condition that the execution result is determined to be the execution failure.
In one exemplary embodiment, the computer readable storage medium may include, but is not limited to: a usb disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing a computer program.
Specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the exemplary implementation, and this embodiment is not described herein.
An embodiment of the invention also provides an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.
Alternatively, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:
s1, responding to a test instruction of a target object, and performing target function test on application software to be tested;
s2, determining an execution result of the identification code when the application software to be tested performs the target function test;
and S3, determining the test result of the application software to be tested based on the identification code white list under the condition that the execution result is determined to be the execution failure.
In an exemplary embodiment, the electronic apparatus may further include a transmission device connected to the processor, and an input/output device connected to the processor.
Specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the exemplary implementation, and this embodiment is not described herein.
It will be appreciated by those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method of determining a test result, comprising:
Responding to a test instruction of a target object, and performing target function test on the application software to be tested;
determining an execution result of the identification code when the application software to be tested performs the target function test;
and under the condition that the execution result is determined to be the execution failure, determining the test result of the application software to be tested based on the identification code white list.
2. The method for determining a test result according to claim 1, wherein determining an execution result of an identification code when the application software to be tested performs the target function test includes:
determining a first identification code required by the application software to be tested when performing target function test; acquiring a second identification code monitored when the application software to be tested performs target function test;
if the second identification code is determined to be consistent with the first identification code, if the execution result of the second identification code is failure, determining that the execution result of the identification code when the application software to be tested performs the target function test is failure; and if the execution result of the second identification code is successful, determining that the execution result of the identification code when the application software to be tested performs the target function test is successful.
3. The method for determining a test result according to claim 2, wherein determining the first identification code required for the application software to be tested to perform the target function test includes:
determining a target transaction type indicated by the target object from the test instruction;
acquiring a target identification code database matched with the target transaction type from a preset identification code database; the preset identification code database is stored with a plurality of sub-databases, and each sub-database of the plurality of sub-databases is used for storing identification codes of different transaction types;
and determining the identification code in the target identification code database as a first identification code required by the application software to be tested when the target function test is carried out.
4. The method of claim 1, wherein the identification code whitelist is determined by one of:
determining a first identification code required by the application software to be tested when performing target function test; acquiring a second identification code monitored when the application software to be tested performs target function test;
under the condition that the second identification code is inconsistent with the first identification code, an initial identification code white list is obtained, and the initial identification code white list is updated based on the first identification code to obtain the identification code white list;
And under the condition that the second identification code is consistent with the first identification code, acquiring an initial identification code white list, and updating the initial identification code white list by using the second identification code with the execution result of failure to acquire the identification code white list.
5. The method for determining test results according to claim 1, wherein before determining the test results of the application software under test based on the generated whitelist of identification codes, the method further comprises:
determining all identification codes corresponding to the application software to be tested from the history test record of the application software to be tested; wherein, each identification code of all the identification codes corresponds to a test result;
determining the identification code with the failed test result from all the identification codes, and generating the identification code white list by using the identification code with the failed test result;
wherein, the identification codes in the identification code white list at least comprise: the identification codes that have been executed and failed to be executed, and the identification codes that have not been executed.
6. The method of claim 5, further comprising, after generating the whitelist of identification codes for failed identification codes using the test result: acquiring a third identification code with an execution result of successful execution from the monitored identification code of the application software to be tested;
Deleting the third identification code from the identification code whitelist if it is determined that the third identification code exists in the identification code whitelist;
and setting the third identification code as an identification code required by the application software to be tested when the target function test is performed.
7. The method for determining a test result according to claim 1, wherein determining the test result of the application software to be tested based on an identification code white list comprises:
determining the execution result as a fourth identification code of execution failure;
for a plurality of fourth identification codes, acquiring default execution results set for the fourth identification codes from the identification code white list under the condition that the fourth identification codes are determined to exist in the identification code white list; wherein the default execution result comprises an execution result of successful execution;
and determining the default execution result as the execution result of the plurality of fourth identification codes, and determining the test result of the application software to be tested as the test success.
8. A test result determining apparatus, comprising:
the target function test module is used for responding to the test instruction of the target object and carrying out target function test on the application software to be tested;
The execution result determining module is used for determining the execution result of the identification code when the application software to be tested performs the target function test;
and the test result determining module is used for determining the test result of the application software to be tested based on the identification code white list under the condition that the execution result is determined to be the execution failure.
9. A computer readable storage medium, characterized in that the computer readable storage medium comprises a stored program, wherein the program when run performs the method of any of the preceding claims 1 to 7.
10. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of the claims 1 to 7 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311119092.0A CN117407280A (en) | 2023-08-31 | 2023-08-31 | Determination method and device of test result, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311119092.0A CN117407280A (en) | 2023-08-31 | 2023-08-31 | Determination method and device of test result, storage medium and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117407280A true CN117407280A (en) | 2024-01-16 |
Family
ID=89489771
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311119092.0A Pending CN117407280A (en) | 2023-08-31 | 2023-08-31 | Determination method and device of test result, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117407280A (en) |
-
2023
- 2023-08-31 CN CN202311119092.0A patent/CN117407280A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109474578B (en) | Message checking method, device, computer equipment and storage medium | |
| CN115190035B (en) | System, method, apparatus, and medium for providing mobile device support services | |
| CN109787858B (en) | Method and terminal for issuing services in batches | |
| CN110134576B (en) | Batch log query method, terminal and computer readable storage medium | |
| CN108234549B (en) | Policy information checking method and device | |
| CN112433944A (en) | Service testing method, device, computer equipment and storage medium | |
| CN113312064A (en) | Installation configuration method and device of physical machine and computer readable medium | |
| CN105704241A (en) | Client terminal program updating method and system and a service platform | |
| CN112817867A (en) | Interface test script generation method and device, computer equipment and medium | |
| CN111371645B (en) | Method, system, computer equipment and storage medium for testing service connectivity | |
| CN114626683A (en) | Product update message notification method and device based on RPA and AI and electronic equipment | |
| CN111177121A (en) | Order data feedback method and device, computer equipment and storage medium | |
| CN110297749B (en) | Method and terminal for testing new function | |
| CN109104297B (en) | Business process processing method and device | |
| CN117407280A (en) | Determination method and device of test result, storage medium and electronic device | |
| CN113301557B (en) | eSIM card state management method, device, equipment and storage medium | |
| CN111597093A (en) | Exception handling method, device and equipment | |
| CN114546842A (en) | Interface test method and device, storage medium and electronic equipment | |
| CN110704301B (en) | TPC-E automatic test method and TPC-E test system | |
| CN113672521A (en) | Program testing method and device and electronic equipment | |
| CN109240906B (en) | Database configuration information adaptation method and device, computer equipment and storage medium | |
| CN110177077B (en) | Account system offline processing method, device, equipment and storage medium | |
| CN109993406B (en) | Information processing method and device | |
| CN117313856B (en) | Reliability test planning system and method | |
| CN111708789B (en) | Method, apparatus, computer device and medium for updating external platform store information |
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 |