CN114996141A - Software testing method, device, equipment and storage medium - Google Patents
Software testing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114996141A CN114996141A CN202210662742.5A CN202210662742A CN114996141A CN 114996141 A CN114996141 A CN 114996141A CN 202210662742 A CN202210662742 A CN 202210662742A CN 114996141 A CN114996141 A CN 114996141A
- Authority
- CN
- China
- Prior art keywords
- test
- parameter value
- parameter
- software
- target financial
- 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
Images
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/3604—Software analysis for verifying properties of programs
- G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
-
- 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/3604—Software analysis for verifying properties of programs
- G06F11/3616—Software analysis for verifying properties of programs using software metrics
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
Abstract
The application discloses a software testing method, a device, equipment and a storage medium, relates to the technical field of finance, and aims to solve the problem that a testing conclusion obtained after financial software passes the existing non-functional test is poor in reliability. The specific scheme is as follows: acquiring at least one test parameter of the target financial software; searching a first static parameter value corresponding to each test parameter under the condition that the target financial software is in an online running state; searching a second static parameter value corresponding to each test parameter under the condition that the target financial software is in a test state; and generating a test report according to the comparison result of the first static parameter value and the second static parameter value. The method and the device are used for the process of testing the financial software.
Description
Technical Field
The present application relates to the field of financial technologies, and in particular, to a software testing method, apparatus, device, and storage medium.
Background
With the development of internet technology, more and more financial software is developed to meet the convenience demand of users for processing financial services by electronic equipment. Before financial software is used online, non-functional tests are required for performance pressure, reliability, availability, maintainability, and extensibility.
However, after the financial software passes the above non-functional test, there may be a case where the financial software cannot be operated or an operation error occurs in actual use, that is, the reliability of the obtained test conclusion is poor.
Disclosure of Invention
The application provides a software testing method, a device, equipment and a storage medium, which are used for solving the problem that a testing conclusion obtained after financial software passes the existing non-functional test is poor in reliability.
In order to achieve the purpose, the technical scheme is as follows:
in a first aspect, the present application provides a software testing method, including: acquiring at least one test parameter of the target financial software; searching a first static parameter value corresponding to each test parameter under the condition that the target financial software is in an online running state; searching a second static parameter value corresponding to each test parameter under the condition that the target financial software is in a test state; and generating a test report according to the comparison result of the first static parameter value and the second static parameter value.
According to the software testing method, firstly, at least one testing parameter of the target financial software is obtained, whether the target financial software normally operates or not can be reflected by a static value corresponding to the testing parameter, secondly, a first static parameter value corresponding to the testing parameter in the target financial software in an online operation state and a second static parameter value corresponding to the testing parameter in the target financial software in a testing state are respectively searched, and finally, whether the first static parameter value is consistent with the second static parameter value or not is compared, and a testing report is generated according to a comparison result. That is, whether the first static parameter and the second static parameter are consistent or not is compared, and whether the target financial software can normally run or not is judged. Therefore, the comparison result is used as a part of conclusion of the software test of the target financial software, so that the reliability of the test conclusion can be improved, and the stability of the target financial software is further improved.
Optionally, the obtaining at least one test parameter of the target financial software includes: and in the test parameter database, acquiring at least one test parameter according to the software attribute of the target financial software, wherein the at least one test parameter comprises an operation environment parameter, a database environment parameter and a user data parameter.
As can be seen from the above, in the software testing method provided by the present application, the software attribute may be any of the following: the system comprises a core transaction system, a connection transaction system, a financial transaction system, a bank core system, an individualized financial system, a customer analysis system, an internal management system and a credit card system, so that at least one test parameter corresponding to software attributes is searched, the test parameter can cover parameters of a bottom operating system, parameters of an upper application framework, parameters of a middleware, parameters of a front-end system, parameters of a background service and parameters of database performance, and the reliability of a test conclusion is improved through comprehensive coverage of the test parameters.
Optionally, the searching for the first static parameter value corresponding to each test parameter under the condition that the target financial software is in the online running state includes: crawling a first static parameter value corresponding to each online test parameter in a program file of the target financial software in an online running state in a crawler mode; or/and generating a first parameter value acquisition request, wherein the first parameter value request is used for requesting to acquire a first static parameter value corresponding to each test parameter; and according to the first parameter acquisition request, acquiring a first static parameter value corresponding to each test parameter from a data monitoring database corresponding to the target financial software in an online running state.
Therefore, the software testing method provided by the application can directly crawl the first static parameter value from the program file of the target financial software in a crawler mode, and can also obtain the first static parameter value from the data monitoring database by responding to the first parameter value obtaining request, and theoretically, the first static parameter value obtained in the two modes should be the same. The first static parameter value is crawled in a crawler mode, and the accuracy of the first static parameter value can be ensured. Under the condition that the crawler does not crawl the first static parameter value corresponding to each test parameter, the first static parameter value can be searched through the stored data in the data monitoring database, and therefore the first static parameter value can be obtained. Certainly, under the condition that the first static parameter value corresponding to each test parameter is not stored in the data monitoring database, the first static parameter value can be obtained by supplementing in a crawler crawling manner.
Optionally, the searching for the second static parameter value corresponding to each test parameter under the condition that the target financial software is in the test state includes: crawling a second static parameter value corresponding to each test parameter in a program file of the target financial software in a test state in a crawler mode; or/and generating a second parameter value acquisition request, wherein the second parameter value request is used for requesting to acquire a second static parameter value corresponding to each test parameter; and according to the second parameter acquisition request, acquiring a second static parameter value corresponding to each test parameter from the running state database corresponding to the target financial software in the test state.
As can be seen from the above, the software testing method provided by the application may directly crawl the second static parameter value from the program file of the target financial software in a crawler manner, and may also obtain the second static parameter value from the data monitoring database in response to the second parameter obtaining request, where theoretically, the second static parameter value obtained in the two manners should be the same. The second static parameter value is crawled in a crawler mode, and the accuracy of the second static parameter value can be improved. Under the condition that the crawler does not crawl the second static parameter value corresponding to each test parameter, the second static parameter value can be searched through the stored data in the data monitoring database, and therefore the second static parameter value can be obtained. Certainly, under the condition that the data monitoring database does not store the second static parameter value corresponding to each test parameter, the second static parameter value can be obtained by supplementing in a crawler crawling manner.
Optionally, after the test report is generated according to the comparison result of the first static parameter value and the second static parameter value, the warning information is generated when the comparison result is an abnormal result.
According to the software testing method, the warning information is generated under the condition that the comparison result is an abnormal result, the butt joint party involved in the testing, running and maintaining processes of the target financial software is prompted through the warning information, the testing parameters of the target financial software can be formally operated online only by resetting, the target financial software is operated online from research and development to testing and from testing to online, and the two-way channel from online operation to research and development and correction is used for realizing the comparison closed loop of the testing parameters, so that the formal online operation stability of the target financial software is improved.
In a second aspect, the present application provides a software testing apparatus, including an obtaining unit, a first searching unit, a second searching unit, and a generating unit; the acquisition unit is used for acquiring at least one test parameter of the target financial software; the first searching unit is used for searching a first static parameter value corresponding to the test parameter acquired by each acquiring unit under the condition that the target financial software is in an online running state; the second searching unit is used for searching a second static parameter value corresponding to the test parameter acquired by each acquiring unit under the condition that the target financial software is in a test state; and the generating unit is used for generating a test report according to the comparison result of the first static parameter value searched by the first searching unit and the second static parameter value searched by the second searching unit.
Optionally, the obtaining unit is configured to: and in the test parameter database, acquiring at least one test parameter according to the software attribute of the target financial software, wherein the at least one test parameter comprises an operation environment parameter, a database environment parameter and a user data parameter.
Optionally, the first searching unit is specifically configured to: crawling a first static parameter value corresponding to each test parameter in a program file of the target financial software in an online running state in a crawler mode; or/and generating a first parameter value acquisition request, wherein the first parameter value request is used for requesting to acquire a first static parameter value corresponding to each test parameter; and according to the first parameter acquisition request, acquiring a first static parameter value corresponding to each test parameter from a data monitoring database corresponding to the target financial software in an online running state.
Optionally, the second searching unit is specifically configured to: crawling a second static parameter value corresponding to each test parameter in a program file of the target financial software in a test state in a crawler mode; or/and generating a second parameter value acquisition request, wherein the second parameter value request is used for requesting to acquire a second static parameter value corresponding to each test parameter; and acquiring a second static parameter value corresponding to each test parameter from the running state database corresponding to the target financial software in the test state according to the second parameter acquisition request.
Optionally, the apparatus further comprises: and the generating unit is further used for generating alarm information under the condition that the comparison result is an abnormal result after generating the test report according to the comparison result of the first static parameter value and the second static parameter value.
In a third aspect, an electronic device is provided, including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute instructions to implement the software testing method as provided in the first aspect above.
In a fourth aspect, the present application provides a computer-readable storage medium comprising instructions. The instructions, when executed on the computer, cause the computer to perform the software testing method as provided above in the first aspect.
In a fifth aspect, the present application provides a computer program product for causing a computer to perform the software testing method as provided in the first aspect above when the computer program product is run on the computer.
It should be noted that all or part of the above computer instructions may be stored on the first computer readable storage medium. The first computer readable storage medium may be packaged with the processor of the access network terminal device, or may be packaged separately from the processor of the access network terminal device, which is not limited in this application.
For the descriptions of the second, third, fourth and fifth aspects in this application, reference may be made to the detailed description of the first aspect; in addition, for the beneficial effects described in the second aspect, the third aspect, the fourth aspect and the fifth aspect, reference may be made to the beneficial effect analysis of the first aspect, and details are not repeated here.
These and other aspects of the present application will be more readily apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is one of the flow diagrams of a software testing method shown in an exemplary embodiment;
FIG. 2 is a second flowchart illustrating a software testing method according to an exemplary embodiment;
FIG. 3 is a third flowchart illustrating a software testing method according to an exemplary embodiment;
FIG. 4 is a fourth flowchart illustrating a software testing method in accordance with an exemplary embodiment;
FIG. 5 is a fifth flowchart illustrating a method of testing software in accordance with an exemplary embodiment;
FIG. 6 is a sixth flowchart illustrating a method of testing software in accordance with an exemplary embodiment;
FIG. 7 is a seventh flowchart illustration of a software testing method, in accordance with an exemplary embodiment;
FIG. 8 is a schematic diagram of a software testing apparatus according to an exemplary embodiment;
FIG. 9 is a schematic diagram illustrating a configuration of a computer device in accordance with an illustrative embodiment;
FIG. 10 is a block diagram of a computer program product illustrating a software testing method in accordance with an exemplary embodiment.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.
It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present relevant concepts in a concrete fashion.
For the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, the terms "first" and "second" are used to distinguish the same items or similar items with basically the same functions and actions, and those skilled in the art can understand that the terms "first" and "second" are not limited in number or execution order.
The software testing technology is an important component in the software development process, mainly comprises functional testing and non-functional testing, and is an active process for verifying and confirming a software program (including a staged program) through the whole software development life cycle, and aims to find various problems (such as the problems of inconsistency with user requirements, predefined inconsistency and the like) existing in the software program as soon as possible. And checking the fault of the software program, generating a test report, and delivering the test report to a developer to modify the software program. Software, software products, and software programs refer to a collection of computer data and instructions organized in a particular order.
It should be noted that the functional test is to verify each function of the software program, and according to the software characteristics, the operation description and the user scheme, test the characteristics and the operable behavior of the software program item by item through the functional test case to determine to meet the design requirements. The function test is also called black box test or data drive test, and only needs to consider each function to be tested and does not need to consider the internal structure and codes of the whole software. Generally, a test case is compiled according to requirements from an interface and a framework of a software program, and input data is evaluated between an expected result and an actual result to judge whether the software program meets the use requirements of a user.
It should also be noted that non-functional testing is a test for checking non-functional aspects of a software program, intended to test the readiness of the system according to non-functional parameters that the functional test never addresses. The software performance of the main test of the non-functional test comprises reliability, availability, maintainability and portability. Reliability is a measure of how software maintains its functionality in both mainstream and unexpected situations, and sometimes also includes self-recovery capability in the event of software errors. For example, the function of automatically saving the active file may automatically save the active file according to a preset time interval under a mainstream situation, and may immediately save the active file at the current time under an unexpected situation (e.g., power failure, system crash, etc.), i.e., classify the function of automatically and timely saving the active file into reliability. The usability metric is the ease with which a user learns and controls the software to meet the user's needs. Maintainability describes the amount of work required to modify software without introducing new errors. Portability refers to the ability of software on one computer to transpose to another computer.
No matter the functional test or the non-functional test, the actual operating environment of the software program during online operation is not covered, and the situation that the software program cannot operate or operates wrongly still occurs under the condition that a test conclusion which is qualified through the conventional functional test and the non-functional test is possibly obtained, namely, the reliability of the test conclusion obtained through the existing test method is poor.
Based on this, the embodiment of the application provides a software testing method. The method respectively searches a first static parameter value and a second static parameter value corresponding to a test parameter in consideration of whether a software program is in an online running state or a test state, and generates a test report according to a comparison result of the first static parameter value and the second static parameter value. Compared with the prior art, the method has higher reliability in obtaining the test conclusion in the test report.
The execution main body of the software testing method provided by the application can be an electronic device with data processing capability, such as a computer and a server. The server may be a single server, or may be a server cluster including a plurality of servers. In some embodiments, the server cluster may also be a distributed cluster. The application does not limit the execution subject of the software testing method.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application and using a software testing device as an execution main body, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
FIG. 1 is a flow diagram illustrating a method of testing software in accordance with an exemplary embodiment. As shown in fig. 1, the software testing method provided in the embodiment of the present application includes steps 101 to 104.
In the embodiment of the present application, the target financial software refers to a software program related to financial transactions, financial information management, or financial practitioner management, and the target financial software relates to personal asset-related information, and therefore, is required to have high reliability. Before the target financial software is formally operated on line, the reliability of the target financial software is improved through a more rigorous software test. The target financial software with high reliability is beneficial to improving the trust of the target financial software for the user, improving the viscosity of the user to the target financial software and increasing the number of the users of the target financial software at the user side.
In the embodiment of the application, the test parameters are mainly related to the performance of the application system, and in a longitudinal view, the test parameters include parameters of a bottom operating system, parameters of an upper application framework, parameters of a middleware and the like; from a horizontal perspective, the parameters suitable for the front-end system and the performance parameters related to the background service and different types of databases are included.
It will be appreciated that the test parameters are related to software attributes of the target financial software and that the test parameters that may be obtained for different target financial software are not identical.
Optionally, as shown in fig. 2, the step 101 may be specifically implemented by the following step 201.
In an embodiment of the present application, the at least one test parameter includes an operating environment parameter, a database environment parameter, and a user data parameter. For example, the operating environment parameter may be a windows-related parameter, a UNIX-related parameter, a Linux-related parameter, or a middleware-related parameter, and may specifically be a system version, a memory size, an interrupt frequency, or the like. The database environment parameter may be an Oracle related parameter or a MySQL related parameter, and specifically may be a database type, a size of a reserved storage space of the database, a mapping relationship between the databases, and the like. The user data parameter may be account related data, log related data or preference related data, and specifically may be a maximum parallel user number, a user data desensitization ratio parameter, a user associated account number limitation parameter, or the like.
In the embodiment of the application, the test parameter database is used for storing the test parameters related to the software test, and the database can be dynamically adjusted in an automatic or manual mode to adaptively increase or decrease the stored test parameters. The basis of dynamic adjustment may be updating of a programming language, updating of a test system, and increasing of development software, which is not limited in the embodiment of the present application.
In the embodiment of the present application, the software attribute is used to indicate a data object, a data size, or a user object related to the target financial software, and the data object may be, for example, ATM-type information data, futures information data, stock information data, deposit information data, employee management data, or the like, and the user object may be a deposit user, a financing user, an enterprise user, an internal employee user, or the like. Thus, the software properties may be any according to the data object: core transaction attributes, connection transaction attributes, financial transaction attributes, bank core attributes, personalized financial attributes, customer analysis attributes, internal management attributes, and credit card attributes.
The technical scheme provided by the embodiment at least has the following beneficial effects: at least one test parameter corresponding to the software attribute is searched, so that the test parameter can cover the bottom operating system parameter, the upper application frame parameter, the middleware parameter, the front-end system parameter, the background service parameter and the database performance parameter, and the reliability of a test conclusion is improved through the comprehensive coverage of the test parameter.
102, searching a first static parameter value corresponding to each test parameter by the software testing device under the condition that the target financial software is in an online running state.
In the embodiment of the application, the online running state refers to a simulated actual running state of the target financial software, that is, random data which may be input by a user during the actual online running is simulated, and the random data may be any data so as to be close to the actual running state of the target financial software. When the target financial software is in an online running state, the target financial software is running or in a temporary closing state after the target financial software is running online.
In this embodiment, the first static parameter value refers to a parameter value corresponding to a test parameter in the target financial software in a continuous operation state of the target financial software.
Optionally, in this embodiment of the present application, as shown in fig. 3, the step 102 may be implemented by the following step 301, or/and, as shown in fig. 4, by the following step 401 and step 402.
In the embodiment of the present application, a crawler is a program for acquiring specific content. And updating the crawling parameters of the crawler program by taking the test parameters as crawling basis, the first static parameter values as crawling targets and the program files of the target financial software in the online running state as crawling ranges, and crawling the first static parameter values.
It should be noted that the program file of the target financial software in the online running state refers to the program file after the online running, and is not an initial file for implementing the target financial software, so that the acquired first static parameter value can reflect the running state of the target financial software.
In this embodiment of the application, the first parameter obtaining request is used to request to obtain a first static parameter value corresponding to each test parameter.
In the embodiment of the application, during the running process of the target financial software, a real-time monitoring program may exist, and the real-time monitoring program acquires the running data of the target financial software, and the running data is stored in the data monitoring database. Therefore, the software testing device can also directly acquire the first static parameter value from the data monitoring database.
In this embodiment of the application, the software testing apparatus may select any one of the manners to obtain the first static parameter value, and may also combine the two manners to obtain the first static parameter value.
In one example, the test parameters are divided into two groups, a first static parameter value is obtained from the first group of test parameters in a crawler mode, and a first static parameter value is obtained from the second group of test parameters in a data monitoring database.
In another example, first static parameter values are obtained through a crawler mode, whether the first static parameter values corresponding to all the test parameters are obtained or not is judged, and if not, the first static parameter values of other test parameters are obtained through the data monitoring database.
In another example, first static parameter values are obtained through the data monitoring database, whether the first static parameter values corresponding to all the test parameters are obtained or not is judged, and if not, the first static parameter values of other test parameters are obtained through a crawler mode.
The technical scheme provided by the embodiment at least has the following beneficial effects: the first static parameter value can be directly crawled from the program file of the target financial software in a crawler mode, and can also be obtained from the data monitoring database in response to a first parameter value obtaining request, and theoretically, the first static parameter value obtained in the two modes should be the same. The first static parameter value is crawled through a crawler mode, the accuracy of the first static parameter value can be guaranteed, under the condition that the first static parameter value corresponding to each test parameter is not crawled through the crawler crawling mode, the first static parameter value can be searched through stored data in a data monitoring database, and therefore the first static parameter value can be obtained. Certainly, under the condition that the data monitoring database does not store the first static parameter value corresponding to each test parameter, the first static parameter value can be obtained by supplementing in a crawler crawling manner.
And 103, searching a second static parameter value corresponding to each test parameter by the software testing device under the condition that the target financial software is in a testing state.
In the embodiment of the present application, the test state refers to a state in a test process of simulating the target financial software, and specifically refers to a state in which the target financial software is being tested or a temporary shutdown state in which the target financial software is being tested, when the target financial software is in the test state, that is, a program file corresponding to the target financial software is not restored to an initial value.
In this embodiment, the second static parameter value is similar to the first static parameter value, and the second static parameter value refers to a parameter value corresponding to a test parameter in the target financial software in a test state of the target financial software.
Optionally, in this embodiment of the present application, as shown in fig. 5, the step 103 may be implemented by the following step 501, or/and, as shown in fig. 6, implemented by the following step 601 and step 602.
And 501, the software testing device crawls a second static parameter value corresponding to each testing parameter in a program file of the target financial software in a testing state in a crawler mode.
In the embodiment of the present application, a crawler is a program for acquiring specific content. And updating the crawling parameters of the crawler program by taking the test parameters as a crawling basis, the second static parameter values as a crawling target and the program files of the target financial software as a crawling range, and crawling the second static parameter values.
It should be noted that the program file of the standard financial software in the visual test state refers to the program file after the test, and is not the initial file for implementing the target financial software, so that the obtained second static parameter value can reflect the test state of the target financial software.
In this embodiment of the application, the second parameter obtaining request is used to request to obtain a second static parameter value corresponding to each test parameter.
In the embodiment of the application, during the testing process of the target financial software, a real-time monitoring program may exist, and the real-time monitoring program acquires the operation data of the target financial software, and the operation data is stored in the operation state database. Therefore, the software testing device can also directly acquire the second static parameter value from the running state database.
In this embodiment of the application, the software testing apparatus may select any one of the manners to obtain the second static parameter value, and may also combine the two manners to obtain the second static parameter value.
In one example, the test parameters are divided into two groups, the first group of test parameters is used for acquiring a second static parameter value in a crawler mode, and the second group of test parameters is used for acquiring the second static parameter value in an operation state database.
In another example, the second static parameter value is obtained in a crawler mode, whether the second static parameter values corresponding to all the test parameters are obtained or not is judged, and if not, the second static parameter values of other test parameters are obtained through the running state database.
In another example, the second static parameter value is obtained through the running state database, whether the second static parameter value corresponding to all the test parameters is obtained or not is judged, and if not, the second static parameter values of other test parameters are obtained through a crawler mode.
The technical scheme provided by the embodiment at least has the following beneficial effects: the second static parameter value may be crawled directly from a program file of the target financial software in a crawler manner, and may also be obtained from the data monitoring database in response to a second parameter obtaining request, where theoretically, the second static parameter value obtained in the foregoing two manners should be the same. The second static parameter value is crawled in a crawler mode, and the accuracy of the second static parameter value can be improved. Under the condition that the crawler does not crawl the second static parameter value corresponding to each test parameter, the second static parameter value can be searched through the stored data in the data monitoring database, and therefore the second static parameter value can be obtained. Certainly, under the condition that the second static parameter value corresponding to each test parameter is not stored in the data monitoring database, the second static parameter value can be obtained by supplementing in a crawler crawling manner.
And 104, generating a test report by the software test device according to the comparison result of the first static parameter value and the second static parameter value.
In the embodiment of the application, the test report is used for recording the test parameters, the first static parameter values and the second static parameter values which are in one-to-one correspondence with the test parameters, and the comparison result.
It is to be understood that the test report may have a particular data format, data arrangement, data attributes (e.g., character color, font size, shading, ground color, bolding, and skewing), and the like.
In this embodiment, the software testing apparatus may further be configured to send the test report to a preset mailbox after the test report is generated, or display the test report in a pop-up window manner.
In the embodiment of the present application, the test report may further include test information such as a test time, a version number of the target financial software, a test type (static test), and the like.
The technical scheme provided by the embodiment at least has the following beneficial effects: the method comprises the steps of firstly obtaining at least one test parameter of target financial software, enabling a static value corresponding to the test parameter to reflect whether the target financial software normally operates, secondly respectively searching a first static parameter value corresponding to the test parameter in the target financial software in an online operating state and a second static parameter value corresponding to the test parameter in the target financial software in the test state, finally comparing whether the first static parameter value and the second static parameter value are consistent, and generating a test report according to a comparison result. That is, whether the first static parameter and the second static parameter are consistent or not is compared, and whether the target financial software can normally run or not is judged. Therefore, the comparison result is used as a part of conclusion of the software test of the target financial software, so that the reliability of the test conclusion can be improved, and the stability of the target financial software is further improved.
Optionally, in this embodiment of the present application, as shown in fig. 7, after the step 104, the software testing method provided in this embodiment of the present application further includes the following step 701.
And 701, generating alarm information by the software testing device under the condition that the comparison result is an abnormal result.
In this embodiment, the abnormal result means that the first static parameter value and the second static parameter value corresponding to the same test parameter are not consistent.
In this embodiment, the warning information may be pop-up window information, mail, and prompt box information, which is not limited in this embodiment.
In this embodiment, the software testing apparatus may send the alarm information to a preset testing dockee, where the preset testing dockee may be a mailbox, a monitoring account, a testing terminal, and the like of a responsible person involved in a process of testing, operating, or maintaining the target financial software.
The technical scheme provided by the embodiment at least has the following beneficial effects: the method comprises the steps of generating alarm information under the condition that a comparison result is an abnormal result, prompting a butt joint party involved in the testing, running and maintaining processes of target financial software through the alarm information, enabling the target financial software to formally run online after test parameters of the target financial software need to be reset, and realizing comparison closed loop of the test parameters from the online running to the research and development of a corrected bidirectional channel from the research and development of the target financial software to the online running from the testing to the online running, so that the formal online running stability of the target financial software is improved.
The method provided by the embodiment of the present application is described in detail above with reference to fig. 1 to 7. In order to implement the above functions, the software testing apparatus includes hardware structures and/or software modules for performing the respective functions, and the hardware structures and/or software modules for performing the respective functions may form an electronic device. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
Hereinafter, the software testing apparatus provided in the embodiment of the present application will be described in detail with reference to fig. 8. It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment, and therefore, for the sake of brevity, details which are not described in detail above may be referred to the method embodiment.
Fig. 8 is a schematic structural diagram of a software testing apparatus according to an exemplary embodiment, which may be used to execute the software testing method shown in fig. 1. As one implementation, the apparatus may include: an acquisition unit 81, a first search unit 82, a second search unit 83, and a generation unit 84;
an acquisition unit 81 for acquiring at least one test parameter of the target financial software; for example, in connection with fig. 1, the obtaining unit 81 may be configured to perform step 101.
The first searching unit 82 is configured to search a first static parameter value corresponding to the test parameter acquired by each acquiring unit 81 when the target financial software is in an online running state; for example, in connection with fig. 1, the first lookup unit 82 may be used to perform step 102.
The second searching unit 83 is configured to search, when the target financial software is in a test state, a second static parameter value corresponding to the test parameter acquired by each acquiring unit 81; for example, in connection with fig. 1, the second lookup unit 83 may be configured to perform step 103.
The generating unit 84 is configured to generate a test report according to a comparison result between the first static parameter value found by the first searching unit 82 and the second static parameter value found by the second searching unit 83. For example, in connection with fig. 1, the generating unit 84 may be configured to perform step 104.
Optionally, the obtaining unit 81 is configured to: and in the test parameter database, acquiring at least one test parameter according to the software attribute of the target financial software, wherein the at least one test parameter comprises an operation environment parameter, a database environment parameter and a user data parameter. For example, in connection with fig. 2, the obtaining unit 81 may be configured to perform step 201.
Optionally, the first searching unit 82 is specifically configured to: crawling a first static parameter value corresponding to each test parameter in a program file of the target financial software in an online running state in a crawler mode; for example, in connection with fig. 3, the first lookup unit 82 may be configured to perform step 301.
Or/and generating a first parameter value acquisition request, wherein the first parameter value request is used for requesting to acquire a first static parameter value corresponding to each test parameter; for example, in connection with fig. 4, the first lookup unit 82 may be configured to perform step 401.
And according to the first parameter acquisition request, acquiring a first static parameter value corresponding to each test parameter from a data monitoring database corresponding to the target financial software in an online running state. For example, in connection with fig. 4, the first lookup unit 82 may be used to perform step 402.
Optionally, the second searching unit 83 is specifically configured to: crawling a second static parameter value corresponding to each test parameter in a program file of the target financial software in a test state in a crawler mode; for example, in connection with fig. 5, the second lookup unit 83 may be configured to perform step 501.
Or/and generating a second parameter value acquisition request, wherein the second parameter value request is used for requesting to acquire a second static parameter value corresponding to each test parameter; for example, in connection with fig. 6, the second lookup unit 83 may be configured to perform step 601.
And according to the second parameter acquisition request, acquiring a second static parameter value corresponding to each test parameter from the running state database corresponding to the target financial software in the test state. For example, in connection with fig. 6, the second lookup unit 83 may be configured to perform step 602.
Optionally, the apparatus further comprises: the generating unit 84 is further configured to generate alarm information when the comparison result is an abnormal result after generating the test report according to the comparison result between the first static parameter value and the second static parameter value. For example, in connection with fig. 7, the generating unit 84 may be configured to perform step 701.
Fig. 9 is a schematic diagram illustrating a hardware configuration of a computer device according to an exemplary embodiment. The computer device may comprise a processor 902, the processor 902 being configured to execute application program code to implement the software testing method in the present application.
The processor 902 may be a Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the teachings of the present disclosure.
As shown in fig. 9, the computer device may also include memory 903. The memory 903 is used for storing application program codes for executing the scheme of the application, and the processor 902 controls the execution.
The memory 903 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disk read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory 903 may be separate and coupled to the processor 902 through a bus 904. The memory 903 may also be integrated with the processor 902.
As shown in fig. 9, the computer device may further comprise a communication interface 901, wherein the communication interface 901, the processor 902, and the memory 903 may be coupled to each other, for example, via a bus 904. The communication interface 901 is used for information interaction with other devices, for example, to support information interaction between the computer device and other devices.
It should be noted that the device configuration shown in fig. 9 does not constitute a limitation of the computer device, and the computer device may include more or less components than those shown in fig. 9, or combine some components, or a different arrangement of components, in addition to the components shown in fig. 9.
The present application also provides a computer-readable storage medium comprising instructions stored thereon, which when executed by a processor of a computer device, enable a computer to perform the block chain based data processing method provided by the above-described illustrative embodiment. For example, the computer-readable storage medium may be the memory 903 comprising instructions executable by the processor 902 of the computer device to perform the above-described method. Alternatively, the computer readable storage medium may be a non-transitory computer readable storage medium, for example, the non-transitory computer readable storage medium may be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Fig. 10 is a schematic diagram illustrating a computer program of a software testing method according to an exemplary embodiment, and the computer program product includes a computer program for executing a computer process on a computing device.
In one embodiment, the computer program product is provided using a signal bearing medium 1007. The signal bearing medium 1007 may include one or more program instructions that, when executed by one or more processors, may provide the functions or portions of the functions described above with respect to fig. 1. Thus, as with the embodiment shown in fig. 1, one or more features of steps 101-104 may be undertaken by one or more instructions associated with the signal bearing medium 1007. Further, the program instructions in FIG. 10 also describe example instructions.
In some examples, the signal bearing medium 1007 may comprise a computer readable medium 1011 such as, but not limited to, a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), a digital tape, a memory, a read-only memory (ROM), a Random Access Memory (RAM), or the like.
In some implementations, the signal bearing medium 1007 may comprise a computer recordable medium 1012 such as, but not limited to, a memory, a read/write (R/W) CD, a R/W DVD, and the like.
In some implementations, the signal bearing medium 1007 may include a communication medium 1013 such as, but not limited to, a digital and/or analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
The signal bearing medium 1007 may be conveyed by a wireless form of communication medium 1013. The one or more program instructions may be, for example, computer-executable instructions or logic-implementing instructions.
In some examples, a software testing apparatus, such as described with respect to fig. 8, may be configured to provide various operations, functions, or actions in response to one or more program instructions through a computer-readable medium 1011, a computer-recordable medium 1012, and/or a communication medium 1013.
Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete the above-described full-classification part or part of the functions.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a module or a unit is only one type of logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another apparatus, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed to a plurality of different places. The purpose of the scheme of the embodiment can be realized by selecting a part of or a whole classification part unit according to actual needs.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented as a software functional unit and sold or used as a separate product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application, or portions thereof that substantially contribute to the prior art, or the whole classification part or portions thereof, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which may be a single chip, a chip, etc.) or a processor (processor) to execute the whole classification part or some steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method for testing software, the method comprising:
acquiring at least one test parameter of the target financial software;
searching a first static parameter value corresponding to each test parameter under the condition that the target financial software is in an online running state;
searching a second static parameter value corresponding to each test parameter under the condition that the target financial software is in a test state;
and generating a test report according to the comparison result of the first static parameter value and the second static parameter value.
2. The method of claim 1, wherein the obtaining at least one test parameter of the target financial software comprises:
and in a test parameter database, acquiring the at least one test parameter according to the software attribute of the target financial software, wherein the at least one test parameter comprises an operation environment parameter, a database environment parameter and a user data parameter.
3. The method according to claim 1, wherein the searching for the first static parameter value corresponding to each of the test parameters when the target financial software is in an online operating state comprises:
crawling a first static parameter value corresponding to each test parameter in a program file of the target financial software in the online running state in a crawler mode; and/or the first and/or second light sources,
generating a first parameter value acquisition request, wherein the first parameter value acquisition request is used for requesting to acquire a first static parameter value corresponding to each test parameter;
and acquiring a first static parameter value corresponding to each test parameter from a data monitoring database corresponding to the target financial software in the online running state according to the first parameter acquisition request.
4. The method of claim 1, wherein the finding a second static parameter value corresponding to each of the test parameters when the target financial software is in a test state comprises:
crawling a second static parameter value corresponding to each test parameter in a program file of the target financial software in the test state in a crawler mode; and/or the first and/or second light sources,
generating a second parameter value acquisition request, wherein the second parameter value request is used for requesting to acquire a second static parameter value corresponding to each test parameter;
and acquiring a second static parameter value corresponding to each test parameter from the running state database corresponding to the target financial software in the test state according to the second parameter acquisition request.
5. The method of claim 1, wherein after generating a test report based on the comparison of the first static parameter value and the second static parameter value, the method further comprises:
and generating alarm information under the condition that the comparison result is an abnormal result.
6. A software testing apparatus, the apparatus comprising: the device comprises an acquisition unit, a first search unit, a second search unit and a generation unit;
the acquisition unit is used for acquiring at least one test parameter of the target financial software;
the first searching unit is used for searching a first static parameter value corresponding to the test parameter acquired by each acquiring unit under the condition that the target financial software is in an online running state;
the second searching unit is used for searching a second static parameter value corresponding to the test parameter acquired by each acquiring unit under the condition that the target financial software is in a test state;
the generating unit is configured to generate a test report according to a comparison result between the first static parameter value found by the first searching unit and the second static parameter value found by the second searching unit.
7. The apparatus of claim 6, wherein the obtaining unit is configured to:
and acquiring the at least one test parameter in a test parameter database according to the software attribute of the target financial software, wherein the at least one test parameter comprises an operating environment parameter, a database environment parameter and a user data parameter.
8. The apparatus according to claim 6, wherein the first lookup unit is specifically configured to:
crawling a first static parameter value corresponding to each test parameter in a program file of the target financial software in the online running state in a crawler mode; and/or the first and/or second light sources,
generating a first parameter value acquisition request, wherein the first parameter value acquisition request is used for requesting to acquire a first static parameter value corresponding to each test parameter;
and acquiring a first static parameter value corresponding to each test parameter from a data monitoring database corresponding to the target financial software in the online running state according to the first parameter acquisition request.
9. An electronic device comprising a memory, a processor, a bus, and a communication interface; the memory is used for storing computer execution instructions, and the processor is connected with the memory through the bus; the processor executes the computer-executable instructions stored by the memory when the electronic device is running to cause the electronic device to perform the software testing method of any of claims 1-5.
10. A computer-readable storage medium comprising computer-executable instructions that, when executed on a computer, cause the computer to perform the software testing method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210662742.5A CN114996141A (en) | 2022-06-13 | 2022-06-13 | Software testing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210662742.5A CN114996141A (en) | 2022-06-13 | 2022-06-13 | Software testing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114996141A true CN114996141A (en) | 2022-09-02 |
Family
ID=83033340
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210662742.5A Pending CN114996141A (en) | 2022-06-13 | 2022-06-13 | Software testing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114996141A (en) |
-
2022
- 2022-06-13 CN CN202210662742.5A patent/CN114996141A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10013439B2 (en) | Automatic generation of instantiation rules to determine quality of data migration | |
| US7757125B2 (en) | Defect resolution methodology and data defects quality/risk metric model extension | |
| US8762777B2 (en) | Supporting detection of failure event | |
| US20100005346A1 (en) | System and method for integrating data quality metrics into enterprise data management processes | |
| US8311794B2 (en) | Testing executable logic | |
| US9092576B2 (en) | Non-intrusive measurement of content quality using dry runs with roll-back | |
| CN108460068A (en) | Method, apparatus, storage medium and the terminal that report imports and exports | |
| CN113837596A (en) | Fault determination method and device, electronic equipment and storage medium | |
| CN113590432A (en) | Database inspection method and device | |
| CN111897696A (en) | Server cluster hard disk state detection method and device, electronic equipment and storage medium | |
| US10664653B2 (en) | Automated structured cloud datatester | |
| CN111949543A (en) | Testing method and device based on distributed platform, electronic equipment and storage medium | |
| CN117056218A (en) | Test management method, platform, medium and equipment | |
| CN116257226A (en) | Data verification method and device, electronic equipment and storage medium | |
| CN114996141A (en) | Software testing method, device, equipment and storage medium | |
| CN115600972A (en) | Method, device, equipment and storage medium for verifying and selling of bad assets | |
| CN115080433A (en) | Testing method and device based on flow playback | |
| CN114693116A (en) | Method and device for detecting code review validity and electronic equipment | |
| CN111914002B (en) | Machine room resource information processing method and device and electronic equipment | |
| CN114996142A (en) | Software testing method, device, equipment and storage medium | |
| Szívós et al. | The role of data authentication and security in the audit of financial statements | |
| CN110008098B (en) | Method and device for evaluating operation condition of nodes in business process | |
| CN113835999A (en) | Workflow-based testing method for distributed heterogeneous processing system | |
| CN112231232A (en) | Method, device and equipment for determining test data model and generating test data | |
| CN112381509A (en) | Management system for major special topic of national science and technology for creating major new drug |
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 |