CN112783773B - Automatic software testing method and device - Google Patents
Automatic software testing method and device Download PDFInfo
- Publication number
- CN112783773B CN112783773B CN202110095607.2A CN202110095607A CN112783773B CN 112783773 B CN112783773 B CN 112783773B CN 202110095607 A CN202110095607 A CN 202110095607A CN 112783773 B CN112783773 B CN 112783773B
- Authority
- CN
- China
- Prior art keywords
- test
- account
- teller
- teller account
- service attribute
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 30
- 238000013522 software testing Methods 0.000 title claims description 8
- 238000012360 testing method Methods 0.000 claims abstract description 507
- 238000013515 script Methods 0.000 claims abstract description 127
- 238000013101 initial test Methods 0.000 claims abstract description 120
- 238000010998 test method Methods 0.000 claims abstract description 14
- 238000003860 storage Methods 0.000 claims description 22
- 230000002159 abnormal effect Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 16
- 238000000605 extraction Methods 0.000 claims description 8
- 238000013473 artificial intelligence Methods 0.000 abstract description 2
- 238000013500 data storage Methods 0.000 description 24
- 238000012423 maintenance Methods 0.000 description 23
- 230000008569 process Effects 0.000 description 17
- 230000006870 function Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 11
- 230000006978 adaptation Effects 0.000 description 5
- 238000007405 data analysis Methods 0.000 description 5
- 239000000284 extract Substances 0.000 description 5
- 230000000737 periodic effect Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000013075 data extraction Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer 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
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- 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 provides a software automatic testing method and device, and belongs to the technical field of artificial intelligence. The software automatic test method comprises the following steps: acquiring an automatic test script in a software automatic test task, and extracting an initial test teller account from the automatic test script; determining a target test teller account according to a matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account; and replacing the initial test teller account in the automatic test script with the target test teller account, and executing the software automatic test task according to the replaced automatic test script. The invention can solve the problem of the conflict of the accounts of the test teller and improve the software test efficiency.
Description
Technical Field
The invention relates to the technical field of artificial intelligence, in particular to a software automatic testing method and device.
Background
In the project software research and development process, in order to better simulate the actual business application scene after the final version is put on line, the requirements on the data quality and the perfection standard required to be used in the function test are very high. When the last round of return test is used for preparing the data of the test environment, the data of the production environment is generally copied and extracted, and the extracted data is desensitized and then restored to the test environment to prepare the test environment. After the test environment is prepared, the test environment is provided for testers to carry out the next version acceptance test. However, because of the limitation of the hardware resources and other conditions of the test environment, the data of the production environment cannot be extracted and recovered in full quantity during the extraction and recovery of the data of the production environment, and the test data can be prepared for acceptance test only by a partial extraction mode.
When the testing environment is built, because a plurality of versions are tested at the same time, a set of relatively independent testing environment can be built for each system version, and testing personnel can test and verify the version functions by using the corresponding testing environment.
As the system construction becomes more and more complex, the systems and functions involved in a complete transaction operation flow process are also more and more, for the test teller account number used by the tester in the test process, the effective test can be developed only when the test data corresponding to all the systems or services involved in the test teller account number transaction operation process are complete, and the corresponding country, region and website information are matched and complete, otherwise, the situation that normal transaction operation cannot be performed due to the loss of part of data can occur.
Meanwhile, in a large-scale application system, the storage of the teller data information is often designed to be that a plurality of information fields are stored in a plurality of different information systems, and only when the information of a certain teller is complete in all data in the plurality of systems and matched with the information, the teller account can perform normal system login and expansion transaction operation, otherwise, login cannot be performed due to the loss of teller information.
In the process of checking and accepting the system by the testers, because the financial industry application system has very strict requirements on the use and authority management of the test teller account number logged in the system, many systems have functions such as user single sign-on control, user login time overlength control, user usable function control and the like, the constraint and the management of user login and accessible information and operable functions are realized through the functions, and when two testers simultaneously use the same test teller account number for testing, one of the testers cannot use the test teller account number for normal testing due to the limitation of the functions such as the single sign-on of the system.
Because the test teller account numbers are associated with the authorities, the sites and the post numbers in most transaction modes, when two test teller accounts meet the same post numbers, belong to the same site and have the same authorities, the test teller accounts can be tested after being replaced with each other, when the problems are solved, a new mode of opening the test teller account numbers is generally adopted, a plurality of test teller data with the same post numbers and authorities are opened in a test environment, and initialization is carried out each time the test environment is prepared.
In this current mode, there are mainly the following problems:
1. in general, the number of test teller accounts corresponding to the test teller accounts in the test environment is relatively complete or the service matching data is relatively complete. Therefore, in the actual test use process, the situation that the same test teller account number is used by a tester often occurs, when two testers use the same test teller account number to test at the same time, the login operation of the test teller account number generates conflict due to the limitation of functions such as single sign-on of a tested system, and when a first tester is in the test, a second tester cannot test; or after the second tester logs in by using the test teller account, the first tester is signed back, so that the overall test efficiency is affected.
2. When the automatic test mode is used, because the automation can submit a plurality of scripts for execution at the same time in batches, the problem of conflict in using the test teller account is more obvious, and the scripts using the same test teller account in the same time period can only be successfully executed, and other scripts can fail because of the problem of conflict in logging in the teller account, so that the test efficiency of the automatic test is greatly affected.
3. In a test organization where a newly opened test teller account number and a test staff reach hundreds of people, with multi-period version iteration, although available test-dedicated teller accounts are increased, due to reasons of variation of test staff, adjustment of test business cross-part rooms, asynchronous maintenance information of the test-dedicated teller accounts in different test environments and the like, after multi-period version test, hot test-dedicated teller accounts with high use frequency and cold test-dedicated teller accounts with little use can appear, and although the mode of manually adjusting the test teller accounts is used for adjusting the stored test teller accounts, due to the fact that data preparation and synchronization among a plurality of systems are involved, users are required to change business means and link the systems, the operation flow is complicated, the time consumption is long, and the effect of manual adjustment is not ideal.
4. Because the hot test teller account data is used for each stage of version test, the matched test data in the test environment is generally complete; the account number data of the cold door test teller cannot be tested when the version data is not recovered perfectly or a problem occurs because few people are used, and after the situation is met, a tester usually tries to replace the account number data of the cold door test teller to other better test teller accounts. After a period of use, the testers often prefer to use the hot special teller account in the test process, and the situation that the use conflict occurs due to the fact that the test teller account is shared by multiple people can occur.
5. In the automatic testing process of the financial industry, due to long transaction flow, high data quality requirement and limitation on hardware, data and other resources, testers generally perform manual testing and automatic testing in the same set of environment. The test teller account number data used in the automatic test script is also often a test teller account number used when a business person performs manual test, so that the problem of login conflict of the test teller account number can also influence the current manual test when the automatic script is submitted for execution.
Because of the problems, when different testers exist in the same environment or a common test teller account exists between manual test and automatic test, the test teller account conflicts are caused, so that transaction test operation is further failed, and the work efficiency of software version function test verification is greatly affected.
Disclosure of Invention
The embodiment of the invention mainly aims to provide a software automatic testing method and device, so as to solve the problem of conflict of test teller accounts and improve software testing efficiency.
In order to achieve the above object, an embodiment of the present invention provides a software automated testing method, including:
Acquiring an automatic test script in a software automatic test task, and extracting an initial test teller account from the automatic test script;
determining a target test teller account according to a matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account;
and replacing the initial test teller account in the automatic test script with the target test teller account, and executing the software automatic test task according to the replaced automatic test script.
The embodiment of the invention also provides a software automatic testing device, which comprises:
the initial test teller account extraction module is used for acquiring an automatic test script in the software automatic test task and extracting an initial test teller account from the automatic test script;
the target test teller account number determining module is used for determining a target test teller account number according to a matching result of the account number business attribute of the initial test teller account number and the account number business attribute of the idle test teller account number;
and the test teller account replacement module is used for replacing the initial test teller account in the automatic test script with the target test teller account, and executing the software automatic test task according to the replaced automatic test script.
The embodiment of the invention also provides computer equipment, which comprises a memory, a processor and a computer program stored on the memory and running on the processor, wherein the processor realizes the steps of the software automation test method when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when being executed by a processor, realizes the steps of the software automated test method.
According to the automatic software testing method and device, the initial testing teller account is extracted from the automatic testing script, then the target testing teller account is determined according to the matching result of the account service attribute of the initial testing teller account and the account service attribute of the idle testing teller account, finally the initial testing teller account in the automatic testing script is replaced by the target testing teller account, the automatic software testing task is executed according to the replaced automatic testing script, the problem of the collision of the testing teller accounts can be solved, and the software testing efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a software automated test method in accordance with one embodiment of the present invention;
FIG. 2 is a flow chart for adjusting account business attributes;
FIG. 3 is a block diagram of a software automated test equipment in an embodiment of the invention;
FIG. 4 is a block diagram of a software automated test equipment in accordance with another embodiment of the present invention;
FIG. 5 is a functional flow diagram of the module of FIG. 4;
FIG. 6 is a functional flow diagram of a script data analysis extraction module and a teller account data storage module;
FIG. 7 is a functional flow diagram of a teller account attribute adjustment module;
fig. 8 is a block diagram of a computer device in an embodiment of the invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Those skilled in the art will appreciate that embodiments of the invention may be implemented as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the following forms, namely: complete hardware, complete software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
In view of the fact that the tested transaction test operation fails due to the fact that the account number conflict of the test teller in the test process frequently occurs in the prior art, the working efficiency of software version function test verification is greatly affected. The present invention will be described in detail with reference to the accompanying drawings.
According to the invention, the test teller account number used by the script operated in the automatic test process is extracted, the teller account number with the same condition and state is searched in the teller account number data storage module of the background, the initial test teller account number in the automatic script is replaced by the special automated test teller account number (test teller account number), and the problem of conflict between the use of the automated test teller account number and the use of the manual test teller account number is solved; meanwhile, the current use states of all the automatic test special teller accounts are registered through the teller account use state maintenance module, only the idle automatic test special teller accounts are selected, the problem of teller account use conflict caused by the fact that the same test teller account is used when a plurality of automatic test scripts are executed simultaneously is solved, and the test execution efficiency is improved.
FIG. 1 is a flow chart of a software automated testing method in an embodiment of the invention. As shown in fig. 1, the software automated test method includes:
s101: and acquiring an automatic test script in the software automatic test task, and extracting an initial test teller account from the automatic test script.
When a tester submits a software automation test task, judging whether the teller data (test teller account number) needs to be replaced, and if not, directly executing the task; execution starts S101 if necessary.
In one embodiment, extracting the initial test teller account number from the automated test script comprises:
and extracting the teller account login transaction from the automatic test script according to the preset keywords and script rules corresponding to the automatic test script, and determining an initial test teller account corresponding to the teller account login transaction.
When the method is implemented, the script operation steps and the script operation parameters are stored separately when the automation test scripts are compiled by different types of automation tools, so that two files of the script operation steps and the script operation parameters are formed respectively. The file storage mode generally comprises text format files such as txt and bin, table files such as key-value format xml configuration files and excel. According to the method, corresponding script rules are selected according to different script types, the script operation step file is analyzed, and the teller account login transaction contained in the script is extracted according to keywords corresponding to the teller account login transaction. After all the teller account login transactions are found, a corresponding initial test teller account (login transaction teller account) is found in the script operation parameter file according to the teller account login transactions, and the initial test teller account and the storage position of the initial test teller account in the script operation parameter file are recorded in the teller account data storage module. When the automatic test script is not parameterized, only a script operation step file exists, and at the moment, an initial test teller account corresponding to the teller account login transaction is searched from the script operation step file.
For example, script execution parameter files for certain types of automated test scripts are stored in a table file. Through analysis of the script operation step file, the fact that two lines of instructions contain keywords of "teller account numbers" indicates that two teller account numbers exist in the script for login transaction, and the positions of the corresponding teller account numbers in the script operation parameter file are respectively that the teller account numbers 90001 are in the row a, the column b and the teller account numbers 90002 are in the row k, the column g.
S102: and determining the target test teller account according to the matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account.
The idle test teller account is stored in a teller account data storage module.
TABLE 1
Table 1 is a table of test teller accounts in the same environment. As shown in Table 1, the account service attributes include country number, area number, network point number, station number, update date, usage status, number of usage times, and test environment. The teller account use state maintenance module in the invention can realize maintenance and registration of teller account use conditions and data abnormal conditions through the test teller account table in the teller account data storage module, achieves the purpose of teller account multiplexing, and ensures that the problem of teller account login conflict does not occur when a plurality of teller accounts in the same test environment login at the same time. The user can configure a corresponding number of special test teller accounts in the test environment according to the concurrency degree of the automatic tasks and the service requirements.
When the test teller account is not logged in, the use state is recorded as idle and available, and the use state can be acquired and used by the software automation test task. When a software automation test task acquires a certain test teller account and starts to execute a script, changing the use state of the corresponding test teller account into use, and recording a state update date, wherein the test teller account is monopolized at the moment, other tasks cannot acquire the test teller account, and the test teller account is prevented from logging in different terminals to cause conflict and error reporting; when the task execution is completed, the test teller account is logged out, the use state of the test teller account is modified into idle availability, the state update date is recorded, and the test teller account can be acquired and used by other software automated test tasks.
According to the invention, the test teller account number in the teller account number data storage module is periodically scanned by the teller account number use state maintenance module, and the test teller account number with abnormal use state is recovered.
In one embodiment, the method further comprises: determining a difference value between the current time and the update date of the account number of the working test teller; and changing the working test teller account number into a free test teller account number according to the comparison result of the difference value and the preset time threshold value.
For example, for a test teller account (working test teller account) that is in "in-use" use for a long time, the periodic daemon task of the teller account use state maintenance module may discover and process test teller account data that is in use timeout because unpredictable errors such as downtime or system crashes may occur in the execution of the software automated test task, resulting in the situation that the test teller account is always in "in-use" use. The teller account usage state maintenance module scans the test teller account in the teller account data storage module regularly, updates the test teller account data which has no change for a long time and is in the "in-use" usage state, judges the login state of the test teller account data, if the test teller account data is in the login state, performs forced sign-in, resets the usage state, modifies the usage state of the test teller account to be free and available, and records the update date.
In one embodiment, the method further comprises: initializing the account service attribute of the abnormal test teller account and changing the abnormal test teller account into a free test teller account.
For example, for a test teller account in an "abnormal" use state for a long time (abnormal test teller account), since the teller account attribute adjustment module modifies the account service attribute of the test teller account in the teller account attribute related service system, and may have an abnormal condition that the account service attribute is inconsistent due to modification and reporting errors, the periodic daemon of the teller account use state maintenance module may also discover and process special teller data with abnormal use state. The module scans the automated special teller in the data storage module at regular time to find out the test teller account with abnormal use state, and then the teller account attribute adjustment module modifies the account service attributes of the teller account into initial values to ensure the uniformity of the number service attribute data in the teller account attribute service system. And after all the adjustment is successful, the account service attribute of the test teller account recorded in the teller account data storage module is modified, the use state is modified to be free and available, and the update date is recorded.
In one embodiment, S102 includes: when the account service attribute of the initial test teller account is matched with the account service attribute of the idle test teller account, selecting a target test teller account from the matched idle test teller accounts according to the account service attribute of each matched idle test teller account.
In the specific implementation, if the number of idle test teller accounts matched with the account business attributes is multiple, in order to make the use frequency of the test teller accounts even, the situation that some test teller accounts are reused and another part of test teller accounts are not used for a long time is avoided, and according to the update date and the use frequency of the test teller accounts, the idle test teller account with the least use frequency and the earliest update date is selected.
In one embodiment, S102 further includes: when the account service attribute of the initial test teller account is not matched with the account service attribute of any idle test teller account, calculating priority parameters of idle test teller accounts according to the account service attribute of the initial test teller account and the account service attribute of each idle test teller account, and determining that the idle test teller account corresponding to the maximum value of the priority parameters is the to-be-adjusted test teller account; and adjusting the account service attribute of the to-be-adjusted test teller account to the account service attribute of the initial test teller account, and determining that the adjusted to-be-adjusted test teller account is the target test teller account.
In one embodiment, calculating the priority parameter of each idle test teller account according to the account service attribute of the initial test teller account and the account service attribute of each idle test teller account includes:
determining account service attribute parameters of each idle test teller account according to the account service attribute of the initial test teller account and the account service attribute of each idle test teller account; and calculating the priority parameter of each idle test teller account according to the account service attribute parameter of each idle test teller account and the corresponding account service attribute weight.
In specific implementation, the priority parameters of each idle test teller account can be determined through the following formula:
wherein G is i Priority parameter for ith idle test teller account, w n For the service attribute weight of the nth account, p in And the service attribute parameter of the nth account number which is the ith idle test teller account number is q which is an adaptation factor.
In particular, since the position number represents the authority of the test teller account and cannot be modified, the position number may be embodied as an fitness factor. The authority of the to-be-adjusted test teller account cannot be smaller than that of the initial test teller account, and if the position number of the to-be-adjusted test teller account is smaller than that of the initial test teller account, the factor score is 0; the bigger the position number is, the bigger the permission gap is, the smaller the corresponding adaptation factor is, and each position number of the test teller account to be adjusted is different from the position number of the initial test teller account by 1, and the adaptation factor is reduced by 0.2.
The update date and the use times are used for controlling the use distribution of the account numbers of the test teller, so that the corresponding weight is relatively larger, and the account number service attribute parameters are calculated according to the queue distribution ordered by the current field duplicate removal value. The earlier the update date or the fewer the number of uses, the larger the account service attribute parameter. And after the update date of each idle test teller account is de-duplicated, sorting the update dates from new to old, and sorting the use times of each idle test teller account from big to small, wherein the update date parameter of the idle test teller account is the ratio of the sorting position of the update date of the idle test teller account to the number of the update dates after de-duplication, and the use times parameter of the idle test teller account is the ratio of the sorting position of the use times of the idle test teller account to the number of the use times after de-duplication.
The country number, the area number and the network point number belong to the account service attribute which can be updated by the test teller account, the corresponding weight is set according to the range size, the parameters are 1 when the account service attribute is matched, and the parameters are 0 when the account service attribute is not matched.
For example, the country number weight is 20, the region number weight is 10, the dot number weight is 5, the update date weight is 40, and the number of uses weight is 40. The account service attributes of the initial test teller account are a country number 11, a region number 300, a network point number 3 and a post number 6 respectively.
TABLE 2
Table 2 is a free test teller account table. As shown in table 2:
for the free test teller account 80001, since the initial test teller account has a position number of 6, the free test teller account has a position number of 5, less than 6, the fitness factor is 0, corresponding to the priority parameter G 1 Is 0.
For the free test teller account 80002, the country number parameter is 1 (the country number 11 of 80002 matches the country number 11 of the initial test teller account), the region number parameter is 0 (the region number 200 of 80002 does not match the region number 300 of the initial test teller account), the site number parameter is 1 (the site number 3 of 80002 matches the site number 3 of the initial test teller account), the update date parameter is 0.75 (the number of update dates after deduplication is 4, the update dates are ordered from new to old, the update date of the free test teller account 80002 is ordered at position 3, so 3/4=0.75), the number of uses parameter is 0.33 (the number of uses after deduplication is ordered from large to small, the number of uses 4 of the free test teller account 80002 is ordered at position first, so 1/3=0.33), the fitness factor is 1 (the position number of post office is matched with the position number of the initial test teller account), and thus the priority parameter of the free test teller account 80002 is:
For the free test teller account 80003, the country number parameter is 1 (the country number 11 of 80003 matches the country number 11 of the initial test teller account), the region number parameter is 1 (the region number 300 of 80003 matches the region number 300 of the initial test teller account), the website number parameter is 0 (the website number 28 of 80003 does not match the website number 3 of the initial test teller account), the update date parameter is 0.5 (the number of update dates after deduplication is 4, the update dates are ordered from new to old, the update date of the free test teller account 80003 is ordered at position 2, so 2/4=0.5), the number of uses parameter is 0.67 (the number of uses after deduplication is ordered from large to small, the number of uses 3 of the free test teller account 80003 is ordered at position second, so 2/3=0.67), the fitness factor is 1 (the post number of 80003 matches the position number of the initial test teller account), and thus the priority parameter of the free test teller account 80003 is:
for the free test teller account 80004, the country number parameter is 1 (the country number 11 of 80004 matches the country number 11 of the initial test teller account), the region number parameter is 1 (the region number 300 of 80004 matches the region number 300 of the initial test teller account), the site number parameter is 0 (the site number 30 of 80004 does not match the site number 3 of the initial test teller account), the update date parameter is 0.25 (the number of update dates after deduplication is 4, the update dates are ordered from new to old, the update date of the free test teller account 80004 is ordered at position 1, so 1/4=0.25), the number of uses parameter is 1 (the number of uses after deduplication is ordered from large to small, so the number of uses 2 of the free test teller account 80004 is ordered at position 3/3=1), the adaptation factor is 0.8 (the number of posts of 80004 is 7, the number of posts with the initial test teller is 6, the adaptation factor is 1- (7.6) ×0.04), so the free test teller account number is ordered at position 0.04).
And selecting the idle test teller account 80003 corresponding to the maximum value of the priority parameters as a test teller account to be adjusted, and adjusting the account service attribute of 80003 into the account service attribute of the initial test teller account through a teller account attribute adjustment module.
If enough idle test teller accounts do not exist at present, namely the test environment, the use state and the like do not meet the conditions, and when the priority parameters are 0, the execution of the software automation test task is paused, the test is performed after waiting for 10 minutes, and the test is performed until the idle test teller accounts needed for executing the software automation test task exist in the teller account data storage module.
Fig. 2 is a flow chart for adjusting account business attributes. As shown in fig. 2, account service attributes are stored in four service systems a, B, C and D, and the teller account attribute adjustment module adjusts the account service attributes in these service systems in order. And when the account service attributes in each service system are updated completely, synchronously modifying the corresponding account service attribute fields in the teller account data storage module.
After the teller account attribute adjustment module adjusts in each service system, whether the account service attribute in the service system is updated successfully or not can be automatically verified. If the exception of a certain system call interface is not updated successfully, the updating process is re-executed; if the test is not successful for 3 times, the execution of the current software automation test task is paused, the test is performed after waiting for 10 minutes, and a warning message is generated to prompt that the update is unsuccessful, so as to check whether the service system has a problem. At this time, there may be a situation that the account service attribute of the test teller account may be inconsistent in a plurality of service systems, and the dirty data cannot be used, so that the teller account attribute adjustment module sets the use state of the test teller account in the teller account data storage module as abnormal, and the use state cannot be used by the software automated test task. The state abnormal test teller account number performs abnormal processing through a teller account number using a state maintenance module to periodically perform teller account number scanning tasks.
S103: and replacing the initial test teller account in the automatic test script with the target test teller account, and executing the software automatic test task according to the replaced automatic test script.
In the specific implementation, the script operation step file or the script operation parameter file can be maintained and modified through the script data maintenance module according to the storage position of the initial test teller account number recorded in the teller account number data storage module in the script operation parameter file, and the initial test teller account number is replaced by the target test teller account number.
For example, the data substitution of multiple test teller accounts is achieved by writing the initial test teller account 90001 to the target test teller account 80001 to row a, column b, and writing the initial test teller account 90002 to the target test teller account 80002 to row k, column g.
The subject of execution of the software automation test shown in fig. 1 may be a computer. As can be seen from the flow shown in fig. 1, the software automation test method in the embodiment of the present invention extracts an initial test teller account from an automation test script, then determines a target test teller account according to a matching result of an account service attribute of the initial test teller account and an account service attribute of a idle test teller account, and finally replaces the initial test teller account in the automation test script with the target test teller account, and executes a software automation test task according to the replaced automation test script, thereby solving the problem of the collision of the test teller accounts and improving the software test efficiency.
The specific flow of the embodiment of the invention is as follows:
1. and acquiring an automatic test script in the software automatic test task.
2. And extracting the teller account login transaction from the automatic test script according to the preset keywords and script rules corresponding to the automatic test script, and determining an initial test teller account corresponding to the teller account login transaction.
3. When the account service attribute of the initial test teller account is matched with the account service attribute of the idle test teller account, selecting a target test teller account from the matched idle test teller accounts according to the account service attribute of each matched idle test teller account.
4. When the account service attribute of the initial test teller account is not matched with the account service attribute of any idle test teller account, calculating priority parameters of each idle test teller account according to the account service attribute of the initial test teller account and the account service attribute of the idle test teller account, determining that the idle test teller account corresponding to the maximum value of the priority parameters is the to-be-adjusted test teller account, adjusting the account service attribute of the to-be-adjusted test teller account to the account service attribute of the initial test teller account, and determining that the adjusted to-be-adjusted test teller account is the target test teller account.
5. And replacing the initial test teller account in the automatic test script with the target test teller account, and executing the software automatic test task according to the replaced automatic test script.
In summary, the software automation test method of the embodiment of the invention firstly extracts the initial test teller account from the automation test script, then determines the target test teller account according to the matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account, finally replaces the initial test teller account in the automation test script with the target test teller account, executes the software automation test task according to the replaced automation test script, can solve the problem of the conflict of the test teller accounts, and improves the software test efficiency.
In summary, the software automation test method provided by the embodiment of the invention has the following beneficial effects:
1. when the automatic test script is executed, a tester can select to use an initial test teller account number or a replaced target test teller account number in the original script, and the original normal use of the tester is not influenced.
2. The invention uniformly distributes and schedules the use, configuration, occupation, sign-off and the like of the test teller account numbers, and the initial test teller account numbers in the original script are not used any more, thereby fundamentally solving the problem of teller account number use conflict generated in a high concurrency scenario when the automatic execution is performed.
3. Because the test teller account number is only used in the automatic test execution process, the test teller account number is completely isolated from the manual test teller account number used by service personnel, and therefore, the use conflict of the teller account number cannot be generated in the manual test process of the test personnel.
4. For special tasks where manual testing of the teller account must be used in part, the tester may choose to follow the initial testing teller account (manual testing teller account) configured in the script.
Based on the same inventive concept, the embodiment of the invention also provides a software automation testing device, and because the principle of the device for solving the problems is similar to that of the software automation testing method, the implementation of the device can be referred to the implementation of the method, and the repetition is omitted.
FIG. 3 is a block diagram of a software automated test equipment in an embodiment of the invention. FIG. 4 is a block diagram of a software automated test equipment in accordance with another embodiment of the present invention. Fig. 5 is a functional flow diagram of the module of fig. 4. FIG. 6 is a functional flow diagram of a script data analysis extraction module and a teller account data storage module. Fig. 7 is a functional flowchart of a teller account attribute adjustment module and a teller account usage status maintenance module. As shown in fig. 3 to 7, the software automated test apparatus includes:
The initial test teller account extraction module is used for acquiring an automatic test script in the software automatic test task and extracting an initial test teller account from the automatic test script;
the target test teller account number determining module is used for determining a target test teller account number according to a matching result of the account number business attribute of the initial test teller account number and the account number business attribute of the idle test teller account number;
and the test teller account replacement module is used for replacing the initial test teller account in the automatic test script with the target test teller account, and executing the software automatic test task according to the replaced automatic test script.
In one embodiment, the target test teller account determination module comprises:
the target test teller account number determining unit is used for selecting a target test teller account number from the matched idle test teller accounts according to the account number business attributes of the matched idle test teller accounts when the account number business attributes of the initial test teller account number are matched with the account number business attributes of the idle test teller accounts.
In one embodiment, the target test teller account determination module further comprises:
the to-be-adjusted test teller account determining unit is used for calculating priority parameters of each idle test teller account according to the account business attribute of the initial test teller account and the account business attribute of the idle test teller account when the account business attribute of the initial test teller account is not matched with the account business attribute of any idle test teller account, and determining that the idle test teller account corresponding to the maximum value of the priority parameters is the to-be-adjusted test teller account;
The account service attribute adjusting unit is used for adjusting the account service attribute of the to-be-adjusted test teller account to the account service attribute of the initial test teller account, and determining that the adjusted to-be-adjusted test teller account is the target test teller account.
In one embodiment, the test teller account replacement module is specifically configured to:
and extracting the teller account login transaction from the automatic test script according to the preset keywords and script rules corresponding to the automatic test script, and determining an initial test teller account corresponding to the teller account login transaction.
As shown in fig. 4 to 7, in practical application, the software automation testing device includes a script data analysis and extraction module, a teller account data matching module, a teller account data storage module, a teller account usage state maintenance module, a teller account attribute adjustment module, and a script data maintenance module.
As shown in fig. 4-5, script sentences are analyzed one by a script data analysis and extraction module, a teller account login transaction in an automatic test script is extracted according to keywords, and then account service attributes of an initial test teller account are obtained through corresponding relations of script parameters. And acquiring the test teller account with attribute matching and idle available state from the teller account data storage module according to the account service attribute of the initial test teller account by the teller account data matching module. If the test teller account with no attribute matching is still required to update the account service attribute of the idle test teller account through the teller account attribute adjustment module, so that the account service attribute of the idle test teller account meets the requirement. In addition, the state of the test teller account is recorded through the teller account use state maintenance module, so that multiplexing of the test teller account is controlled, and abnormal states are processed. And finally, writing the target test teller account number into an automation script through a script data maintenance module to replace the original initial test teller account number, and executing an automation task by using the replaced data.
As shown in fig. 6, the script data analysis and extraction module includes an initial test teller account extraction module, which is responsible for analyzing an automation script to be executed according to a script format and rules, and extracting all login teller account data used in the script. And recording an initial test teller account and a storage position of the initial test teller account in the script operation parameter file in the teller account data storage module.
The teller account data storage module is used for storing account service attributes of the test teller account, such as country numbers, area numbers, network point numbers, post numbers, update dates, use states, use times, test environment numbers and the like, through the account service attributes, the teller account data matching module can inquire and match the corresponding test teller account, and the teller account use state maintenance module realizes maintenance and registration of teller account use conditions and data abnormal conditions through the use state fields, so that the purpose of teller account multiplexing is achieved.
As shown in fig. 7, the teller account usage state maintenance module is configured to perform maintenance registration on the usage state of the test teller account according to the current usage situation of the test teller account.
For the test teller account in the "in-use" use state for a long time, because unpredictable errors such as downtime or system breakdown and the like can occur in the execution of the software automation test task, the test teller account is always in the "in-use" use state, and therefore the periodic daemon task of the teller account use state maintenance module can find and process the test teller account data with overtime use. The teller account usage state maintenance module scans the test teller account in the teller account data storage module regularly, updates the test teller account data which has no change for a long time and is in the "in-use" usage state, judges the login state of the test teller account data, if the test teller account data is in the login state, performs forced sign-in, resets the usage state, modifies the usage state of the test teller account to be free and available, and records the update date.
For the test teller account in the "abnormal" use state for a long time, because the teller account attribute adjustment module modifies the account service attribute of the test teller account in the teller account attribute related service system, the abnormal condition that the account service attribute is inconsistent due to modification error may occur, so the periodic daemon task of the teller account use state maintenance module also can find and process the special teller data with abnormal use state. The module scans the automated special teller in the data storage module at regular time to find out the test teller account with abnormal use state, and then the teller account attribute adjustment module modifies the account service attributes of the teller account into initial values to ensure the uniformity of the number service attribute data in the teller account attribute service system. And after all the adjustment is successful, the account service attribute of the test teller account recorded in the teller account data storage module is modified, the use state is modified to be free and available, and the update date is recorded.
The teller account data matching module comprises a target test teller account determining unit and a to-be-adjusted test teller account determining unit, and is used for inquiring corresponding account service attributes such as country numbers, area numbers, network point numbers, post numbers and the like in a test environment to which a current task belongs according to an initial test teller account extracted by a script, and obtaining test teller accounts with matched attributes from the teller account data storage module according to the account service attributes.
The teller account attribute adjustment module comprises an account service attribute adjustment unit, and is used for modifying and maintaining each account service attribute in the related service system. And when the account service attributes in each service system are updated completely, synchronously modifying the corresponding account service attribute fields in the teller account data storage module.
The script data maintenance module comprises a test teller account replacement module, which is used for maintaining and modifying a script operation step file or a script operation parameter file according to the storage position of the initial test teller account recorded in the teller account data storage module in the script operation parameter file, and replacing the initial test teller account with a target test teller account.
In summary, the software automation testing device of the embodiment of the invention firstly extracts the initial testing teller account from the automation testing script, then determines the target testing teller account according to the matching result of the account service attribute of the initial testing teller account and the account service attribute of the idle testing teller account, finally replaces the initial testing teller account in the automation testing script with the target testing teller account, executes the software automation testing task according to the replaced automation testing script, can solve the problem of the conflict of the testing teller accounts, and improves the software testing efficiency.
The embodiment of the invention also provides a concrete implementation mode of the computer equipment capable of realizing all the steps in the software automatic test method in the embodiment. Fig. 8 is a block diagram of a computer device according to an embodiment of the present invention, and referring to fig. 8, the computer device specifically includes:
a processor (processor) 801 and a memory (memory) 802.
The processor 801 is configured to invoke a computer program in the memory 802, where the processor executes the computer program to implement all the steps in the software automated test method in the foregoing embodiment, for example, the processor executes the computer program to implement the following steps:
acquiring an automatic test script in a software automatic test task, and extracting an initial test teller account from the automatic test script;
determining a target test teller account according to a matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account;
and replacing the initial test teller account in the automatic test script with the target test teller account, and executing the software automatic test task according to the replaced automatic test script.
In summary, the computer device of the embodiment of the invention firstly extracts the initial test teller account from the automatic test script, then determines the target test teller account according to the matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account, finally replaces the initial test teller account in the automatic test script with the target test teller account, executes the software automatic test task according to the replaced automatic test script, can solve the problem of the conflict of the test teller accounts, and improves the software test efficiency.
The embodiment of the present invention further provides a computer readable storage medium capable of implementing all the steps of the software automation test method in the above embodiment, where the computer readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program implements all the steps of the software automation test method in the above embodiment, for example, the processor implements the following steps when executing the computer program:
acquiring an automatic test script in a software automatic test task, and extracting an initial test teller account from the automatic test script;
determining a target test teller account according to a matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account;
And replacing the initial test teller account in the automatic test script with the target test teller account, and executing the software automatic test task according to the replaced automatic test script.
In summary, the computer readable storage medium of the embodiment of the invention firstly extracts the initial test teller account from the automatic test script, then determines the target test teller account according to the matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account, finally replaces the initial test teller account in the automatic test script with the target test teller account, executes the software automatic test task according to the replaced automatic test script, can solve the problem of the conflict of the test teller accounts, and improves the software test efficiency.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.
Those of skill in the art will further appreciate that the various illustrative logical blocks (illustrative logical block), units, and steps described in connection with the embodiments of the invention may be implemented by electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components (illustrative components), elements, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present invention.
The various illustrative logical blocks, or units, or devices described in the embodiments of the invention may be implemented or performed with a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described. A general purpose processor may be a microprocessor, but in the alternative, the general purpose processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In an example, a storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may reside in a user terminal. In the alternative, the processor and the storage medium may reside as distinct components in a user terminal.
In one or more exemplary designs, the above-described functions of embodiments of the present invention may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on a computer-readable medium or transmitted as one or more instructions or code on the computer-readable medium. Computer readable media includes both computer storage media and communication media that facilitate transfer of computer programs from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. For example, such computer-readable media may include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store program code in the form of instructions or data structures and other data structures that may be read by a general or special purpose computer, or a general or special purpose processor. Further, any connection is properly termed a computer-readable medium, e.g., if the software is transmitted from a website, server, or other remote source via a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless such as infrared, radio, and microwave, and is also included in the definition of computer-readable medium. The disks (disks) and disks (disks) include compact disks, laser disks, optical disks, DVDs, floppy disks, and blu-ray discs where disks usually reproduce data magnetically, while disks usually reproduce data optically with lasers. Combinations of the above may also be included within the computer-readable media.
Claims (8)
1. A method for automated testing of software, comprising:
acquiring an automatic test script in a software automatic test task, and extracting an initial test teller account from the automatic test script;
determining a target test teller account according to a matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account;
replacing an initial test teller account in the automatic test script with the target test teller account, and executing a software automatic test task according to the replaced automatic test script;
determining the target test teller account according to the matching result of the account service attribute of the initial test teller account and the account service attribute of the idle test teller account comprises:
when the account service attribute of the initial test teller account is not matched with the account service attribute of any idle test teller account, calculating priority parameters of idle test teller accounts according to the account service attribute of the initial test teller account and the account service attribute of each idle test teller account, and determining that the idle test teller account corresponding to the maximum value of the priority parameters is the test teller account to be adjusted;
The account service attribute of the to-be-adjusted test teller account is adjusted to the account service attribute of the initial test teller account, and the adjusted to-be-adjusted test teller account is determined to be the target test teller account;
the computing the priority parameter of each idle test teller account according to the account service attribute of the initial test teller account and the account service attribute of each idle test teller account comprises:
determining account service attribute parameters of each idle test teller account according to the account service attribute of the initial test teller account and the account service attribute of each idle test teller account;
and calculating the priority parameter of each idle test teller account according to the account service attribute parameter of each idle test teller account and the corresponding account service attribute weight.
2. The method according to claim 1, wherein determining the target test teller account according to a result of matching the account service attribute of the initial test teller account with the account service attribute of the idle test teller account comprises:
and when the account service attribute of the initial test teller account is matched with the account service attribute of the idle test teller account, selecting a target test teller account from the matched idle test teller accounts according to the account service attribute of each matched idle test teller account.
3. The software automated testing method of claim 1, wherein extracting an initial test teller account from the automated test script comprises:
and extracting a teller account login transaction from the automatic test script according to preset keywords and script rules corresponding to the automatic test script, and determining an initial test teller account corresponding to the teller account login transaction.
4. The method for automated software testing according to claim 1, wherein the account service attribute comprises an update date;
the software automated testing method further comprises the following steps:
determining a difference value between the current time and the update date of the account number of the working test teller;
and changing the work test teller account into a idle test teller account according to a comparison result of the difference value and a preset time threshold.
5. The software automated testing method of claim 1, further comprising:
initializing account service attributes of the abnormal test teller account and changing the abnormal test teller account into a idle test teller account.
6. A software automated testing apparatus, comprising:
the initial test teller account extraction module is used for acquiring an automatic test script in the software automatic test task and extracting an initial test teller account from the automatic test script;
The target test teller account number determining module is used for determining a target test teller account number according to a matching result of the account number business attribute of the initial test teller account number and the account number business attribute of the idle test teller account number;
the test teller account replacement module is used for replacing the initial test teller account in the automatic test script with the target test teller account, and executing a software automatic test task according to the replaced automatic test script;
the target test teller account number determining module comprises:
the to-be-adjusted test teller account determining unit is used for calculating priority parameters of each idle test teller account according to the account business attribute of the initial test teller account and the account business attribute of the idle test teller account when the account business attribute of the initial test teller account is not matched with the account business attribute of any idle test teller account, and determining that the idle test teller account corresponding to the maximum value of the priority parameters is the to-be-adjusted test teller account;
the account service attribute adjustment unit is used for adjusting the account service attribute of the to-be-adjusted test teller account to the account service attribute of the initial test teller account, and determining that the adjusted to-be-adjusted test teller account is the target test teller account;
The to-be-adjusted test teller account number determining unit is specifically configured to:
determining account service attribute parameters of each idle test teller account according to the account service attribute of the initial test teller account and the account service attribute of each idle test teller account;
and calculating the priority parameter of each idle test teller account according to the account service attribute parameter of each idle test teller account and the corresponding account service attribute weight.
7. A computer device comprising a memory, a processor and a computer program stored on the memory and running on the processor, characterized in that the processor implements the steps of the software automated test method of any of claims 1 to 5 when the computer program is executed by the processor.
8. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the software automated test method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110095607.2A CN112783773B (en) | 2021-01-25 | 2021-01-25 | Automatic software testing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110095607.2A CN112783773B (en) | 2021-01-25 | 2021-01-25 | Automatic software testing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112783773A CN112783773A (en) | 2021-05-11 |
| CN112783773B true CN112783773B (en) | 2024-02-06 |
Family
ID=75758898
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110095607.2A Active CN112783773B (en) | 2021-01-25 | 2021-01-25 | Automatic software testing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112783773B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107832230A (en) * | 2017-12-04 | 2018-03-23 | 中国工商银行股份有限公司 | Method of testing, equipment and system based on data tuning |
| CN110362493A (en) * | 2019-07-18 | 2019-10-22 | 中国工商银行股份有限公司 | Electronic equipment response method and device, electronic equipment and readable storage medium storing program for executing |
| CN111949545A (en) * | 2020-08-19 | 2020-11-17 | 彩讯科技股份有限公司 | Automatic testing method, system, server and storage medium |
| CN112134901A (en) * | 2020-09-29 | 2020-12-25 | 中国银行股份有限公司 | Work authority sharing method and device, server and computer storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10565095B2 (en) * | 2016-12-15 | 2020-02-18 | Syntel, Inc. | Hybrid testing automation engine |
-
2021
- 2021-01-25 CN CN202110095607.2A patent/CN112783773B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107832230A (en) * | 2017-12-04 | 2018-03-23 | 中国工商银行股份有限公司 | Method of testing, equipment and system based on data tuning |
| CN110362493A (en) * | 2019-07-18 | 2019-10-22 | 中国工商银行股份有限公司 | Electronic equipment response method and device, electronic equipment and readable storage medium storing program for executing |
| CN111949545A (en) * | 2020-08-19 | 2020-11-17 | 彩讯科技股份有限公司 | Automatic testing method, system, server and storage medium |
| CN112134901A (en) * | 2020-09-29 | 2020-12-25 | 中国银行股份有限公司 | Work authority sharing method and device, server and computer storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112783773A (en) | 2021-05-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8954397B2 (en) | Creation and replay of a simulation workload using captured workloads | |
| CN108804306B (en) | Method and system for automatic test system | |
| CN102236705B (en) | The fine granularity that data base resets synchronizes | |
| US6185701B1 (en) | Automated client-based web application URL link extraction tool for use in testing and verification of internet web servers and associated applications executing thereon | |
| CN101135989B (en) | Automatization test method and device for Web applied system | |
| US6182245B1 (en) | Software test case client/server system and method | |
| US20060064456A1 (en) | Multistep master data cleansing in operative business processes | |
| CN109460841B (en) | User account opening method, system and storage medium | |
| CN105677465B (en) | The data processing method and device of batch processing are run applied to bank | |
| US20220019625A1 (en) | Systems and methods for improved transactional mainframes | |
| US8595559B2 (en) | Method and apparatus for model-based testing of a graphical user interface | |
| CN117914737A (en) | Mirror image resource testing method and device for network target range | |
| CN112783773B (en) | Automatic software testing method and device | |
| CN116226092B (en) | Database updating method and device | |
| US20240161109A1 (en) | Distributed evaluation platform for nonfungible tokens using virtual token cloning | |
| US10003492B2 (en) | Systems and methods for managing data related to network elements from multiple sources | |
| US20220300461A1 (en) | Correction, Synchronization, and Migration of Databases | |
| CN114595216A (en) | Data verification method and device, storage medium and electronic equipment | |
| CN113157583A (en) | Test method, device and equipment | |
| CN111767222A (en) | Data model verification method and device, electronic equipment and storage medium | |
| CN110609790A (en) | Analytic program test method, device, medium and computer equipment | |
| CN111915279B (en) | Method, device and system for auditing operation data stream | |
| CN112835588B (en) | Code auditing method and device | |
| WO2022267181A1 (en) | Method and apparatus for generating code list, computer device, and storage medium | |
| US20220222227A1 (en) | Correction, synchronization, and migration of databases |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |