WO2018202172A1

WO2018202172A1 - Mass comparison test method and system

Info

Publication number: WO2018202172A1
Application number: PCT/CN2018/085723
Authority: WO
Inventors: 邓亦超
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-05-05
Filing date: 2018-05-04
Publication date: 2018-11-08
Also published as: CN107870859B; CN107870859A

Abstract

A mass comparison test method and system. The method comprises: configuring a rollback point for a mass comparison test database (S100); calculating, according to basic data in the mass comparison test database, a receivable insurance premium, to obtain first result data (S102); performing, according to the configured rollback point, a rollback of the mass comparison test database (S104); upon the deployment of a new version of code, re-calculating the receivable insurance premium, to obtain second result data (S106); comparing the first result data with the second result data and determining whether there is a difference (S108); analyzing the difference, and determining whether the difference is caused by program defects of the new version of code (S110). Thus, a comparison test between the new version and the old version of a receivable insurance premium system can be performed in a full-coverage manner.

Description

Mass comparison test method and system

The present application claims priority to Chinese Patent Application No. 2009103123280, the entire disclosure of which is incorporated herein by reference. .

Technical field

The present application relates to the field of database technology, and in particular, to a large-scale comparative test method and system.

Background technique

At present, when the life insurance system calculates the premiums receivable in the next period, the system business scenario is complex, and the amount of information carried by the data interface that needs to be called is very large. After the system business function is upgraded, generally only the regular function verification is performed. The data covered by the system test may not be comprehensive enough, and an effective automated test means is not available to cover all the test data.

If you rely on the traditional manual method to check the data, the following problems may occur: a lot of manpower is required, and the efficiency is low; the newly added services may affect the normal operation of the old functions, and the traditional verification method cannot fully cover all functions; The amount of data that can be processed is small, and it is impossible to fully cover the business scenario; the impact of new business functions on performance and resources cannot be estimated; the abnormal class test data cannot be covered; it is easy to cause missed measurement. All of the above problems can cause significant losses.

Therefore, there is a need for a software test method that can perform batch data testing, cover all business scenarios, and be able to assess the functional differences and impacts of service upgrades, and can adapt to continuous system updates and complete corresponding test tasks.

Summary of the invention

In view of this, the purpose of the present application is to provide a high-volume comparison test method and system to solve the problem of how to perform the comparison test of the before and after versions of the premium receivable system in full coverage.

To achieve the above object, the present application provides a high-volume comparison test method, the method comprising the steps of:

Set the rollback point of the large batch comparison test database;

Calculating the premium receivable according to the basic data in the large batch comparison test database, and obtaining the first result data;

Performing rollback of the large batch comparison test database according to the set rollback point;

After deploying the new version code, calculate the premium receivable again and get the second result data;

Comparing the first result data with the second result data to determine whether there is a difference; and

The difference is analyzed to determine whether it is caused by a program defect of the new version code.

To achieve the above object, the present application also provides a high-volume comparison test system, the system comprising:

Setting module for setting the rollback point of the large batch comparison test database;

a calculation module, configured to calculate the premium receivable according to the basic data in the large batch comparison test database, and obtain the first result data;

a rollback module, configured to perform rollback of the large batch comparison test database according to the set rollback point;

The calculation module is further configured to: after the new version code is deployed, calculate the premium receivable again to obtain the second result data;

a comparison module, configured to compare the first result data with the second result data to determine whether there is a difference;

An analysis module is configured to analyze the difference and determine whether it is caused by a program defect of the new version code.

To achieve the above objective, the present application provides a computer readable storage medium having a large batch comparison test system stored therein, the high volume comparison test system comprising:

The high-volume comparison test method, system and computer readable storage medium proposed by the present application use a database rollback method to perform large-volume data comparison test, first calculate the premium receivable for the old version, save the result table and import it into other databases. Backup, then perform database rollback, then perform the receivable premium calculation again for the data of the new version interface, save the result table, and compare and analyze the data of the two saved result tables, which can reduce the test manpower and increase the test coverage. Moreover, the basis of the database rollback ensures that the basic conditions of the two test results are consistent, which can guarantee the effectiveness of the comparison test.

DRAWINGS

1 is a flowchart of a high-volume comparison test method according to a first embodiment of the present application;

2 is a flow chart of a method for testing a large batch of comparisons according to a second embodiment of the present application;

3 is a flow chart of a method for testing a large batch of comparisons according to a third embodiment of the present application;

4 is a schematic diagram of a module of a large batch comparison test system according to a fourth embodiment of the present application;

The object of the present application, the features and advantages of the present application will be further described with reference to the accompanying drawings.

detailed description

In order to make the technical problems, technical solutions and beneficial effects to be solved by the present application clearer and clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

First embodiment

As shown in FIG. 1 , the first embodiment of the present application provides a high-volume comparison test method, which includes the following steps:

S100, set the rollback point of the large batch comparison test database.

Specifically, according to the set rollback point, after the rollback of the large batch comparison test database is performed, the data state in the large batch comparison test database will be restored to the state of the rollback point. Pay attention to the time to set the rollback point, because the rollback is a rollback that indicates the state of the database. Once rolled back, the data and code will be rolled back.

It is worth noting that the status of the data will change after the code is run. If the data is deleted before and after the comparison test, the data deletion may be unclean and affect the results of the comparison test. The way the database is rolled back ensures that the state of the data when testing the new version of the code is the same as the state of the data when testing the old version of the code. The purpose is to ensure that the underlying conditions of the comparison result are consistent and to ensure the validity of the comparison test.

In other embodiments, the step S100 may also be performed after the step S102 described below.

S102. Calculate the premium receivable according to the basic data in the large batch comparison test database, and obtain the first result data.

Specifically, in the table tst_rbs_prem_due_tmp, the data of proc_flag='N' is captured, and the core interface lifeman.rbs_prem_due_package.policy_due_draw_core of the receivable premium is generated to generate the receivable data, and then the flag of the proc_flag is updated to Y, to avoid repeatedly fetching data. .

After calling the core interface of the receivable file, the receivable data is mainly generated in the prem_due table and the stat_prem_due table. For the data of proc_flag=‘Y’ in tst_rbs_prem_due_tmp, the same policy, the same due date information, and the main check field are obtained in the prem_due table, and the fields to be checked are combined into a new field. Also in the stat_prem_due table, the same policy, the same due date information and the main check field are obtained.

Here, by the switch tst_rbs_control_table, control_id is PREM_DUE_DATA_OLD, and v_control_char = 'N' is controlled to calculate the premium data under the old version code. The obtained first result data is written in the table tst_prem_due_case_old.

S104. Perform rollback of the large batch comparison test database according to the set rollback point.

Specifically, after the rollback, the data state in the large batch comparison test database is restored to the state of the rollback point. Therefore, the basic conditions when the calculation is performed again later are consistent with the calculation of the first result data.

S106. After deploying the new version code, calculate the premium receivable again and obtain the second result data.

Specifically, when the new version code is deployed to the high-volume comparison test database, the premium receivable is recalculated based on the new version code. In order to ensure that the premium data under the new version code is calculated here, the switch at this time is tst_rbs_control_table, control_id is the state of PREM_DUE_DATA_OLD, and v_control_char = 'Y'. The second result data obtained by recalculating the premium receivable is written in the table tst_prem_due_case_new.

Corresponding to the first result data, the second result data also includes the same policy acquired in the prem_due table, the information of the same due date, the main check field, and the same policy obtained in the stat_prem_due table. , the same due date information and the main check field.

S108. Compare the first result data with the second result data to determine whether there is a difference.

Specifically, a comparison analysis is performed on the first result data (tst_prem_due_case_old) and the second result data (tst_prem_due_case_new), and the analyzed differences are written in the table tst_rbs_exception. After checking the data, you need to update the corresponding policy and the proc_flag of the due date to Y, indicating that the data has been checked to avoid repeated verification.

S110, analyzing the difference to determine whether it is caused by a program defect of the new version code.

Specifically, by analyzing the difference data in the table tst_rbs_exception, the cause of the abnormality is determined to see if it is a problem caused by a program defect of the new version code. If it is a problem caused by a bug in the new version of the code, you need to fix the new version of the code.

In this embodiment, the content added or changed in the new version code and the contents of the added or changed content may be recorded in accordance with which items of the premium data are affected. When there is a difference between the first result data and the second result data, it is determined whether it is a program defect by analyzing whether the difference belongs to an item affected by the added or changed content. If the difference belongs to an item affected by the added or changed content, it means that it is not a program defect, and the difference is ignored. If the difference does not belong to the item affected by the added or changed content, it means that the difference is a program defect and needs to be repaired.

The large-scale comparison test method proposed in this embodiment adopts a database rollback method to perform large-volume data comparison test, first performs the premium collection calculation on the old version, and then performs database rollback, and then data for the new version interface again. Carry out the calculation of the premiums receivable, and compare and analyze the data obtained from the two calculations to reduce the test manpower and increase the test coverage. Moreover, the basis of the database rollback ensures that the basic conditions of the two test results are consistent, which can guarantee the effectiveness of the comparison test.

Second embodiment

As shown in FIG. 2, the second embodiment of the present application proposes a large-scale comparison test method. In the second embodiment, the steps of the mass comparison test method are similar to those of the first embodiment, the main difference being that steps S204 and S210 are added on the basis of the first embodiment. The method specifically includes the following steps:

S200, set the rollback point of the large batch comparison test database.

In other embodiments, the step S200 may also be performed after the step S202 described below.

S202. Calculate the premium receivable according to the basic data in the large batch comparison test database, and obtain the first result data.

S204. Import the first result data into another database for backup.

Specifically, the first result data of the table tst_prem_due_case_old is imported into another database, and can be imported by means of a database link (Database Link, dblink). Because when the database is rolled back, the result set will also be rolled back together, so the result set needs to be backed up, and then returned to the large batch comparison test library.

S206. Perform rollback of the large batch comparison test database according to the set rollback point.

S208: After deploying the new version code, calculate the premium receivable again to obtain the second result data.

Specifically, when the new version code is deployed to the high-volume comparison test database, the premium receivable is recalculated based on the new version code. In order to ensure that the premium data under the new version code is calculated here, the switch at this time is tst_rbs_control_table, the control_id is PREM_DUE_DATA_OLD, and the state of v_control_char = 'Y'. The second result data obtained by recalculating the premium receivable is written in the table tst_prem_due_case_new.

S210. The first result data is returned to the large batch comparison test database.

Specifically, the first result data of the table tst_prem_due_case_old is returned to the large batch comparison test library by means of dblink from the another database.

S212. Compare the first result data with the second result data to determine whether there is a difference.

S214, analyzing the difference and determining whether it is caused by a program defect of the new version code.

In this embodiment, the content added or changed in the new version code and the contents of the added or changed may be recorded in accordance with which items of the premium data are affected. When there is a difference between the first result data and the second result data, it is determined whether it is a program defect by analyzing whether the difference belongs to an item affected by the added or changed content. If the difference belongs to an item affected by the added or changed content, it means that it is not a program defect, and the difference is ignored. If the difference does not belong to the item affected by the added or changed content, it means that the difference is a program defect and needs to be repaired.

The large-scale comparison test method proposed in this embodiment adopts a database rollback method to perform large-volume data comparison test, first performs the premium collection of the old version, saves the result table and imports it into other databases for backup, and then performs the database back. Roll, then perform the receivable premium calculation again for the data of the new version interface, save the result table, and compare and analyze the data of the two saved result tables, which can reduce the test manpower and increase the test coverage. Moreover, the basis of the database rollback ensures that the basic conditions of the two test results are consistent, which can guarantee the effectiveness of the comparison test. In addition, backing up the results table of the first calculation ensures that the result table is not affected by the database rollback.

Third embodiment

As shown in FIG. 3, the third embodiment of the present application proposes a mass comparison test method. In the third embodiment, the steps of the mass comparison test method are similar to those of the second embodiment, the main difference being that step S300 and step S302 are added on the basis of the second embodiment. The method specifically includes the following steps:

S300, set the range and time for obtaining the basic data.

Specifically, the data of the specified delivery date range (generally the next month) is set, and the time of the capture can be set by controlling the corresponding program switch to periodically capture a batch of basic data.

S302: Acquire basic data into the large-scale comparison test database according to the set range and time.

Specifically, the data of the specified due date range is fetched according to the set time, and the basic data satisfying the condition is obtained, and is written in the table tst_rbs_prem_due_tmp.

S304. Set a rollback point of the large batch comparison test database.

In other embodiments, the step S304 can also be performed after the step S306 described below.

S306. Calculate the premium receivable according to the obtained basic data, and obtain the first result data.

S308. Import the first result data into another database for backup.

Specifically, the first result data of the table tst_prem_due_case_old is imported into another database, and can be imported by means of dblink. Because when the database is rolled back, the result set will also be rolled back together, so the result set needs to be backed up, and then returned to the large batch comparison test library.

S310. Perform rollback of the large batch comparison test database according to the set rollback point.

S312. After deploying the new version code, calculate the premium receivable again and obtain the second result data.

S314, the first result data is returned to the large batch comparison test database.

S316. Compare the first result data with the second result data to determine whether there is a difference.

S318, analyzing the difference to determine whether it is caused by a program defect of the new version code.

The large-scale comparison test method proposed in this embodiment adopts a database rollback method to perform large-volume data comparison test, first performs the premium collection of the old version, saves the result table and imports it into other databases for backup, and then performs the database back. Roll, then perform the receivable premium calculation again for the data of the new version interface, save the result table, and compare and analyze the data of the two saved result tables, which can reduce the test manpower and increase the test coverage. Moreover, the database is rolled back to ensure that the basic conditions of the two test results are consistent, which can guarantee the effectiveness of the comparison test. In addition, backing up the results table of the first calculation ensures that the result table is not affected by the database rollback.

Fourth embodiment

As shown in FIG. 4, the fourth embodiment of the present application proposes a mass comparison test system 40.

In the present embodiment, the high-volume comparison test system 40 includes a setup module 400, a calculation module 402, a rollback module 404, a comparison module 406, and an analysis module 408.

The setting module 400 is configured to set a rollback point of the large batch comparison test database.

The calculating module 402 is configured to calculate the premium receivable according to the basic data in the large batch comparison test database to obtain the first result data.

Here, by the switch tst_rbs_control_table, control_id is PREM_DUE_DATA_OLD, and v_control_char = 'N' is controlled to calculate the premium data under the old version code. The resulting first result data is written in the table tst_prem_due_case_old.

The rollback module 404 is configured to perform rollback of the large batch comparison test database according to the set rollback point.

The calculating module 402 is further configured to calculate the premium receivable again after the new version code is deployed, to obtain the second result data.

Specifically, after deploying the new version code to the high volume comparison test database, the calculation module 402 recalculates the premium receivable based on the new version code. In order to ensure that the premium data under the new version code is calculated here, the switch at this time is tst_rbs_control_table, the control_id is PREM_DUE_DATA_OLD, and the state of v_control_char = 'Y'. The second result data obtained by recalculating the premium receivable is written in the table tst_prem_due_case_new.

The comparison module 406 is configured to compare the first result data with the second result data to determine whether there is a difference.

Specifically, the comparison module 406 performs a comparative analysis on the first result data (tst_prem_due_case_old) and the second result data (tst_prem_due_case_new), and writes the analyzed difference into the table tst_rbs_exception. After checking the data, you need to update the corresponding policy and the proc_flag of the due date to Y, indicating that the data has been checked to avoid repeated verification.

The analysis module 408 is configured to analyze the difference and determine whether it is caused by a program defect of the new version code.

Further, the high volume comparison test system 40 may further include:

The backup module 410 is configured to import the first result data into another database for backup before the rollback module 404 performs rollback of the large batch comparison test database.

Specifically, the backup module 410 imports the first result data of the table tst_prem_due_case_old into another database, and can be imported by means of dblink. Because when the database is rolled back, the result set will also be rolled back together, so the result set needs to be backed up, and then returned to the large batch comparison test library.

The backup module 410 is further configured to, after the calculating module 402 obtains the second result data, import the first result data back into the large batch comparison test database.

Specifically, the backup module 410 imports the first result data of the table tst_prem_due_case_old from the another database to the large batch comparison test library by way of dblink.

Further, the setting module 400 is further configured to set a range and time for acquiring basic data.

Specifically, the setting module 400 sets the data for grasping the specified delivery date range (generally the next month), and the time of the capture can be set by controlling the corresponding program switch to periodically capture a batch of basic data.

Moreover, the high volume comparison test system 40 may further include:

The obtaining module 412 is configured to obtain basic data into the large batch comparison test database according to the range and time set by the setting module 400.

Specifically, the obtaining module 412 fetches the data of the specified delivery date according to the set time, and obtains basic data that satisfies the condition, and writes the data into the table tst_rbs_prem_due_tmp.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and can also be implemented by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

The preferred embodiments of the present application have been described above with reference to the drawings, and are not intended to limit the scope of the application. The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments. Additionally, although logical sequences are shown in the flowcharts, in some cases the steps shown or described may be performed in a different order than the ones described herein.

A person skilled in the art can implement the present application in various variants without departing from the scope and spirit of the present application. For example, the features as one embodiment can be used in another embodiment to obtain another embodiment. Any modifications, equivalent substitutions and improvements made within the technical concept of the application should be within the scope of the application.

Claims

A high-volume comparison test method, characterized in that the method comprises the steps of:

Set the rollback point of the large batch comparison test database;

Calculating the premium receivable according to the basic data in the large batch comparison test database, and obtaining the first result data;

Performing rollback of the large batch comparison test database according to the set rollback point;

After deploying the new version code, calculate the premium receivable again and get the second result data;

Comparing the first result data with the second result data to determine whether there is a difference; and

The difference is analyzed to determine whether it is caused by a program defect of the new version code.
The high-volume comparison test method according to claim 1, further comprising the steps of:

Importing the first result data into another database for backup before performing the rollback of the large batch comparison test database; and

After the second result data is obtained, the first result data is returned to the high volume comparison test database.
The high-volume comparison test method according to claim 2, wherein the method further comprises the steps of:

Setting the scope and time for obtaining the basic data; and

The basic data is obtained into the large batch comparison test database according to the set range and time.
The high-volume comparison test method according to claim 3, wherein the range of the acquisition basic data is a specified delivery date range.
The large-scale comparison test method according to claim 1, wherein after the rollback, the data state in the large batch comparison test database is restored to the state of the rollback point.
The large-scale comparison test method according to claim 2, wherein after the rollback, the data state in the large batch comparison test database is restored to the state of the rollback point.
The high-volume comparison test method according to claim 3 or 4, characterized in that after the rollback, the data state in the large batch comparison test database is restored to the state of the rollback point.
A high volume comparison test system, characterized in that the system comprises:

Setting module for setting the rollback point of the large batch comparison test database;

a calculation module, configured to calculate the premium receivable according to the basic data in the large batch comparison test database, and obtain the first result data;

a rollback module, configured to perform rollback of the large batch comparison test database according to the set rollback point;

The calculation module is further configured to: after the new version code is deployed, calculate the premium receivable again to obtain the second result data;

a comparison module, configured to compare the first result data with the second result data to determine whether there is a difference;

An analysis module is configured to analyze the difference and determine whether it is caused by a program defect of the new version code.
The high-volume comparison test system according to claim 8, wherein the system further comprises:

a backup module, configured to import the first result data into another database for backup before performing the rollback of the large batch comparison test database; and, after obtaining the second result data, the first A result data is returned to the bulk comparison test database.
The high volume comparison test system of claim 9 wherein said system further comprises an acquisition module, wherein:

The setting module is further configured to set a range and time for acquiring the basic data;

The obtaining module is configured to acquire the basic data into the large batch comparison test database according to the set range and time.
The high-volume comparison test system according to claim 10, wherein the range of the acquisition basic data is a specified delivery date range.
The large batch comparison test system according to claim 8, wherein after the rollback, the data state in the large batch comparison test database is restored to the state of the rollback point.
The high-volume comparison test system according to claim 9, wherein after the rollback, the data state in the large batch comparison test database is restored to the state of the rollback point.
The large batch comparison test system according to claim 10 or 11, wherein after the rollback, the data state in the large batch comparison test database is restored to the state of the rollback point.
A computer readable storage medium, wherein the computer readable storage medium stores a large batch comparison test system, wherein the large batch comparison test system comprises:

Setting module for setting the rollback point of the large batch comparison test database;

a calculation module, configured to calculate the premium receivable according to the basic data in the large batch comparison test database, and obtain the first result data;

a rollback module, configured to perform rollback of the large batch comparison test database according to the set rollback point;

The calculation module is further configured to: after the new version code is deployed, calculate the premium receivable again to obtain the second result data;

a comparison module, configured to compare the first result data with the second result data to determine whether there is a difference;

An analysis module is configured to analyze the difference and determine whether it is caused by a program defect of the new version code.
The computer readable storage medium according to claim 15, wherein the large batch comparison test system further comprises:

a backup module, configured to import the first result data into another database for backup before performing the rollback of the large batch comparison test database; and, after obtaining the second result data, the first A result data is returned to the bulk comparison test database.
The computer readable storage medium of claim 16 wherein said high volume comparison test system further comprises an acquisition module, wherein:

The setting module is further configured to set a range and time for acquiring the basic data;

The obtaining module is configured to acquire the basic data into the large batch comparison test database according to the set range and time.
The computer readable storage medium according to claim 17, wherein the range of the acquisition base data is a specified due date range.
The computer readable storage medium according to claim 15, wherein after the rollback, the data state in the large batch comparison test database is restored to the state of the rollback point.
The computer readable storage medium according to any one of claims 16 to 18, characterized in that, after the rollback, the data state in the large batch comparison test database is restored to the state of the rollback point.