Pressure test flow configuration method and system, and pressure test method

By receiving the test time period, calculating the reference time period, collecting historical traffic, constructing building factors, and calculating the target traffic, the problem of simulating real traffic in traditional testing is solved, realizing efficient and flexible stress test traffic construction and improving work efficiency.

CN115774671BActive Publication Date: 2026-07-10PING AN BANK CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
PING AN BANK CO LTD
Filing Date
2022-12-02
Publication Date
2026-07-10

AI Technical Summary

Technical Problem

Traditional performance baseline regression testing struggles to simulate the dynamic changes in real-world traffic and future traffic patterns, resulting in complex and cumbersome analysis and configuration, requiring significant manpower and leading to low work efficiency.

Method used

By receiving the test period, calculating the reference period, collecting historical traffic, constructing the construction factor, and calculating the target traffic based on the historical traffic and the construction factor, a more realistic stress test traffic is constructed.

Benefits of technology

The target traffic was optimized to be closer to reality, reducing human intervention, improving work efficiency, and enabling performance testing in unmanned scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115774671B_ABST
    Figure CN115774671B_ABST
Patent Text Reader

Abstract

The application provides a pressure test flow construction method for pressure testing of bank software, comprising the following steps: receiving a test time period, the test time period comprising a plurality of test dates; calculating a reference time period according to the test time period, the reference time period comprising a plurality of reference dates, and each reference date corresponding to a test date; collecting flow of the bank software on each reference date in the reference time period as historical flow; constructing a construction factor; and calculating target flow of the test date according to the historical flow and the construction factor, the pressure test flow comprising target flow of all test dates. In addition, the application also provides a pressure test flow construction system, a computer device and a pressure test method. The pressure test flow construction method provided by the application can efficiently construct pressure test flow closer to reality.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of financial technology, and in particular to a stress test flow construction method and system, a stress test method, and a computer device. Background Technology

[0002] Bank system upgrades involve periodic version iterations, each requiring performance baseline regression testing. Traditional performance baseline regression testing typically involves setting a fixed traffic level or a single, incrementally increasing traffic pattern for load testing. However, the load-bearing traffic pattern often differs significantly from real-world traffic patterns. Simulating realistic system performance scenarios often requires substantial manpower for analysis and frequent configuration adjustments. Furthermore, it's usually difficult to accurately simulate the dynamic changes in online traffic and future traffic patterns. Therefore, traditional analysis and configuration methods are complex, cumbersome, require significant manpower, and have low efficiency, making them difficult to improve. Summary of the Invention

[0003] In view of this, it is necessary to provide a method and system for constructing pressure test flow and a pressure testing method that can efficiently construct a pressure test flow that is closer to the real one.

[0004] In a first aspect, embodiments of this application provide a method for constructing stress test traffic, wherein the stress test traffic is used to perform stress tests on banking software, and the method for constructing stress test traffic includes:

[0005] Receive a test period, wherein the test period includes several test dates;

[0006] A reference time period is calculated based on the test time period, wherein the reference time period includes several reference dates, and the reference dates correspond one-to-one with the test dates;

[0007] The traffic of the banking software on each reference date within the reference time period is collected as historical traffic;

[0008] Constructing factors; and

[0009] The target flow for the test date is calculated based on the historical flow and the constructive factor, wherein the stress test flow includes the target flow for all test dates.

[0010] Secondly, embodiments of this application provide a computer device, the computer device comprising:

[0011] Memory, used to store program instructions; and

[0012] A processor for executing the program instructions to implement the stress test flow construction method as described above.

[0013] Thirdly, embodiments of this application provide a stress test flow rate construction system, the stress test flow rate construction system comprising:

[0014] A receiving module is used to receive a test time period, wherein the test time period includes several test dates;

[0015] The first calculation module is used to calculate a reference time period based on the test time period, wherein the reference time period includes a number of reference dates, and the reference dates correspond one-to-one with the test dates;

[0016] The data acquisition module is used to collect the traffic of the banking software on each reference date within the reference time period as historical traffic.

[0017] Modules for building constructs; and

[0018] The second calculation module is used to calculate the target traffic for the test date based on the historical traffic and the constructing factor, wherein the stress test traffic includes the target traffic for all test dates, and the stress test traffic is used to stress test the bank software.

[0019] Fourthly, embodiments of this application provide a pressure testing method, the pressure testing method comprising:

[0020] Receive stress test flow, wherein the stress test flow is constructed by the stress test flow construction method described above; and

[0021] The target version of the bank's software is stress-tested based on the stress test traffic.

[0022] The aforementioned stress test traffic construction method and system, along with the stress testing method, combine online process data collection to construct simulated stress test traffic. A reference time period is calculated based on the test time period, and historical traffic within that reference time period is used as the base traffic. Adjustments are made according to construction factors to obtain the target traffic for the test time period. This method of constructing stress test traffic based on online traffic collection optimizes the target traffic, making it closer to real-world conditions. Furthermore, the process of constructing stress test traffic can meet the performance testing requirements of unmanned scenarios, making the stress test traffic construction method more intelligent and flexible, while reducing human intervention and significantly improving work efficiency. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0024] Figure 1 A flowchart illustrating the stress test flow rate construction method provided in this application embodiment.

[0025] Figure 2 This is a first sub-flowchart of the stress test flow construction method provided in the embodiments of this application.

[0026] Figure 3 This is a second sub-flowchart of the stress test flow construction method provided in the embodiments of this application.

[0027] Figure 4 The third sub-flowchart of the stress test flow construction method provided in the embodiments of this application.

[0028] Figure 5 This is a schematic diagram illustrating an application scenario for the stress test flow rate construction method provided in the embodiments of this application.

[0029] Figure 6 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of this application.

[0030] Figure 7 A schematic diagram of the internal structure of the pressure test flow construction system provided in the embodiments of this application.

[0031] Figure 8 A flowchart of the pressure testing method provided in the embodiments of this application.

[0032] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0034] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar planned objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data are interchangeable where appropriate; in other words, the described embodiments are implemented according to a sequence other than that illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, may also include other content; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0035] It should be noted that the use of terms such as "first" and "second" in this application is for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first" and "second" may explicitly or implicitly include one or more of that feature. Furthermore, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0036] Please refer to the following: Figure 1 and Figure 5 , Figure 1 This is a flowchart of the stress test flow rate construction method provided in the embodiments of this application. Figure 5 This diagram illustrates an application scenario of the stress test traffic construction method provided in this embodiment. The stress test traffic construction method is applied in the fintech field to construct stress test traffic. The constructed stress test traffic can be used to perform stress tests on a bank software that is about to release a new version. The bank software refers to software related to the banking system. Figure 5 Taking the illustrated application scenario as an example, the platform 30 and the backend server 40 are connected for communication. In this embodiment, the backend server 40 runs banking software. The related functions of the platform 30 and the backend server 40 can be implemented by a single device, multiple devices working together, or one or more functional modules within a single device; no specific limitations are made here. It is understood that the aforementioned functions can be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0037] The method for constructing the flow rate for stress testing includes the following steps.

[0038] Step S102: Receive the test time period.

[0039] The administrator of platform 30 can input a test time period according to actual testing needs, and platform 30 receives the test time period. In this embodiment, the test time period includes several test dates, each including a test start date and a test end date. The test start date is the release date of the new version of the bank software, and the test end date is the release date of the next new version of the bank software. It can be understood that the test time period is the runtime of the upcoming new version.

[0040] For example, if the release date of a new version of a bank's software is August 18, 2022, and the release date of the next new version is September 8, 2022, then the test will start on August 18, 2022, and end on September 8, 2022. Accordingly, the test period will be from August 18, 2022, to September 8, 2022.

[0041] In some feasible embodiments, the administrator can maintain the annual version plan of the bank software on the construction platform 30, that is, set the release dates of all versions of the bank software for the year in advance, thereby generating several construction tasks on the construction platform 30, each construction task including a testing period. The construction platform 30 can automatically trigger and execute the construction tasks according to the current date.

[0042] Step S104: Calculate the reference time period based on the test time period.

[0043] The platform 30 calculates a reference time period based on the test time period. In this embodiment, the reference time period includes several reference dates, each with a reference start date and a reference end date. Each reference date corresponds one-to-one with a test date.

[0044] The specific process of calculating the reference time period based on the test time period will be described in detail below.

[0045] Step S106: Collect the traffic of the banking software on each reference date within the reference time period as historical traffic.

[0046] After calculating the reference time period, platform 30 collects the traffic of the banking software within the reference time period from backend server 40 as historical traffic. Specifically, platform 30 collects the traffic for each reference date within the reference time period as historical traffic. It can be understood that regardless of the version of the banking software running within the reference time period, only the traffic corresponding to the reference time period needs to be collected as historical traffic. Accordingly, historical traffic represents real traffic.

[0047] After calculating the reference time period, the platform 30 can first determine whether the reference start date of the reference time period is earlier than the current date. If the reference start date is earlier than the current date, the platform 30 can wait until the current date is the same as the reference start date before starting to collect historical traffic.

[0048] In some feasible embodiments, to prevent the reference start date from being later than the current date, i.e., having already passed the reference start date, the construction platform 30 can collect and record daily traffic during the operation of the banking software and store it in a database. Once the reference time period is calculated, the construction platform 30 can directly retrieve the traffic for the corresponding date from the database as historical traffic.

[0049] Among them, the construction platform 30 can collect historical traffic from the backend server 40 through the performance platform tool corona.

[0050] In other feasible embodiments, the construction platform 30 can also generate periodic trend charts of the collected historical traffic for administrators to view.

[0051] Step S108: Construct the building factors.

[0052] Platform 30 constructs construction factors based on the specific business situation and operating environment of the bank software.

[0053] The specific process of constructing the building factors will be described in detail below.

[0054] Step S110: Calculate the target flow for the test date based on historical flow and construction factors.

[0055] The platform 30 calculates the target traffic for the test dates based on historical traffic and construction factors. In this embodiment, the stress test traffic includes the target traffic for all test dates. That is, the target traffic for all test dates within the test period constitutes the stress test traffic.

[0056] The specific process of calculating the target traffic for the test date based on historical traffic and construct factors will be described in detail below.

[0057] In the above embodiments, online process data is collected to construct simulated stress test traffic. A reference time period is calculated based on the test time period, and historical traffic within the reference time period is used as the base traffic. Adjustments are made according to the construction factors to obtain the target traffic for the test time period. This method of constructing stress test traffic based on online traffic collection optimizes the target traffic, making it closer to reality. Furthermore, the process of constructing stress test traffic can meet the performance testing requirements of unmanned scenarios, making the stress test traffic construction method more intelligent and flexible, while reducing human intervention and significantly improving work efficiency.

[0058] Please refer to the following: Figure 2 This is the first sub-flowchart of the pressure test flow rate construction method provided in the embodiments of this application. Step S104 specifically includes the following steps.

[0059] Step S202: Receive the acquisition cycle.

[0060] The administrator of platform 30 can input the data collection period according to actual testing needs, and platform 30 will receive the data collection period. The data collection period includes, but is not limited to, yearly or monthly periods. Specifically, when the data collection period is yearly, platform 30 collects the traffic from the previous year as historical traffic, i.e., platform 30 collects year-on-year traffic; when the data collection period is monthly, platform 30 collects the traffic from the previous month as historical traffic, i.e., platform 30 collects month-on-month traffic.

[0061] Step S204: Calculate the intermediate start date based on the data collection period and the test start date.

[0062] The construction platform 30 calculates the intermediate start date based on the received collection cycle and the test start date of the test time period. In this embodiment, the construction platform 30 uses the date obtained by subtracting one collection cycle from the test start date as the intermediate start date.

[0063] For example, if the data collection period is one year and the test starts on August 18, 2022, then the intermediate start date calculated one year backward would be August 18, 2021.

[0064] Step S206: Determine whether the week number of the intermediate start date is the same as the week number of the test start date.

[0065] Since traffic on weekdays and weekends can differ significantly, platform 30 needs to determine whether the week number of the intermediate start date is the same as the week number of the test start date.

[0066] In this embodiment, the construction platform 30 first calculates the week number of the intermediate start date and the week number of the test start date. Specifically, the construction platform 30 can calculate the week number according to the Zeller formula.

[0067] The Zeller formula is: w = (y + [y / 4] + [c / 4] - 2c + [26(m+1) / 10] + d - 1) MOD7. Where w represents the weekday; c represents the century; y represents the year; m represents the month; d represents the day; square brackets [·] indicate that only the integer part of the number is taken; MOD7 indicates taking the modulus of 7. Accordingly, the value of w ranges from 0 to 6: when w = 0, it represents Sunday; when w = 1, it represents Monday; when w = 2, it represents Tuesday; when w = 3, it represents Wednesday; when w = 4, it represents Thursday; when w = 5, it represents Friday; and when w = 6, it represents Saturday.

[0068] In this embodiment, the year y is represented by only the last two digits. The month m is greater than or equal to 3 and less than or equal to 14, where m=3 represents March, m=4 represents April, and so on, m=13 represents January of the following year, m=14 represents February of the following year.

[0069] By substituting the century, year, month, and day of the test start date and intermediate start date into the Zeyler formula, we can obtain the week number of the test start date and the week number of the intermediate start date.

[0070] If the week number of the intermediate start date is the same as the week number of the test start date, proceed to step S208; if the week number of the intermediate start date is different from the week number of the test start date, proceed to step S210.

[0071] Step S208: Use the intermediate start date as the reference start date.

[0072] When the week number of the intermediate start date is the same as the week number of the test start date, the construction platform 30 can directly use the intermediate start date as the reference start date.

[0073] Step S210: Use a date that is in the same week as the intermediate start date and has the same week number as the test start date as the reference start date.

[0074] When the weekday number of the intermediate start date is different from the weekday number of the test start date, the construction platform 30 will use a date that shares the same weekday as the intermediate start date and has the same weekday number as the test start date as the reference start date. In other words, the weekday number of the reference start date must be the same as the weekday number of the test start date.

[0075] For example, the weekday number of the calculated test start date, August 18, 2022, is Thursday, and the weekday number of the intermediate start date, August 18, 2021, is Wednesday. Therefore, the weekday number of the intermediate start date is different from the weekday number of the test start date.

[0076] Since the intermediate starting date, August 18, 2021, falls on a Wednesday, the date that falls on the same Thursday as August 18, 2021, is August 19, 2021. Therefore, August 19, 2021, will be used as the reference starting date.

[0077] Step S212: Calculate the reference end date based on the reference start date and the test period.

[0078] The platform 30 calculates the reference end date based on the obtained reference start date and test time period. In this embodiment, the duration of the test time period is the same as the duration of the reference time period. That is, the number of test dates in the test time period is the same as the number of reference dates in the reference time period. Therefore, once the reference start date is obtained, the reference end date can be directly calculated based on the duration of the test time period.

[0079] For example, if the reference start date is August 19, 2021, which is one day later than the test start date of August 18, 2022, then the reference end date can be one day later than the test end date. Therefore, if the test end date is September 8, 2022, then the reference end date is September 9, 2021.

[0080] Understandably, when the week number of the intermediate start date is the same as the week number of the test start date, the dates of the reference period and the test period correspond perfectly. When the week number of the intermediate start date is different from the week number of the test start date, the dates of the reference period and the test period do not correspond perfectly, but are adjusted accordingly based on the week number of the test start date.

[0081] In the above embodiments, the year-on-year flow simulation method is used. When the collection period is annual, the stress test flow is constructed using the annual year-on-year flow method; when the collection period is monthly, the stress test flow is constructed using the monthly year-on-year flow method. Both year-on-year and month-on-month flow simulation methods are supported.

[0082] Please refer to the following: Figure 3 This is the second sub-flowchart of the pressure test flow rate construction method provided in the embodiments of this application. Step S108 specifically includes the following steps.

[0083] Step S302: Receive the business indicator volume and annual business volume from the bank's software.

[0084] The administrator of platform 30 can input the corresponding business indicators and annual business volume of the banking software according to actual business needs, and platform 30 receives the business indicators and annual business volume. The business indicators include annual indicators and monthly indicators. It can be understood that when the administrator inputs a collection period of years, the annual indicators can be entered accordingly; when the administrator inputs a collection period of months, the monthly indicators can be entered accordingly.

[0085] Step S304: Calculate the conversion factor based on the business indicator volume and annual business volume.

[0086] Platform 30 calculates conversion factors based on business indicators and annual business volume.

[0087] In this embodiment, based on online data analysis, it is known that the monthly transaction volume trend chart for each month of the previous year is similar to the corresponding monthly trend chart for the current year. Therefore, the target flow can be based on historical flow over a reference time period, taking into account both business metrics and annual business volume.

[0088] The conversion factor is calculated based on the business target volume and the annual business volume. Specifically, the ratio of the business target volume to the annual business volume is used as the conversion factor.

[0089] In this embodiment, the platform 30 calculates the conversion factor according to the first formula. Specifically, the first formula is: g = T / C. Wherein, g represents the conversion factor; T represents the business indicator quantity; and C represents the annual business volume.

[0090] Step S306, Number of receiving machines.

[0091] The administrator of platform 30 can input the number of machines based on the actual operating environment of the banking software, and platform 30 receives the number of machines. It can be understood that the number of machines refers to the number of machines in the environment running the banking software.

[0092] Step S308: Calculate and adjust parameters based on the number of machines.

[0093] Platform 30 calculates and adjusts parameters based on the number of machines received. These adjustment parameters can be calculated based on the relationship between the number of machines and software operation in existing stress tests, and are not limited here.

[0094] In some feasible embodiments, the adjustment parameters can also be calculated based on the number of machines and other factors that may affect the operation of the banking software, which are not limited here.

[0095] Step S310: Calculate the product of the conversion factor and the adjustment parameter as the construction factor.

[0096] In the above embodiments, the performance baseline task established by the user only needs to be modified and adjusted according to the environment, such as the number of machines.

[0097] Please refer to the following: Figure 4 This is the third sub-flowchart of the pressure test flow rate construction method provided in the embodiments of this application. Step S110 specifically includes the following steps.

[0098] Step S402: Determine whether the test date has a special mark.

[0099] The platform 30 determines whether each test date within the test period has a special marker. In this embodiment, when inputting the test period, the administrator can add special markers for certain special test dates based on actual business needs. These special markers are used to mark activity days or other special days of the banking software. Considering that activity days of the banking software may bring additional traffic, the administrator can mark the test dates corresponding to activity days or other special days.

[0100] If the test date has a special mark, proceed to step S404; if the test date does not have a special mark, proceed to step S408.

[0101] Step S404: Match a reference date within the reference time period as the target date.

[0102] When the test date has a special marker, the construction platform 30 matches a reference date within the reference time period as the target date. In this embodiment, the target date may or may not be a reference date that corresponds one-to-one with the test date. For example, if the activity day is a fixed day of the month or year, such as the 8th of each month or June 20th of each year, then one day of the same date within the reference time period is used as the target date. That is, if the test date August 20, 2022 has a special marker, then the corresponding target date is August 20, 2021. In other words, when the dates in the reference time period and the dates in the test time period are completely identical, the target date is a reference date that corresponds one-to-one with the test date; when the dates in the reference time period and the dates in the test time period are not completely identical, the target date is not a reference date that corresponds one-to-one with the test date.

[0103] Step S406: Calculate the target flow for the test date based on the historical flow and construction factor for the target date.

[0104] The platform 30 calculates the target traffic for the corresponding test date based on the historical traffic and construction factors for the target date.

[0105] Calculating the target flow for the test date based on the historical flow and construction factor of the target date specifically includes: calculating the product of the historical flow and the construction factor as the target flow.

[0106] Step S408: Calculate the target flow for the test date based on the historical flow of the reference date and the construction factor.

[0107] When the test date is not specially marked, the construction platform 30 calculates the target traffic for the corresponding test date based on the historical traffic and construction factor of the reference date.

[0108] Calculating the target flow for the test date based on the historical flow and construction factor of the reference date specifically includes: calculating the product of the historical flow and the construction factor as the target flow.

[0109] In this embodiment, the construction platform 30 calculates the target traffic according to the second formula. Specifically, the second formula is Tf = Hf * g * e. Wherein, Tf represents the target traffic; Hf represents the historical traffic; g * e represents the construction factor; g represents the conversion factor; and e represents the adjustment parameter.

[0110] In the above embodiments, the collected reference traffic is used as a daily unit to calculate the target traffic based on the constructed factors. Specifically, special days within the test period are taken into account, and the target traffic is calculated based on the reference traffic of the matching reference dates, making the calculated target traffic more accurate.

[0111] Please refer to the following: Figure 6 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of this application. The computer device 10 includes a memory 11 and a processor 12. The memory 11 is used to store program instructions, and the processor 12 is used to execute the program instructions to implement the stress test flow construction method described above.

[0112] In some embodiments, the processor 12 may be a central processing unit (CPU), controller, microcontroller, microprocessor or other data processing chip, used to run program instructions stored in the memory 11.

[0113] The memory 11 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 11 may be an internal storage unit of a computer device, such as a hard disk. In other embodiments, the memory 11 may be an external storage device of a computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Furthermore, the memory 11 may include both internal and external storage units of the computer device. The memory 11 can be used not only to store application software and various types of data installed on the computer device, such as code implementing a stress test flow construction method, but also to temporarily store data that has been output or will be output.

[0114] Please refer to the following: Figure 7 This is a schematic diagram of the internal structure of the stress test traffic construction system provided in this application embodiment. The stress test traffic construction system 20 is used to construct stress test traffic, which is used to stress test bank software. The stress test traffic construction system 20 includes a receiving module 21, a first calculation module 22, a data acquisition module 23, a construction module 24, and a second calculation module 25.

[0115] The receiving module 21 is used to receive the test time period.

[0116] The administrator of the stress test traffic construction system 20 can input a test time period according to actual testing needs, and the receiving module 21 receives the test time period. In this embodiment, the test time period includes several test dates, including a test start date and a test end date. The test start date is the release date of the new version of the bank software, and the test end date is the release date of the next new version of the bank software. It can be understood that the test time period is the runtime of the upcoming new version.

[0117] For example, if the release date of a new version of a bank's software is August 18, 2022, and the release date of the next new version is September 8, 2022, then the test will start on August 18, 2022, and end on September 8, 2022. Accordingly, the test period will be from August 18, 2022, to September 8, 2022.

[0118] In some feasible embodiments, the administrator can maintain the annual version schedule of the bank software in the stress test traffic construction system 20. That is, the release dates of all versions of the bank software for the year are set in advance, thereby generating several construction tasks in the stress test traffic construction system 20, each construction task including a test period. The stress test traffic construction system 20 can automatically trigger and execute the construction tasks according to the current date.

[0119] The first calculation module 22 is used to calculate the reference time period based on the test time period.

[0120] The first calculation module 22 calculates a reference time period based on the test time period. In this embodiment, the reference time period includes several reference dates, each with a reference start date and a reference end date. Each reference date corresponds one-to-one with a test date.

[0121] The data collection module 23 is used to collect the traffic of the banking software on each reference date within a reference time period as historical traffic.

[0122] After the first calculation module 22 calculates the reference time period, the acquisition module 23 collects the traffic of the banking software within the reference time period as historical traffic. Specifically, the acquisition module 23 collects the traffic for each reference date within the reference time period as historical traffic. It can be understood that regardless of the version of the banking software running within the reference time period, only the traffic corresponding to the reference time period needs to be collected as historical traffic. Accordingly, historical traffic represents real traffic.

[0123] After the first calculation module 22 calculates the reference time period, the collection module 23 can first determine whether the reference start date of the reference time period is earlier than the current date. If the reference start date is earlier than the current date, the collection module 23 can wait until the current date is the same as the reference start date before starting to collect historical traffic.

[0124] In some feasible embodiments, to prevent the reference start date from being later than the current date (i.e., past the reference start date), the data collection module 23 can collect and record the daily data traffic during the operation of the banking software and store it in the database. After calculating the reference time period, the data collection module 23 can directly retrieve the data traffic for the corresponding date from the database as historical data.

[0125] Among them, the acquisition module 23 can collect historical traffic through the performance platform tool Corona.

[0126] In other feasible embodiments, the acquisition module 23 can also generate a periodic trend chart of the acquired historical traffic for administrators to view.

[0127] Module 24 is used to construct the building factors.

[0128] Module 24 constructs building factors based on the specific business situation and operating environment of the bank software.

[0129] The second calculation module 25 is used to calculate the target flow for the test date based on historical flow and construction factors.

[0130] The second calculation module 25 calculates the target flow for the test date based on historical flow and construction factors. In this embodiment, the stress test flow includes the target flow for all test dates. That is, the target flow for all test dates within the test period constitutes the stress test flow.

[0131] Please refer to the following: Figure 8 This is a flowchart of a stress testing method provided in an embodiment of this application. The stress testing method is used to perform stress tests on a bank software that is about to release a new version. The stress testing method specifically includes the following steps.

[0132] Step S802: Receive stress test traffic.

[0133] In this embodiment, the pressure test flow rate is constructed using the pressure test flow rate construction method described above.

[0134] Step S804: Perform stress testing on the target version of the bank software based on the stress test traffic.

[0135] In this embodiment, stress testing the target version of the banking software based on the stress test traffic specifically includes: sequentially executing the target traffic for each test date in the stress test traffic on the target version of the banking software. Specifically, the tests are performed in chronological order of the test dates within the test time period.

[0136] The execution time for the target traffic is the same for each test date. That is, a preset time can be set to execute the target traffic for one test date within that preset time. For example, the preset time could be 10 minutes. The specific value of the preset time can be set according to the actual testing situation and is not limited here.

[0137] In the above embodiments, the stress test performance execution scenario can simulate an online day, i.e. a test date scenario, based on a preset time, and complete the test by continuously executing the target traffic of all test dates within the test period.

[0138] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

[0139] The above-listed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A method for constructing flow rate for pressure testing, characterized in that, The stress test traffic is used to stress test the banking software, and the stress test traffic construction method includes: The test period is received, wherein the test period includes several test dates; the test dates include a test start date and a test end date, wherein the test start date is the release date of the new version of the bank software, and the test end date is the release date of the next new version of the bank software; A reference time period is calculated based on the test time period, wherein the reference time period includes several reference dates, each corresponding one-to-one with the test date; the reference dates include a reference start date and a reference end date. The calculation of the reference time period based on the test time period specifically includes: Receive acquisition cycle; Calculate the intermediate start date based on the data collection period and the test start date; Determine whether the week number of the intermediate start date is the same as the week number of the test start date; When the week number of the intermediate start date is the same as the week number of the test start date, the intermediate start date is used as the reference start date; When the weekday number of the intermediate start date is different from the weekday number of the test start date, the date that shares the same weekday as the intermediate start date and has the same weekday number as the test start date will be used as the reference start date; and Calculate the reference end date based on the reference start date and the test period; The traffic of the banking software on each reference date within the reference time period is collected as historical traffic; Constructing factors; and The target flow for the test date is calculated based on the historical flow and the constructive factor, wherein the stress test flow includes the target flow for all test dates.

2. The pressure test flow rate construction method as described in claim 1, characterized in that, The construction of building factors specifically includes: Receive the business performance indicators and annual business volume of the bank software; Calculate the conversion factor based on the business indicator volume and the annual business volume; Number of receiving machines; Calculate and adjust parameters based on the number of machines; and The product of the conversion factor and the adjustment parameter is calculated as the construction factor.

3. The pressure test flow rate construction method as described in claim 2, characterized in that, The calculation of the conversion factor based on the aforementioned business indicator volume and the aforementioned annual business volume specifically includes: The ratio of the business indicator quantity to the annual business volume is calculated as the conversion factor.

4. The pressure test flow rate construction method as described in claim 1, characterized in that, Calculating the target traffic for the test date based on the historical traffic and the constructive factor specifically includes: Determine whether the test date has a special mark; When the test date is marked with a special symbol, a reference date is matched within the reference time period as the target date; Calculate the target traffic for the test date based on the historical traffic for the target date and the constructive factor; and When the test date is not specially marked, the target traffic for the test date is calculated based on the historical traffic of the reference date and the construct factor.

5. The pressure test flow rate construction method as described in claim 4, characterized in that, Calculating the target traffic for the test date based on the historical traffic of the target date or the reference date and the constructive factor specifically includes: The product of the historical flow and the construction factor is calculated as the target flow.

6. A computer device, characterized in that, The computer device includes: Memory, used to store program instructions; and A processor for executing the program instructions to implement the stress test flow construction method as described in any one of claims 1 to 5.

7. A pressure testing flow rate construction system, characterized in that, The pressure test flow construction system includes: A receiving module is used to receive a test time period, wherein the test time period includes several test dates; the test dates include a test start date and a test end date, wherein the test start date is the release date of a new version of the bank software, and the test end date is the release date of the next new version of the bank software; The first calculation module is used to calculate a reference time period based on the test time period, wherein the reference time period includes a plurality of reference dates, each of which corresponds one-to-one with the test date; the reference dates include a reference start date and a reference end date, and the calculation of the reference time period based on the test time period specifically includes: Receive acquisition cycle; Calculate the intermediate start date based on the data collection period and the test start date; Determine whether the week number of the intermediate start date is the same as the week number of the test start date; When the week number of the intermediate start date is the same as the week number of the test start date, the intermediate start date is used as the reference start date; When the weekday number of the intermediate start date is different from the weekday number of the test start date, the date that shares the same weekday as the intermediate start date and has the same weekday number as the test start date will be used as the reference start date; and Calculate the reference end date based on the reference start date and the test period; The data acquisition module is used to collect the traffic of the banking software on each reference date within the reference time period as historical traffic. Modules for building constructs; and The second calculation module is used to calculate the target traffic for the test date based on the historical traffic and the constructing factor, wherein the stress test traffic includes the target traffic for all test dates, and the stress test traffic is used to stress test the bank software.

8. A pressure testing method, characterized in that, The pressure testing method includes: Receive stress test flow, wherein the stress test flow is constructed by the stress test flow construction method as described in any one of claims 1 to 5; and The target version of the bank's software is stress-tested based on the stress test traffic.

9. The pressure testing method as described in claim 8, characterized in that, The stress test on the target version of the banking software based on the stress test traffic specifically includes: The target version of the bank software is executed sequentially for each test date of the stress test traffic, wherein the execution time of the target traffic for each test date is the same.