CN111813694A - Test method, test device, electronic device and readable storage medium - Google Patents

Abstract

The present disclosure provides a test method, a test device, an electronic device, and a readable storage medium. The testing method includes: displaying a requirement collection view, wherein the requirement collection view includes options for different types of performance testing requirements; determining the type of target performance testing requirement selected by the user in the requirement collection view Eigenvalues to be input and scalars of elements to be input; according to the eigenvalue information and element scalar information input by the user for the eigenvalues to be input and the scalars of elements to be input, a performance test case is generated; and the performance test case is executed to meet the target performance test requirements.

Description

Test method, test device, electronic device and readable storage medium

technical field

The present disclosure relates to the field of software performance testing, and more particularly, to a performance testing method, a performance testing device, an electronic device, and a computer-readable storage medium.

Background technique

With the rapid development of Internet technology and e-commerce, customers' experience of software performance is getting higher and higher, and the demand for performance testing of software systems in the financial industry is also increasing. In the process of testing software systems in the financial industry, the requirements for rapid delivery such as agility and iteration, as well as the growing system scale, cannot fully cover the testing requirements. Performance testing must screen and prioritize requirements.

During the process of realizing the concept of the present disclosure, the inventor found that the related art has at least the following problems: the testing efficiency of using the related technology to test the performance of the system is low, and it is time-consuming and labor-intensive.

SUMMARY OF THE INVENTION

In view of this, the present disclosure provides a performance testing method, a performance testing apparatus, an electronic device, and a computer-readable storage medium.

One aspect of the present disclosure provides a testing method, which may include: displaying a requirements collection view, wherein the requirements collection view includes options for different types of performance testing requirements; Type, determine the eigenvalues to be input and the scalars of the elements to be input for the target performance test requirements; generate performance test cases according to the eigenvalue information and element scalar information input by the user for the eigenvalues to be input and the scalars of elements to be input; and execute the performance test cases , to achieve the target performance test requirements.

According to an embodiment of the present disclosure, wherein, according to the type of the target performance test requirement selected by the user in the requirement collection view, determining the to-be-input feature value and the to-be-input element scalar of the target performance test requirement includes: according to the type of the target performance test requirement, Extract feature values to be input and element scalars to be input associated with the type of target performance test requirements from the element warehouse, wherein the element warehouse includes test elements corresponding to different types of performance test requirements, wherein the test elements include feature values features and feature scalar features; and generate a page input that includes the feature values to be input and the feature scalars to be input.

According to an embodiment of the present disclosure, the above-mentioned performance testing method further includes: before generating a performance test case according to the eigenvalue information and element scalar information input by the user for the eigenvalue to be input and the element scalar information to be input The test requirements are qualitatively analyzed, and the qualitative analysis results are obtained; and when the qualitative analysis results indicate that the target performance test requirements are allowed to be executed, a performance test case is generated.

According to an embodiment of the present disclosure, the above performance testing method further includes: when the qualitative analysis result indicates that the target performance testing requirement is allowed to be executed, quantitatively analyzing the target performance testing requirement according to the element scalar information to obtain a quantitative analysis result; and according to the quantitative analysis The analysis result calculates the risk score of the target performance test requirement; and determines the execution order of the performance test cases of the target performance test requirement according to the risk score.

According to an embodiment of the present disclosure, performing quantitative analysis on the target performance test requirement according to the element scalar information, and obtaining a quantitative analysis result includes: comparing and analyzing the element scalar information with the actual production operation data in the production operation database to determine the element scalar Is the information reasonable.

According to an embodiment of the present disclosure, the above performance testing method further includes: after executing the performance test case, feeding back the execution result to the user.

According to an embodiment of the present disclosure, displaying the requirement collection view includes: acquiring type information of the logged-in user; and displaying the requirement collection view when it is determined according to the type information of the logged-in user that the logged-in user is a performance test demander.

Another aspect of the present disclosure provides a testing device, which may include: a presentation module for displaying a requirement collection view, wherein the requirement collection view includes options for different types of performance testing requirements; a first determination module for The type of the target performance test requirement selected by the user in the requirement collection view determines the to-be-inputted eigenvalues and to-be-input element scalars of the target performance test requirement; the generation module is used to determine the to-be-inputted eigenvalues and to-be-inputted element scalars according to the user input feature value information and element scalar information to generate performance test cases; and an execution module for executing performance test cases to achieve target performance test requirements.

According to an embodiment of the present disclosure, the first determination module includes: an extraction unit, configured to extract, from the element repository, the feature values to be input and the elements to be input associated with the type of the target performance test requirement from the element repository scalar, wherein the element warehouse includes test elements corresponding to different types of performance test requirements, wherein the test elements include eigenvalue elements and element scalar elements; and a generating unit is used to generate scalar elements including the eigenvalues to be input and the elements to be input page entry.

According to an embodiment of the present disclosure, the above-mentioned performance testing apparatus further includes: a qualitative analysis module, configured to, before generating a performance test case according to the eigenvalue information and element scalar information input by the user for the eigenvalues to be input and the scalar elements of the elements to be input, analyze the The value information qualitatively analyzes the target performance test requirement, and obtains a qualitative analysis result; and the generating module is used to generate a performance test case when the qualitative analysis result indicates that the target performance test requirement is allowed to be executed.

According to an embodiment of the present disclosure, the above performance testing device further includes: a quantitative analysis module, configured to perform quantitative analysis on the target performance test requirement according to the element scalar information under the condition that the qualitative analysis result indicates that the target performance test requirement is allowed to be executed, and obtain a quantitative analysis and a calculation module for calculating the risk score of the target performance test requirement according to the quantitative analysis result; and a second determination module for determining the execution order of the performance test cases of the target performance test requirement according to the risk score.

According to an embodiment of the present disclosure, the quantitative analysis module is configured to: compare and analyze the element scalar information with the actual production operation data in the production operation database to determine whether the element scalar information is reasonable.

According to an embodiment of the present disclosure, the above performance testing apparatus further includes: a feedback module, configured to feed back the execution result to the user after executing the performance test case.

According to an embodiment of the present disclosure, the presentation module includes: an acquisition unit for acquiring type information of the logged-in user; and a presentation unit for displaying the logged-in user when it is determined according to the type information of the logged-in user that the logged-in user is a performance test demander Requirements Gathering View.

Another aspect of the present disclosure provides an electronic device comprising: one or more processors; a memory for storing one or more instructions, wherein the one or more instructions when executed by the one or more processors , so that one or more processors implement the above method.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed, are used to implement the above method.

Another aspect of the present disclosure provides a computer program comprising computer-executable instructions, when executed, for implementing the method as above.

Through the embodiments of the present disclosure, according to the type of the target performance test requirement selected by the user in the requirement collection view, the to-be-input feature value and the to-be-input element scalar of the target performance test requirement are determined; The eigenvalue information and element scalar information of scalar input are used to generate performance test cases; and performance test cases are executed to achieve the target performance test requirements, thereby unifying the channels and methods of performance test requirements and saving communication costs caused by artificial collection requirements. Save manpower; solve the leakage and leakage of requirements caused by different personnel standards, and at the same time, the reasons for the requester's permission and return are more clear and explainable, which is convenient for all parties to synchronize information and avoid misunderstanding; test cases and test requirements are strong Association, provide unified progress management, problem management, risk management, and provide a starting point for managers.

Description of drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically shows an exemplary system architecture to which a performance testing method, testing apparatus, electronic device and readable storage medium of the present disclosure can be applied;

FIG. 2 schematically shows a flowchart of a testing method according to an embodiment of the present disclosure;

3 schematically shows a flow chart of determining the characteristic value to be inputted and the element scalar to be input of the target performance test requirement according to the type of target performance test requirement selected by the user in the requirement collection view according to an embodiment of the present disclosure;

FIG. 4 schematically shows a flowchart of a testing method according to another embodiment of the present disclosure;

FIG. 5 schematically shows a flow chart in the case that the qualitative analysis result indicates that the target performance test requirement is allowed to be performed according to an embodiment of the present disclosure;

FIG. 6 schematically shows a flow chart showing a demand collection view according to an embodiment of the present disclosure;

FIG. 7 schematically shows a flowchart of a performance testing method according to another embodiment of the present disclosure;

FIG. 8 schematically shows a structural diagram of a testing device according to an embodiment of the present disclosure;

FIG. 9 schematically shows a structural diagram of a testing device according to another embodiment of the present disclosure; and

Figure 10 schematically illustrates a block diagram of a computer system suitable for implementing the methods described above, according to an embodiment of the present disclosure.

Detailed ways

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood, however, that these descriptions are exemplary only, and are not intended to limit the scope of the present disclosure. In the following detailed description, for convenience of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It will be apparent, however, that one or more embodiments may be practiced without these specific details. Also, in the following description, descriptions of well-known structures and techniques are omitted to avoid unnecessarily obscuring the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the present disclosure. The terms "comprising", "comprising" and the like as used herein indicate the presence of stated features, steps, operations and/or components, but do not preclude the presence or addition of one or more other features, steps, operations or components.

All terms (including technical and scientific terms) used herein have the meaning as commonly understood by one of ordinary skill in the art, unless otherwise defined. It should be noted that terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly rigid manner.

Where expressions like "at least one of A, B, and C, etc.," are used, they should generally be interpreted in accordance with the meaning of the expression as commonly understood by those skilled in the art (eg, "has A, B, and C") At least one of the "systems" shall include, but not be limited to, systems with A alone, B alone, C alone, A and B, A and C, B and C, and/or A, B, C, etc. ). Where expressions like "at least one of A, B, or C, etc.," are used, they should generally be interpreted in accordance with the meaning of the expression as commonly understood by those skilled in the art (eg, "has A, B, or C, etc." At least one of the "systems" shall include, but not be limited to, systems with A alone, B alone, C alone, A and B, A and C, B and C, and/or A, B, C, etc. ).

In the process of realizing the present disclosure, it is found that there are many sources of performance test requirements collection, and the characteristic values and elements are not uniform, which often requires multiple rounds of communication and confirmation between the demander and the tester, which is inefficient, wastes a lot of manpower, and is prone to information asymmetry. Situation; performance testing requirements are mostly the result of human discussions, lacking a quantifiable and interpretable decision-making process. The result of allowing performance test requirements is not convincing to the requester, and lacks quality control for the test manager; the requirements and test cases are independent of each other, and there is no relationship established. The information of the test administrator and the test administrator is not transparent.

The present disclosure provides a test method, a test device, an electronic device, and a readable storage medium. The testing method includes: displaying a requirement collection view, wherein the requirement collection view includes options for different types of performance testing requirements; determining the type of target performance testing requirement selected by the user in the requirement collection view Eigenvalues to be input and scalars of elements to be input; according to the eigenvalue information and element scalar information input by the user for the eigenvalues to be input and the scalars of elements to be input, a performance test case is generated; and the performance test case is executed to meet the target performance test requirements.

FIG. 1 schematically shows an exemplary system architecture 100 to which a performance testing method, testing apparatus, electronic device and readable storage medium of the present disclosure may be applied. It should be noted that FIG. 1 is only an example of a system architecture to which the embodiments of the present disclosure can be applied, so as to help those skilled in the art to understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used for other A device, system, environment or scene.

As shown in FIG. 1 , the system architecture 100 according to this embodiment may include terminal devices 101 , 102 , and 103 , a network 104 and a server 105 . The network 104 is a medium used to provide a communication link between the terminal devices 101 , 102 , 103 and the server 105 . The network 104 may include various connection types, such as wired and/or wireless communication links, and the like.

The user can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages and the like. Various communication client applications may be installed on the terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients and/or social platform software, etc. (just an example). ).

The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

The server 105 may be a server that provides various services, such as a background management server (just an example) that provides support for websites browsed by users using the terminal devices 101 , 102 , and 103 . The background management server can analyze and process the received user requests and other data, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

It should be noted that, the performance testing method provided by the embodiment of the present disclosure may generally be executed by the server 105 . Correspondingly, the performance testing apparatus provided by the embodiments of the present disclosure may generally be provided in the server 105 . The performance testing method provided by the embodiment of the present disclosure may also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101 , 102 , 103 and/or the server 105 . Correspondingly, the performance testing apparatus provided by the embodiments of the present disclosure may also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101 , 102 , 103 and/or the server 105 . Alternatively, the performance testing method provided by the embodiment of the present disclosure may also be executed by the terminal device 101 , 102 , or 103 , or may also be executed by other terminal device different from the terminal device 101 , 102 , or 103 . Correspondingly, the performance testing apparatus system provided by the embodiments of the present disclosure may also be set in the terminal equipment 101 , 102 , or 103 , or set in other terminal equipment different from the terminal equipment 101 , 102 , or 103 .

For example, the user stores the performance test requirement instance in any one of the terminal devices 101, 102, or 103 (for example, the terminal device 101, but not limited to) through page entry, file import, etc., and displays the requirement collection view, according to the user Select the type of the target performance test requirement in the requirement collection view, determine the feature value to be input and the element scalar to be input of the target performance test requirement, according to the feature value information and element scalar input by the user for the feature value to be input and the element scalar to be input information, generate performance test cases, and execute performance test cases to achieve target performance test requirements.

It should be understood that the numbers of terminal devices, networks and servers in FIG. 1 are merely illustrative. There can be any number of terminal devices, networks and servers according to implementation needs.

FIG. 2 schematically shows a flow chart of a testing method according to an embodiment of the present disclosure.

It should be noted that, unless it is clearly stated that the operations shown in the flowcharts in the embodiments of the present disclosure have a sequence of execution between different operations, or there is a sequence of execution of different operations in terms of technical implementation, otherwise, between multiple operations The order of execution can be in no particular order, and multiple operations can also be executed at the same time.

As shown in FIG. 2, the method includes operations S201-S204.

In operation S201, a requirement collection view is displayed, wherein the requirement collection view includes options for different types of performance testing requirements.

According to an embodiment of the present disclosure, the display requirement collection view may be an interface that the user can see after the user logs in to the system for the user to select different requirement types.

According to an embodiment of the present disclosure, the options for performance testing requirements may be different requirement types set for the testing requirements of different users. For example, it can be new features, seckill activities, system upgrades, etc.

In operation S202, according to the type of the target performance test requirement selected by the user in the requirement collection view, the to-be-input feature value and the to-be-input element scalar of the target performance test requirement are determined.

According to an embodiment of the present disclosure, the user may be, for example, a performance test demander.

According to the embodiments of the present disclosure, if the user is a performance test demander, the system can provide a relevant view of demand collection.

According to an embodiment of the present disclosure, the target performance test requirement is one or more test requirement types to be tested provided by the user, and the input of requirement elements is checked for validity.

According to an embodiment of the present disclosure, the characteristic value is an objective classification in the classification of performance testing requirements. For example, it can be whether it is a new online system, whether it is a customer system, transaction type, etc.

According to an embodiment of the present disclosure, the element scalar is a hierarchical classification of demand urgency in the performance test demand classification. For example, it can be system level, average daily transaction volume, number of users, etc.

In operation S203, a performance test case is generated according to the eigenvalue information and the element scalar information input by the user for the to-be-inputted eigenvalue and the to-be-input element scalar.

According to an embodiment of the present disclosure, a performance test case is a way for a user to input feature value information and element variable information into the system to generate a performance test requirement instance, convert performance test requirement elements into performance test case elements, and combine them into a performance test case. One way can be through page entry, or, through file import.

In operation S204, the performance test case is executed to achieve the target performance test requirement.

According to an embodiment of the present disclosure, performing a performance test case may associate a performance test requirement with a performance test instance through a performance test transformation parameter. Among them, the performance test conversion parameters include the requirement elements that are allowed to be executed and converted into performance test case elements through calculation. For example, it can be test time, response time, number of concurrent users, etc.

Through the embodiments of the present disclosure, according to the type of the target performance test requirement selected by the user in the requirement collection view, the to-be-input feature value and the to-be-input element scalar of the target performance test requirement are determined; The eigenvalue information and element scalar information of scalar input are used to generate performance test cases; and performance test cases are executed to achieve the target performance test requirements, thereby unifying the channels and methods of performance test requirements and saving communication costs caused by artificial collection requirements. Save manpower; solve the leakage and leakage of requirements caused by different personnel standards, and at the same time, the reasons for the requester's permission and return are more clear and explainable, which is convenient for all parties to synchronize information and avoid misunderstanding; test scenarios and test requirements Strong correlation, providing unified progress management, problem management, risk management, and providing a starting point for managers.

The method shown in FIG. 2 will be further described below with reference to FIG. 3 in conjunction with specific embodiments.

FIG. 3 schematically shows a flow chart of determining the to-be-inputted feature value and to-be-input element scalar of the target performance test requirement according to the type of the target performance test requirement selected by the user in the requirement collection view according to an embodiment of the present disclosure.

As shown in FIG. 3, the method includes operations S301-S302.

In operation S301, according to the type of the target performance test requirement, extract the feature value to be input and the element scalar to be input associated with the type of the target performance test requirement from the element warehouse, wherein the element warehouse includes different types of performance test requirements respectively Corresponding test elements, wherein the test elements include eigenvalue elements and element scalar elements.

According to an embodiment of the present disclosure, the element repository may include all different test elements corresponding to different requirement types in the performance test requirement.

In operation S302, a page entry including the feature value to be input and the element scalar to be input is generated.

According to an embodiment of the present disclosure, the page entry may be a functional view of different requirements that can be selected by the performance test demander. For example, it can be feature value information such as performance testing requirements for new functions, performance testing requirements for seckill activities, etc., or it can also be element scalar information such as the number of users, average daily transaction volume, and delivery time.

According to the embodiments of the present disclosure, by inputting the target test requirement type, converting it into a combination of elements, and extracting the combination of elements from the element warehouse to generate the elements of each requirement instance, the type of performance test requirements can be standardized during the collection process It provides a discourse system that can be understood by all parties involved in the standard, and solves the problem of lack of quality control in the past.

FIG. 4 schematically shows a flow chart of a testing method according to another embodiment of the present disclosure.

As shown in FIG. 4 , the method includes operations S401-S402.

In operation S401, before generating a performance test case according to the eigenvalue information and element scalar information input by the user for the eigenvalues to be input and the element scalars to be input, qualitatively analyze the target performance test requirements according to the eigenvalue information, and obtain a qualitative analysis result .

According to the embodiment of the present disclosure, the qualitative analysis is mainly based on the feature value information to obtain a qualitative conclusion on whether the performance test requirement is allowed to be executed through a decision tree method. For example, the feature value information may be whether it is a newly launched system, whether it is a customer-facing system, whether the processing method is synchronous or asynchronous, and so on.

According to the embodiment of the present disclosure, for example, assuming that the performance test requirement is planned to be this weekend, the pending branch is entered due to insufficient test time, but since the application system is a class A system (a high-risk system for customers), and it is a seckill transaction, Therefore, the requirement enters the allowable execution stage through the qualitative analysis module and enters the subsequent test.

In operation S402, when the qualitative analysis result indicates that the target performance test requirement is allowed to be executed, a performance test case is generated.

According to an embodiment of the present disclosure, the qualitative analysis result may include allowing execution of the target performance test and returning the target performance test. For example, if the target performance test is to be returned, the performance test request is returned to the performance test requester, and the reason for the return is replied.

According to the embodiments of the present disclosure, the qualitative analysis enables the performance testing team to perform preliminary screening of the performance testing requirement review in the qualitative analysis phase, thereby reducing the process of reviewing the performance testing team's requirements and saving labor costs.

The method shown in FIG. 4 will be further described below with reference to FIG. 5 in conjunction with specific embodiments.

FIG. 5 schematically illustrates a flow chart in the case that the qualitative analysis result indicates that the target performance test requirement is allowed to be performed, according to an embodiment of the present disclosure.

As shown in FIG. 5 , the method includes operations S501 to S503.

In operation S501, when the qualitative analysis result indicates that the target performance test requirement is allowed to be executed, quantitatively analyze the target performance test requirement according to the element scalar information to obtain a quantitative analysis result.

According to the embodiment of the present disclosure, the quantitative analysis is based on the element scalars in the demand elements, by quantitatively comparing and analyzing the relevant element scalars and the actual production operation data in the production operation database, evaluating the rationality and importance of the demand, and determining the Whether the performance test requirements are allowed to be executed, enter the follow-up test. The element scalar can be the number of users, average daily transaction volume, data volume, delivery date, etc.

In operation S502, a risk score of the target performance test requirement is calculated according to the quantitative analysis result.

According to an embodiment of the present disclosure, the quantitative analysis result may include allowing execution of the target performance test and returning the target performance test. For example, if the target performance test is to be returned, the performance test request is returned to the performance test requester, and the reason for the return is replied.

According to an embodiment of the present disclosure, calculating the risk score of the target performance test requirement may be to calculate the risk score of the requirement by subjecting the input of the input requirement instance to risk degree evaluation. Specifically, the calculation algorithm may include setting a weight according to each element, the weight may range from -10 to 10, and the risk score of each requirement is equal to the sum of the element scalar × the weight. Factors can include application risk level, delivery date, number of users, average daily transaction volume, etc.

According to an embodiment of the present disclosure, for example, to calculate the risk score of the demand of the Class A application system (high-risk system for customers), the demand risk score is equal to 100-1000/(100×10+100000×0.1+2000000×0.01)= 99.7, record the risk score for this requirement as 99.7 (percentage scale) for follow-up testing.

In operation S503, the execution order of the performance test cases of the target performance test requirement is determined according to the risk score.

According to an embodiment of the present disclosure, the execution order is based on the result of risk analysis and is prioritized according to the score, and combined with the resources that can be invested during the performance test team's evaluation, it is determined that the performance test requirement with the highest risk score is allowed to be executed, and the rest are returned. The performance test demand side, and answer the reasons for rejection.

According to the embodiments of the present disclosure, when the qualitative analysis result indicates that the target performance test requirement is allowed to be executed, combined with quantitative analysis, according to the method of integrated expert experience and data statistical analysis, the performance test requirement is automatically analyzed as the test requirement The basis for allowing execution solves the leakage and leakage of requirements caused by inconsistent standards of different personnel. At the same time, the reasons why the performance test demander allows execution and return can be synchronized to all parties for easy explanation.

According to an embodiment of the present disclosure, performing quantitative analysis on the target performance test requirement according to the element scalar information, and obtaining a quantitative analysis result includes: comparing and analyzing the element scalar information with the actual production operation data in the production operation database to determine the element scalar Is the information reasonable.

According to an embodiment of the present disclosure, the production operation database may include synchronizing the operation data of each application system from the production environment every half month.

According to an embodiment of the present disclosure, the actual production operation data in the production operation database may include indicators such as the average daily transaction volume, data volume, number of users, and delivery date, which are used to check the deviation of key elements input by users on the one hand, and the degree of deviation of key elements input by users on the other hand. The comparative analysis model is continuously adjusted according to the production operation.

According to an embodiment of the present disclosure, for example, according to the statistics of the production operation database, the actual transaction volume and the number of users in the production operation database of the high-risk system for customers are compared with the number of participating users and the active transaction volume in the performance test requirement instance, The estimated indicators in the demand example are all 5 times the current production index, which is a relatively large deviation. However, because it is a transaction such as a spike activity, the transaction growth of less than 10 times is within a reasonable range, and the demand is not directly rejected. , and transfer the analysis results to the performance test demander for confirmation, and the performance test demander confirms the transaction volume change. This requirement allows the performance test to be performed through the quantitative comparative analysis module and enters the risk assessment stage.

According to an embodiment of the present disclosure, the above method further includes: after executing the performance test case, feeding back the execution result to the user.

According to an embodiment of the present disclosure, a performance test case is an element that converts an allowable performance test requirement into a performance test case according to the element scalar, and then generates a corresponding requirement performance test case after conversion, and outputs it to the performance test implementation stage. Elements of a performance test case can include the number of online users, transactions, forks, throughput, response time, etc.

According to the embodiment of the present disclosure, for example, the daily average transaction volume of the transaction is 2,000,000, the transaction time is 9:00-17:00 on working days, and the peak throughput is estimated according to the fact that 80% of the transaction volume is concentrated in 20% of the transaction time. The throughput that this transaction needs to support is (2000000×80%)÷60×60×20%=278.

According to an embodiment of the present disclosure, when a performance test case is executed, the performance test requirement is converted into a performance test case, the test requirement is associated with the test case, and the progress, risk, and result of the implementation process can be fed back to the user.

According to the embodiments of the present disclosure, by combining qualitative analysis and quantitative analysis, the process of reviewing requirements by the performance testing team can be reduced and manpower can be saved. The assessment of performance test requirements is carried out through the solidified expert rules, which solves the leakage and leakage of requirements caused by different personnel standards. In addition, the reasons for the requester's admission and return are clearer and interpretable, so that all parties can synchronize information and avoid misunderstandings.

The method shown in FIG. 2 will be further described below with reference to FIG. 6 in conjunction with specific embodiments.

FIG. 6 schematically illustrates a flow chart showing a requirements collection view according to an embodiment of the present disclosure.

As shown in FIG. 6 , the method includes operations S601-S602.

In operation S601, type information of the logged-in user is acquired.

According to the embodiment of the present disclosure, the user may be the performance testing requester, or may also be the performance testing team.

According to an embodiment of the present disclosure, obtaining the type information of the logged-in user may be through a coding program of user account information preset in the system, and the user logs in his own system account to obtain whether the logged-in user is the performance testing demander or the performance testing team. .

According to an embodiment of the present disclosure, if the user is a performance test demander, the system can provide a relevant view showing the collection of requirements; if the user is a performance test team, the system can provide a view of whether the requirement is allowed to be executed and the demand response view.

In operation S602, in a case where it is determined according to the type information of the logged-in user that the logged-in user is a performance test demander, a demand collection view is displayed.

According to the embodiment of the present disclosure, if the login user information is the performance test demander, the system will provide a function view of the business promotion category for the performance test demander to choose. Business promotion categories can include new features, seckill activities, system upgrades, etc.

FIG. 7 schematically shows a flowchart of a performance testing method according to another embodiment of the present disclosure.

As shown in FIG. 7 , the method includes operations S701 to S708.

In operation S701, the performance test demander logs in to the system, and selects to display the performance test requirements of the business promotion category in the requirements collection view.

In operation S702, a performance test requirement is submitted according to the input provided by the requirement type. Among them, including the application system level, activity type, activity planning time, number of users participating in the activity, and activity transaction volume.

In operation S703, after the requirement is submitted, qualitative analysis is performed by a decision tree method. If the analysis result fails, return to the performance test demander and reply the reason for rejection; if the analysis result passes, output the requirement instance to the next item.

In operation S704, the input demand enters the comparative analysis model of quantitative analysis, and according to the statistics in the production operation database, the relative element scalar is compared and analyzed with the actual production operation data of the production operation database to evaluate the rationality and importance of the demand. If it does not pass, it will return to the performance test demander and reply with the reason; if it passes, the passed requirements will be output to the latter item.

In operation S705, the input requirement enters into quantitative risk assessment, and the risk score of the requirement is calculated according to the element variables in the requirement instance.

In operation S706, the risk scores calculated in the risk degree analysis are sorted, and the performance testing team determines whether the requirement is allowed to be executed according to the resource input situation and the quantitative index of the requirement priority. The requirements with high priority are allowed to be executed, and the remaining requirements that are not allowed to be executed are returned to the performance test demander and the reason is answered.

In operation S707, the requirements for allowing execution are converted into elements of the performance test case according to the element variables. Factors can include transactions, forks, throughput, number of users, response time, etc.

In operation S708, the transformed requirements are formed into a performance test case and output to the performance test implementation stage.

Through the embodiments of the present disclosure, according to the type of the target performance test requirement selected by the user in the requirement collection view, the to-be-input feature value and the to-be-input element scalar of the target performance test requirement are determined; The eigenvalue information and element scalar information of scalar input are used to generate performance test cases; and performance test cases are executed to achieve the target performance test requirements, thereby unifying the channels and methods of performance test requirements and saving communication costs caused by artificial collection requirements. Save manpower; solve the leakage and leakage of requirements caused by different personnel standards, and at the same time, the reasons for the requester's permission and return are more clear and explainable, which is convenient for all parties to synchronize information and avoid misunderstanding; test scenarios and test requirements Strong correlation, providing unified progress management, problem management, risk management, and providing a starting point for managers.

FIG. 8 schematically shows a structural diagram of a testing device according to an embodiment of the present disclosure.

As shown in FIG. 8 , the testing apparatus 800 includes a presentation module 810 , a first determination module 820 , a generation module 830 , and an execution module 840 .

The presentation module 810 is used to present a requirement collection view, wherein the requirement collection view includes options for different types of performance testing requirements.

The first determination module 820 is configured to determine, according to the type of the target performance test requirement selected by the user in the requirement collection view, the to-be-inputted characteristic value and the to-be-input element scalar of the target performance test requirement.

The generating module 830 is configured to generate a performance test case according to the eigenvalue information and element scalar information input by the user for the eigenvalues to be input and the element scalars to be input.

The execution module 840 is used for executing performance test cases to achieve target performance test requirements.

Through the embodiments of the present disclosure, according to the type of the target performance test requirement selected by the user in the requirement collection view, the to-be-input feature value and the to-be-input element scalar of the target performance test requirement are determined; The eigenvalue information and element scalar information of scalar input are used to generate performance test cases; and performance test cases are executed to achieve the target performance test requirements, thereby unifying the channels and methods of performance test requirements and saving communication costs caused by artificial collection requirements. Save manpower; solve the leakage and leakage of requirements caused by different personnel standards, and at the same time, the reasons for the requester's permission and return are more clear and explainable, which is convenient for all parties to synchronize information and avoid misunderstanding; test scenarios and test requirements are strong Association provides unified progress management, problem management, and risk management, and provides a starting point for managers.

According to an embodiment of the present disclosure, the first determination module 820 includes: an extraction unit and a generation unit.

The extraction unit is used to extract the feature value to be input and the element scalar to be input associated with the type of the target performance test requirement from the element warehouse according to the type of the target performance test requirement, wherein the element warehouse includes different types of performance test requirements respectively. Corresponding test elements, wherein the test elements include eigenvalue elements and element scalar elements.

The generating unit is used for generating a page input item including the feature value to be input and the element scalar to be input.

FIG. 9 schematically shows a structural diagram of a testing device according to another embodiment of the present disclosure.

As shown in FIG. 9 , in addition to the display module 810 , the first determination module 820 , the generation module 830 and the execution module 840 , the test device 800 ′ may also include a qualitative analysis module 850 , a quantitative analysis module 860 , a calculation module Module 870 , second determination module 880 , feedback module 890 .

According to an embodiment of the present disclosure, the qualitative analysis module 850 is configured to test the performance of the target according to the eigenvalue information before generating the performance test case according to the eigenvalue information and the element scalar information input by the user for the eigenvalues to be input and the element scalars to be input. The requirement is qualitatively analyzed, and a qualitative analysis result is obtained; and the generating module 830 is configured to generate a performance test case under the condition that the qualitative analysis result indicates that the target performance test requirement is allowed to be executed.

According to an embodiment of the present disclosure, the quantitative analysis module 860 is configured to perform quantitative analysis on the target performance test requirement according to the element scalar information to obtain a quantitative analysis result when the qualitative analysis result indicates that the target performance test requirement is allowed to be executed.

According to an embodiment of the present disclosure, the calculation module 870 is configured to calculate the risk score of the target performance test requirement according to the quantitative analysis result.

According to an embodiment of the present disclosure, the second determination module 880 is configured to determine the execution sequence of the performance test cases of the target performance test requirement according to the risk score.

According to an embodiment of the present disclosure, the quantitative analysis module 860 is configured to compare and analyze the element scalar information with the actual production operation data in the production operation database to determine whether the element scalar information is reasonable.

According to an embodiment of the present disclosure, the feedback module 890 is configured to feed back the execution result to the user after executing the performance test case.

According to an embodiment of the present disclosure, the display module 810 includes: an acquisition unit and a display unit.

The obtaining unit is used to obtain the type information of the logged in user.

The display unit is used to display the requirement collection view when it is determined according to the type information of the logged in user that the logged in user is the performance test demander.

Any of the modules, sub-modules, units, sub-units, or at least part of the functions of any of them according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be divided into multiple modules for implementation. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as hardware circuits, such as field programmable gate arrays (FPGA), programmable logic arrays (PLA), A system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or any other reasonable means of hardware or firmware that integrates or packages circuits, or can be implemented in software, hardware, and firmware Any one of these implementations or an appropriate combination of any of them is implemented. Alternatively, one or more of the modules, sub-modules, units, and sub-units according to embodiments of the present disclosure may be implemented at least in part as computer program modules that, when executed, may perform corresponding functions.

For example, any number of presentation module 810, first determination module 820, generation module 830, execution module 840, qualitative analysis module 850, quantitative analysis module 860, calculation module 870, second determination module 880, feedback module 890 may be combined Implemented in one module/unit/subunit, or any one of the modules/units/subunits can be split into multiple modules/units/subunits. Alternatively, at least part of the functionality of one or more of these modules/units/subunits may be combined with at least part of the functionality of other modules/units/subunits and combined in one module/unit/subunit realized in. According to an embodiment of the present disclosure, the display module 810 , the first determination module 820 , the generation module 830 , the execution module 840 , the qualitative analysis module 850 , the quantitative analysis module 860 , the calculation module 870 , the second determination module 880 , and the feedback module 890 at least one may be implemented at least in part as a hardware circuit, such as a field programmable gate array (FPGA), programmable logic array (PLA), system on chip, system on substrate, system on package, application specific integrated circuit (ASIC), Or it can be implemented by any other reasonable way of integrating or encapsulating the circuit, such as hardware or firmware, or by any one of the three implementation ways of software, hardware and firmware, or by any suitable combination of any of them. Alternatively, at least one of the presentation module 810 , the first determination module 820 , the generation module 830 , the execution module 840 , the qualitative analysis module 850 , the quantitative analysis module 860 , the calculation module 870 , the second determination module 880 , and the feedback module 890 may be at least Partially implemented as computer program modules that, when executed, perform corresponding functions.

It should be noted that the performance testing apparatus in the embodiments of the present disclosure corresponds to the performance testing method section in the embodiments of the present disclosure, and the description of the performance testing apparatus section refers to the performance testing method section, which will not be repeated here.

Another aspect of the present disclosure provides an electronic device comprising: one or more processors; a memory for storing one or more instructions, wherein the one or more instructions when executed by the one or more processors , so that one or more processors implement the above method.

The following description will be given by taking the electronic device as a computer system as an example.

Figure 10 schematically illustrates a block diagram of a computer system suitable for implementing the methods described above, according to an embodiment of the present disclosure. The computer system shown in FIG. 10 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present disclosure.

As shown in FIG. 10 , a computer system 1000 according to an embodiment of the present disclosure includes a processor 1001 that can be loaded into a random access memory (RAM) 1003 according to a program stored in a read only memory (ROM) 1002 or from a storage section 1008 program to perform various appropriate actions and processes. The processor 1001 may include, for example, a general-purpose microprocessor (eg, a CPU), an instruction set processor and/or a related chipset, and/or a special-purpose microprocessor (eg, an application-specific integrated circuit (ASIC)), among others. The processor 1001 may also include onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to the embodiments of the present disclosure.

In the RAM 1003, various programs and data necessary for the operation of the system 1000 are stored. The processor 1001 , the ROM 1002 , and the RAM 1003 are connected to each other through a bus 1004 . The processor 1001 performs various operations of the method flow according to an embodiment of the present disclosure by executing programs in the ROM 1002 and/or the RAM 1003 . Note that the program may also be stored in one or more memories other than the ROM 1002 and the RAM 1003 . The processor 1001 may also perform various operations of the method flow according to the embodiments of the present disclosure by executing programs stored in the one or more memories.

According to embodiments of the present disclosure, the system 1000 may also include an input/output (I/O) interface 1005 that is also connected to the bus 1004 . System 1000 may also include one or more of the following components connected to I/O interface 1005: input portion 1006 including keyboard, mouse, etc.; including components such as cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers An output section 1007 including a hard disk, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN card, a modem, and the like. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I/O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 1010 as needed so that a computer program read therefrom is installed into the storage section 1008 as needed.

According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 1009, and/or installed from the removable medium 1011. When the computer program is executed by the processor 1001, the above-described functions defined in the system of the embodiment of the present disclosure are executed. According to embodiments of the present disclosure, the above-described systems, apparatuses, apparatuses, modules, units, etc. can be implemented by computer program modules.

The present disclosure also provides a computer-readable storage medium. The computer-readable storage medium may be included in the device/apparatus/system described in the above embodiments; it may also exist alone without being assembled into the device/system. device/system. The above-mentioned computer-readable storage medium carries one or more programs, and when the above-mentioned one or more programs are executed, implement the method according to the embodiment of the present disclosure.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), portable compact disk read only memory (CD- ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

For example, according to embodiments of the present disclosure, a computer-readable storage medium may include one or more memories other than ROM 1002 and/or RAM 1003 and/or ROM 1002 and RAM 1003 described above.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented. Those skilled in the art will appreciate that various combinations and/or combinations of features recited in various embodiments and/or claims of the present disclosure are possible, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments of the present disclosure and/or in the claims may be made without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of this disclosure.

Embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only, and are not intended to limit the scope of the present disclosure. Although the various embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art can make various substitutions and modifications, and these substitutions and modifications should all fall within the scope of the present disclosure.

Claims (12)

1. A test method comprising: displaying a requirements collection view, wherein the requirements collection view includes options for different types of performance testing requirements; According to the type of the target performance test requirement selected by the user in the requirement collection view, determine the to-be-input characteristic value and the to-be-input element scalar of the target performance test requirement; generating a performance test case according to the eigenvalue information and element scalar information input by the user for the to-be-input eigenvalue and the to-be-input element scalar; and The performance test case is executed to achieve the target performance test requirement. 2 . The method according to claim 1 , wherein the feature value to be input and the element scalar to be input of the target performance test requirement are determined according to the type of the target performance test requirement selected by the user in the requirement collection view. 3 . include: According to the type of the target performance test requirement, extract the to-be-input feature value and the to-be-input element scalar associated with the type of the target performance test requirement from the element repository, wherein the element repository includes different types of performance tests the test elements corresponding to the requirements respectively, wherein the test elements include eigenvalue elements and element scalar elements; and A page entry including the feature value to be input and the element scalar to be input is generated. 3. The method of claim 1, further comprising: Before generating a performance test case according to the eigenvalue information and element scalar information input by the user for the to-be-input eigenvalue and the to-be-input element scalar, qualitatively analyze the target performance test requirement according to the eigenvalue information, obtain qualitative analysis results; and The performance test case is generated when the qualitative analysis result indicates that the target performance test requirement is allowed to be performed. 4. The method of claim 3, further comprising: When the qualitative analysis result indicates that the target performance test requirement is allowed to be executed, quantitatively analyze the target performance test requirement according to the element scalar information to obtain a quantitative analysis result; and calculating a risk score for the target performance test requirement based on the quantitative analysis result; and The execution sequence of the performance test cases of the target performance test requirement is determined according to the risk score. 5. The method according to claim 4, wherein performing quantitative analysis on the target performance test requirement according to the element scalar information, and obtaining a quantitative analysis result comprises: The element scalar information is compared with the actual production operation data in the production operation database to determine whether the element scalar information is reasonable. 6. The method of any one of claims 1 to 3, further comprising: After the performance test case is executed, the execution result is fed back to the user. 7. The method of any one of claims 1 to 3, wherein the presenting a requirements collection view comprises: Get the type information of the logged in user; and In a case where it is determined according to the type information of the logged-in user that the logged-in user is a performance test demander, the demand collection view is displayed. 8. A test device comprising: a display module, used to display a requirement collection view, wherein the requirement collection view includes options for different types of performance testing requirements; a first determining module, configured to determine the to-be-input characteristic value and to-be-input element scalar of the target performance test requirement according to the type of the target performance test requirement selected by the user in the requirement collection view; a generating module, configured to generate a performance test case according to the eigenvalue information and element scalar information input by the user for the to-be-input eigenvalue and the to-be-input element scalar; and The execution module is used for executing the performance test case to realize the target performance test requirement. 9. The apparatus of claim 8, further comprising: The qualitative analysis module is configured to, before generating a performance test case according to the eigenvalue information and element scalar information input by the user for the to-be-input eigenvalue and the to-be-input element scalar, analyze the target performance according to the eigenvalue information Qualitative analysis of test requirements and qualitative analysis results; and The generating module is configured to generate the performance test case when the qualitative analysis result indicates that the target performance test requirement is allowed to be executed. 10. The apparatus of claim 9, further comprising: a quantitative analysis module, configured to perform quantitative analysis on the target performance test requirement according to the element scalar information under the condition that the qualitative analysis result indicates that the target performance test requirement is allowed to be executed, to obtain a quantitative analysis result; and a calculation module for calculating the risk score of the target performance test requirement according to the quantitative analysis result; and The second determining module is configured to determine, according to the risk score, the execution sequence of the performance test cases of the target performance test requirement. 11. An electronic device comprising: one or more processors; memory for storing one or more instructions, wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7. 12. A computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to implement the method of any one of claims 1 to 7.

Images