CN114968829B - Full link pressure test method, electronic device and storage medium - Google Patents
Full link pressure test method, electronic device and storage medium Download PDFInfo
- Publication number
- CN114968829B CN114968829B CN202210919369.7A CN202210919369A CN114968829B CN 114968829 B CN114968829 B CN 114968829B CN 202210919369 A CN202210919369 A CN 202210919369A CN 114968829 B CN114968829 B CN 114968829B
- Authority
- CN
- China
- Prior art keywords
- subsystem
- target transaction
- data
- response result
- full link
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a full link pressure test method, electronic equipment and a storage medium, wherein the full link pressure test method comprises the following steps: when the first response result of the target transaction does not accord with the preset result, the third subsystem calls at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction; when the second response result of the target transaction conforms to the preset result, the third subsystem acquires first calling data and second calling data of the target transaction; and the third subsystem compares the first calling data of the target transaction with the second calling data of the target transaction to obtain calling difference data and the like. Compared with the prior art, the method and the device have the advantages of being high in testing efficiency, and especially have high testing efficiency when massive transactions need to be tested.
Description
Technical Field
The present application relates to the field of device testing, and in particular, to a full link pressure testing method, an electronic device, and a storage medium.
Background
The full link pressure test is an important ring in the field of software test, and for the traditional full link pressure test, under the condition that system resources are consumed to a certain extent, three performance indexes are mainly considered: response time, transaction processing capability, and failure rate. Currently, for banking, the failure rate is the most important performance index, because banking is the most sensitive to failed transactions.
However, in the existing full link pressure testing technology, because the full link has serial-parallel combination, synchronous-asynchronous mixing, and different timeout times of each node, when a transaction execution failure occurs, the reason of the transaction execution failure cannot be determined based on the abnormal log output by each node of the link.
In view of the above problems, in the prior art, the code for implementing the transaction is modified and analyzed manually to determine the reason of the transaction execution failure, however, this method has low analysis efficiency and depends on each node to output the exception log, for example, when the reason of the transaction failure is analyzed, if one node outputs the exception log temporarily, the analysis process is interrupted.
Disclosure of Invention
An object of the embodiments of the present application is to provide a full link pressure testing method, an electronic device, and a storage medium, which are used to perform a full link pressure test on a target transaction.
In a first aspect, the present invention provides a full link pressure testing method, where the method is applied to a full link pressure testing system, where the full link pressure testing system includes a first subsystem, at least two second subsystems, and a third subsystem, and the method includes:
after the first subsystem receives a full link pressure test request aiming at a target transaction, the first subsystem calls at least two second subsystems to test the target transaction and obtains a first response result of the target transaction;
the first subsystem sends a first response result of the target transaction to the third subsystem so that the third subsystem judges whether the first response result of the target transaction meets a preset result or not;
when the first response result of the target transaction does not accord with the preset result, the third subsystem calls at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction;
when the second response result of the target transaction conforms to the preset result, the third subsystem acquires first calling data and second calling data of the target transaction;
and the third subsystem compares the first calling data of the target transaction with the second calling data of the target transaction to obtain calling difference data.
In the first aspect of the present application, after the first subsystem receives a full link pressure test request for a target transaction, the first subsystem can invoke at least two second subsystems to test the target transaction, and obtain a first response result of the target transaction, and then the first subsystem can send the first response result of the target transaction to the third subsystem, so that the third subsystem determines whether the first response result of the target transaction meets a preset result; further, when the first response result of the target transaction does not accord with the preset result, the third subsystem can call at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction, and further when the second response result of the target transaction accords with the preset result, the third subsystem can obtain first call data and second call data of the target transaction and compare the first call data of the target transaction with the second call data of the target transaction to obtain call difference data, and finally the reason of execution failure of the target transaction can be determined through the call difference data.
Compared with the prior art, the method and the device do not need to modify and analyze the related codes of the target affairs manually, and can automatically obtain the calling difference data through the steps, so that the method and the device have higher testing efficiency, and particularly have higher testing efficiency in the scene that a large number of affairs need to be tested.
In an alternative embodiment, the method further comprises:
when the second response result of the target transaction does not accord with the preset result, the third subsystem repeatedly calls at least two second subsystems to test the target transaction again until the second response result of the target transaction accords with the preset result.
In this optional embodiment, the third subsystem may repeatedly invoke at least two of the second subsystems to perform a retest on the target transaction until the second response result of the target transaction matches the preset result.
In an alternative embodiment, the method further comprises:
and when the test times of the repeated calling of the third subsystem is more than or equal to a preset threshold value, determining the input parameter data carried by the full link pressure test request as abnormal data.
In this optional embodiment, when the number of times of the test repeatedly invoked by the third subsystem is greater than or equal to a preset threshold, the third subsystem may determine the incoming parameter data carried by the full link pressure test request as abnormal data.
In an alternative embodiment, the full link pressure test system further includes a monitoring subsystem, and the method further includes:
and the monitoring subsystem acquires and stores input parameters and output parameters used when each second subsystem tests the target transaction.
In this optional embodiment, the monitoring subsystem may obtain and store the input parameters and the output parameters used by each second subsystem to test the target transaction, so that when the third subsystem needs to analyze data differences in the process of executing the target transaction multiple times, it is not necessary to wait for each second subsystem to output an exception log, but may obtain the exception log from the monitoring subsystem.
In an optional embodiment, the third subsystem invokes at least two of the second subsystems to perform retesting on the target transaction, and obtains a second response result of the target transaction, including:
the third subsystem acquires input parameters used by each second subsystem for testing the target transaction from the monitoring subsystem;
and the third subsystem retests the target transaction for at least two second subsystems based on the input parameters used when each second subsystem tests the target transaction, and obtains a second response result of the target transaction.
In an optional embodiment, the third subsystem may be configured to retest the target transaction for at least two of the second subsystems based on input parameters used when each of the second subsystems tests the target transaction, and obtain a second response result of the target transaction.
In an optional embodiment, the obtaining, by the third subsystem, the first call data and the second call data of the target transaction includes:
and the third subsystem acquires the first calling data and the second calling data of the target transaction from the monitoring subsystem based on the unique identifier of the full link pressure test request.
In this optional embodiment, the third subsystem may be capable of acquiring, from the monitoring subsystem, the first call data and the second call data of the target transaction based on the unique identifier of the full link pressure test request.
In an optional embodiment, the comparing, by the third subsystem, the first call data of the target transaction with the second call data of the target transaction to obtain call difference data includes:
and the third subsystem compares a preset field in the first calling data of the target transaction with a preset field in the second calling data of the target transaction to obtain the calling difference data.
In this optional implementation manner, the third subsystem may compare a preset field in the first call data of the target transaction with a preset field in the second call data of the target transaction, so as to obtain the call difference data.
In an optional embodiment, before the third subsystem invokes at least two of the second subsystems to retest the target transaction, the method further comprises:
and the first subsystem judges whether a retest instruction is received, and if so, the third subsystem is triggered to call at least two second subsystems to retest the target transaction.
In this optional embodiment, the first subsystem may determine whether a retest instruction is received, and if so, may trigger the third subsystem to call at least two of the second subsystems to retest the target transaction.
In a second aspect, the present invention provides an electronic device comprising:
a processor; and
a memory configured to store machine readable instructions that, when executed by the processor, perform a full link pressure testing method as in any one of the preceding embodiments.
According to the electronic equipment in the second aspect of the application, by executing the full link pressure testing method, after the first subsystem receives the full link pressure testing request for the target transaction, the first subsystem can call at least two second subsystems to test the target transaction and obtain a first response result of the target transaction, and then the first subsystem can send the first response result of the target transaction to the third subsystem, so that the third subsystem can judge whether the first response result of the target transaction meets a preset result or not; further, when the first response result of the target transaction does not accord with the preset result, the third subsystem can call at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction, and further when the second response result of the target transaction accords with the preset result, the third subsystem can obtain first call data and second call data of the target transaction and compare the first call data of the target transaction with the second call data of the target transaction to obtain call difference data, and finally the reason of execution failure of the target transaction can be determined through the call difference data.
Compared with the prior art, the method and the device do not need to modify and analyze the related codes of the target affairs manually, and can automatically obtain the calling difference data through the steps, so that the method and the device have higher testing efficiency, and particularly have higher testing efficiency in the scene that a large number of affairs need to be tested.
In a third aspect, the present invention provides a storage medium storing a computer program for execution by a processor of a full link pressure testing method according to any one of the preceding embodiments.
By executing the full link pressure testing method, when the first subsystem receives a full link pressure testing request for a target transaction, the first subsystem can call at least two second subsystems to test the target transaction and obtain a first response result of the target transaction, and then the first subsystem can send the first response result of the target transaction to the third subsystem, so that the third subsystem can judge whether the first response result of the target transaction meets a preset result; further, when the first response result of the target transaction does not accord with the preset result, the third subsystem can call at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction, and further when the second response result of the target transaction accords with the preset result, the third subsystem can obtain the first call data and the second call data of the target transaction, compare the first call data of the target transaction with the second call data of the target transaction to obtain call difference data, and finally determine the reason of the target transaction execution failure through the call difference data.
Compared with the prior art, the method and the device do not need to modify and analyze the related codes of the target affairs manually, and can automatically obtain the calling difference data through the steps, so that the method and the device have higher testing efficiency, and particularly have higher testing efficiency in the scene that a large number of affairs need to be tested.
Drawings
To more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
FIG. 1 is a schematic structural diagram of a full link pressure test system disclosed in an embodiment of the present application;
fig. 2 is a schematic flowchart of a full link pressure testing method disclosed in an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device disclosed in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Example one
Referring to fig. 1, fig. 1 is a schematic structural diagram of a full link pressure testing system according to an embodiment of the present disclosure. As shown in fig. 1, the full link pressure testing system according to the embodiment of the present application includes a first subsystem 100, a second subsystem 200, and a third subsystem 300, wherein the first subsystem and the second subsystem are communicatively connected, so that data can be transmitted between the first subsystem and the second subsystem. The third subsystem is communicatively coupled to the first subsystem such that data may be transmitted between the third subsystem and the first subsystem.
Further, the full link pressure testing system further includes a monitoring subsystem 400, wherein the monitoring subsystem is connected to the first subsystem, the second subsystem and the third subsystem in a communication manner, so that the monitoring subsystem can perform data interaction with the first subsystem, the second subsystem and the third subsystem.
In this embodiment of the present application, the first subsystem serves as a traffic entry for full link pressure testing, and may receive a full link pressure test request of a target transaction, where when the first subsystem receives the full link pressure test request of the target transaction, it may invoke the second subsystem to test the target transaction.
In an embodiment of the present application, optionally, the full link pressure testing system includes at least two second subsystems, for example, the full link pressure testing system includes a second subsystem a and a second subsystem B. Further optionally, the first subsystem may invoke the second subsystem in a simultaneous invocation mode, for example, the first subsystem invokes the second subsystem a and the second subsystem B simultaneously. On the other hand, the second subsystem may be called in a sequential manner, for example, the first subsystem calls the second subsystem a first, and then calls the second subsystem B through the second subsystem a.
In the embodiment of the application, when the first subsystem calls the second subsystem, the first subsystem can analyze the parameters carried by the full link pressure test request of the target transaction into input parameters required by calling, so that the second subsystem is called based on the input parameters, the second subsystem tests the target transaction based on the input parameters, and a calling result is returned.
In the system of the application embodiment, after a first subsystem receives a full link pressure test request for a target transaction, the first subsystem calls at least two second subsystems to test the target transaction and obtain a first response result of the target transaction, correspondingly, the first subsystem sends the first response result of the target transaction to a third subsystem so that the third subsystem judges whether the first response result of the target transaction meets a preset result, correspondingly, when the first response result of the target transaction does not meet the preset result, the third subsystem calls the at least two second subsystems to test the target transaction again and obtains a second response result of the target transaction, correspondingly, when the second response result of the target transaction meets the preset result, the third subsystem obtains first call data and second call data of the target transaction, and correspondingly, the third subsystem compares the first call data of the target transaction with the second call data of the target transaction to obtain call difference data.
In the embodiment of the application, after the first subsystem receives a full link pressure test request for a target transaction, the first subsystem can call at least two second subsystems to test the target transaction and obtain a first response result of the target transaction, and then the first subsystem can send the first response result of the target transaction to the third subsystem, so that the third subsystem can judge whether the first response result of the target transaction meets a preset result or not; further, when the first response result of the target transaction does not accord with the preset result, the third subsystem can call at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction, and further when the second response result of the target transaction accords with the preset result, the third subsystem can obtain the first call data and the second call data of the target transaction, compare the first call data of the target transaction with the second call data of the target transaction to obtain call difference data, and finally determine the reason of the target transaction execution failure through the call difference data.
Compared with the prior art, the method and the device for testing the transaction have the advantages that the related codes of the target transaction do not need to be modified and analyzed manually, and the calling difference data can be obtained automatically through the steps, so that the method and the device have higher testing efficiency, and particularly have higher testing efficiency in a scene that a large number of transactions need to be tested.
Please refer to the following description of the present application for further description of the full link pressure test system according to the embodiment of the present application.
Example two
Referring to fig. 2, fig. 2 is a schematic flow chart of a full link pressure testing method disclosed in the embodiment of the present application, wherein the full link pressure testing method is applied to a full link pressure testing system in the embodiment of the present application. As shown in fig. 2, the method of the embodiment of the present application includes the following steps:
101. after the first subsystem receives a full link pressure test request aiming at a target transaction, the first subsystem calls at least two second subsystems to test the target transaction and obtain a first response result of the target transaction;
102. the first subsystem sends the first response result of the target transaction to the third subsystem so that the third subsystem judges whether the first response result of the target transaction conforms to a preset result or not;
103. when the first response result of the target transaction does not accord with the preset result, the third subsystem calls at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction;
104. when the second response result of the target transaction conforms to the preset result, the third subsystem acquires first calling data and second calling data of the target transaction;
105. and the third subsystem compares the first calling data of the target transaction with the second calling data of the target transaction to obtain calling difference data.
In the embodiment of the application, after the first subsystem receives a full link pressure test request for a target transaction, the first subsystem can call at least two second subsystems to test the target transaction and obtain a first response result of the target transaction, and then the first subsystem can send the first response result of the target transaction to the third subsystem, so that the third subsystem can judge whether the first response result of the target transaction meets a preset result or not; further, when the first response result of the target transaction does not accord with the preset result, the third subsystem can call at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction, and further when the second response result of the target transaction accords with the preset result, the third subsystem can obtain the first call data and the second call data of the target transaction, compare the first call data of the target transaction with the second call data of the target transaction to obtain call difference data, and finally determine the reason of the target transaction execution failure through the call difference data.
Compared with the prior art, the method and the device for testing the transaction have the advantages that the related codes of the target transaction do not need to be modified and analyzed manually, and the calling difference data can be obtained automatically through the steps, so that the method and the device have higher testing efficiency, and particularly have higher testing efficiency in a scene that a large number of transactions need to be tested.
In an alternative implementation, the method of the embodiments of the present application further includes the steps of:
and when the second response result of the target transaction does not accord with the preset result, the third subsystem repeatedly calls the at least two second subsystems to test the target transaction again until the second response result of the target transaction accords with the preset result.
In this optional embodiment, the third subsystem can repeatedly invoke at least two second subsystems to perform retest on the target transaction until the second response result of the target transaction meets the preset result.
In an alternative implementation, the method of the embodiments of the present application further includes the steps of:
and when the test times of the repeated calling of the third subsystem is more than or equal to a preset threshold value, determining the input parameter data carried by the full link pressure test request as abnormal data.
In this optional embodiment, when the number of times of the test repeatedly invoked by the third subsystem is greater than or equal to the preset threshold, the third subsystem may determine the entry parameter data carried by the full link pressure test request as abnormal data.
In an alternative embodiment, the full link stress testing system further includes a monitoring subsystem, and the method further includes:
and the monitoring subsystem acquires and stores input parameters and output parameters used when each second subsystem tests the target transaction.
In this optional embodiment, the monitoring subsystem can acquire and store the input parameters and the output parameters used when each second subsystem tests the target transaction, so that when the third subsystem needs to analyze data differences in the process of executing the target transaction multiple times, it is not necessary to wait for each second subsystem to output an exception log, but rather, the exception logs can be acquired from the monitoring subsystem.
In an alternative embodiment, the steps of: the third subsystem calls at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction, and the method further comprises the following steps:
the third subsystem acquires input parameters used when each second subsystem tests the target transaction from the monitoring subsystem;
and the third subsystem retests the target transaction of the at least two second subsystems based on the input parameters used when each second subsystem tests the target transaction, and obtains a second response result of the target transaction.
In an optional embodiment, the third subsystem may be configured to retest the target transaction for the at least two second subsystems based on the input parameters used when each second subsystem tests the target transaction, and obtain a second response result of the target transaction.
In an alternative embodiment, the steps of: the third subsystem acquires the first calling data and the second calling data of the target transaction, and comprises the following steps:
and the third subsystem acquires the first calling data and the second calling data of the target transaction from the monitoring subsystem based on the unique identification of the full-link pressure test request.
In this alternative embodiment, the third subsystem may be capable of obtaining the first call data and the second call data of the target transaction from the monitoring subsystem based on the unique identifier of the full link pressure test request.
In an alternative embodiment, the comparing, by the third subsystem, the first call data of the target transaction with the second call data of the target transaction to obtain the call difference data includes:
and the third subsystem compares the preset field in the first calling data of the target transaction with the preset field in the second calling data of the target transaction to obtain calling difference data.
In this optional embodiment, the third subsystem may compare a preset field in the first call data of the target transaction with a preset field in the second call data of the target transaction to obtain call difference data.
In an optional implementation manner, before the third subsystem invokes at least two second subsystems to retest the target transaction, the method of the embodiment of the present application further includes the following steps:
and the first subsystem judges whether a retest instruction is received, and if so, the third subsystem is triggered to call the at least two second subsystems to retest the target transaction.
In this optional embodiment, the first subsystem may determine whether a retest instruction is received, and if so, may trigger the third subsystem to call the at least two second subsystems to retest the target transaction.
EXAMPLE III
Referring to fig. 3, fig. 3 is a schematic structural diagram of an electronic device disclosed in an embodiment of the present application, and as shown in fig. 3, the electronic device in the embodiment of the present application includes:
a processor 201; and
a memory 202 configured to store machine readable instructions that, when executed by the processor 201, perform a full link pressure testing method as in any one of the preceding embodiments.
By executing the full link pressure testing method, after the first subsystem receives a full link pressure testing request for a target transaction, the first subsystem can call at least two second subsystems to test the target transaction and obtain a first response result of the target transaction, and then the first subsystem can send the first response result of the target transaction to the third subsystem, so that the third subsystem can judge whether the first response result of the target transaction meets a preset result or not; further, when the first response result of the target transaction does not accord with the preset result, the third subsystem can call at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction, and further when the second response result of the target transaction accords with the preset result, the third subsystem can obtain the first call data and the second call data of the target transaction, compare the first call data of the target transaction with the second call data of the target transaction to obtain call difference data, and finally determine the reason of the target transaction execution failure through the call difference data.
Compared with the prior art, the method and the device for testing the transaction have the advantages that the related codes of the target transaction do not need to be modified and analyzed manually, and the calling difference data can be obtained automatically through the steps, so that the method and the device have higher testing efficiency, and particularly have higher testing efficiency in a scene that a large number of transactions need to be tested.
Example four
The embodiment of the application provides a storage medium, wherein a computer program is stored in the storage medium, and the computer program is executed by a processor to execute the full link pressure testing method according to any one of the foregoing implementation modes.
By executing the full link pressure testing method, when the first subsystem receives a full link pressure testing request for a target transaction, the first subsystem can call at least two second subsystems to test the target transaction and obtain a first response result of the target transaction, and then the first subsystem can send the first response result of the target transaction to the third subsystem, so that the third subsystem can judge whether the first response result of the target transaction meets a preset result; further, when the first response result of the target transaction does not accord with the preset result, the third subsystem can call at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction, and further when the second response result of the target transaction accords with the preset result, the third subsystem can obtain the first call data and the second call data of the target transaction, compare the first call data of the target transaction with the second call data of the target transaction to obtain call difference data, and finally determine the reason of the target transaction execution failure through the call difference data.
Compared with the prior art, the method and the device do not need to modify and analyze the related codes of the target affairs manually, and can automatically obtain the calling difference data through the steps, so that the method and the device have higher testing efficiency, and particularly have higher testing efficiency in the scene that a large number of affairs need to be tested.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is only a logical division, and other divisions may be realized in practice, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
In addition, units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
Furthermore, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
It should be noted that the functions, if implemented in the form of software functional modules and sold or used as independent products, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
The above embodiments are merely examples of the present application and are not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (9)
1. A full link pressure test method is applied to a full link pressure test system, wherein the full link pressure test system comprises a first subsystem, at least two second subsystems and a third subsystem, and the method comprises the following steps:
after the first subsystem receives a full link pressure test request aiming at a target transaction, the first subsystem calls at least two second subsystems to test the target transaction and obtains a first response result of the target transaction;
the first subsystem sends a first response result of the target transaction to the third subsystem so that the third subsystem judges whether the first response result of the target transaction meets a preset result or not;
when the first response result of the target transaction does not accord with the preset result, the third subsystem calls at least two second subsystems to test the target transaction again and obtain a second response result of the target transaction;
when the second response result of the target transaction conforms to the preset result, the third subsystem acquires first calling data and second calling data of the target transaction;
the third subsystem compares the first calling data of the target transaction with the second calling data of the target transaction to obtain calling difference data;
and, the method further comprises:
when the second response result of the target transaction does not accord with the preset result, the third subsystem repeatedly calls at least two second subsystems to test the target transaction again until the second response result of the target transaction accords with the preset result.
2. The method of claim 1, wherein the method further comprises:
and when the test times of the third subsystem repeated calling are more than or equal to a preset threshold value, the third subsystem determines the entry parameter data carried by the full link pressure test request as abnormal data.
3. The method of claim 1, wherein the full link pressure test system further comprises a monitoring subsystem, the method further comprising:
and the monitoring subsystem acquires and stores input parameters and output parameters used when each second subsystem tests the target transaction.
4. The method of claim 3, wherein the third subsystem invoking at least two of the second subsystems to retest the target transaction and obtain a second response result for the target transaction, comprising:
the third subsystem acquires input parameters used by each second subsystem for testing the target transaction from the monitoring subsystem;
and the third subsystem tests the target transaction again for at least two second subsystems based on the input parameters used when each second subsystem tests the target transaction, and obtains a second response result of the target transaction.
5. The method of claim 3, wherein the third subsystem obtaining the first call data and the second call data for the target transaction comprises:
and the third subsystem acquires the first calling data and the second calling data of the target transaction from the monitoring subsystem based on the unique identifier of the full link pressure test request.
6. The method of claim 3, wherein the third subsystem comparing the first call data of the target transaction to the second call data of the target transaction to obtain call difference data, comprises:
and the third subsystem compares a preset field in the first calling data of the target transaction with a preset field in the second calling data of the target transaction to obtain the calling difference data.
7. The method of claim 1, wherein before the third subsystem invokes at least two of the second subsystems to retest the target transaction, the method further comprises:
and the first subsystem judges whether a retest instruction is received, and if so, a third subsystem is triggered to call at least two second subsystems to retest the target transaction.
8. An electronic device, comprising:
a processor; and
a memory configured to store machine readable instructions that, when executed by the processor, perform the full link pressure testing method of any of claims 1-7.
9. A storage medium storing a computer program for execution by a processor of the full link pressure testing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210919369.7A CN114968829B (en) | 2022-08-02 | 2022-08-02 | Full link pressure test method, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210919369.7A CN114968829B (en) | 2022-08-02 | 2022-08-02 | Full link pressure test method, electronic device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114968829A CN114968829A (en) | 2022-08-30 |
| CN114968829B true CN114968829B (en) | 2022-10-28 |
Family
ID=82970363
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210919369.7A Active CN114968829B (en) | 2022-08-02 | 2022-08-02 | Full link pressure test method, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114968829B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110740079A (en) * | 2019-10-16 | 2020-01-31 | 北京航空航天大学 | full link benchmark test system for distributed scheduling system |
| CN112306648A (en) * | 2020-10-29 | 2021-02-02 | 平安科技（深圳）有限公司 | Transaction calling method and device, electronic equipment and storage medium |
| CN112350878A (en) * | 2019-08-07 | 2021-02-09 | 阿里巴巴集团控股有限公司 | Pressure test system |
| CN112799940A (en) * | 2021-01-26 | 2021-05-14 | 中国工商银行股份有限公司 | Regression testing method, device, computer system and computer readable storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190004932A1 (en) * | 2017-06-30 | 2019-01-03 | Infinera Corporation | Unit test and automation framework (utaf) system and method |
| CN109491891A (en) * | 2018-10-17 | 2019-03-19 | 深圳壹账通智能科技有限公司 | Full-automatic interface pressure surveys method, apparatus, computer equipment and storage medium |
| CN110262977A (en) * | 2019-06-24 | 2019-09-20 | 深圳前海微众银行股份有限公司 | A kind of full link performance test method, calculates equipment and storage medium at device |
| CN113986766A (en) * | 2021-11-29 | 2022-01-28 | 深圳前海微众银行股份有限公司 | Automatic testing method and device |
-
2022
- 2022-08-02 CN CN202210919369.7A patent/CN114968829B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112350878A (en) * | 2019-08-07 | 2021-02-09 | 阿里巴巴集团控股有限公司 | Pressure test system |
| CN110740079A (en) * | 2019-10-16 | 2020-01-31 | 北京航空航天大学 | full link benchmark test system for distributed scheduling system |
| CN112306648A (en) * | 2020-10-29 | 2021-02-02 | 平安科技（深圳）有限公司 | Transaction calling method and device, electronic equipment and storage medium |
| CN112799940A (en) * | 2021-01-26 | 2021-05-14 | 中国工商银行股份有限公司 | Regression testing method, device, computer system and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114968829A (en) | 2022-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110445688B (en) | Interface service function monitoring method and system based on data collection | |
| US10657028B2 (en) | Method for replicating production behaviours in a development environment | |
| CN112948234B (en) | Interface test method and device and electronic equipment | |
| CN112732563A (en) | Interface script test log extraction method and device, terminal and storage medium | |
| CN110851352A (en) | Fuzzy test system and terminal equipment | |
| CN114253864A (en) | Service testing method and device, electronic equipment and storage medium | |
| CN112650676A (en) | Software testing method, device, equipment and storage medium | |
| CN112100070A (en) | Version defect detection method and device, server and storage medium | |
| CN116302989A (en) | Pressure testing method and system, storage medium and computer equipment | |
| CN112882957B (en) | Test task validity checking method and device | |
| CN107257290A (en) | A kind of method of testing and system of open SOA Service-Oriented Architecture Baseds | |
| CN116401113B (en) | Environment verification method, device and medium for heterogeneous many-core architecture acceleration card | |
| CN114968829B (en) | Full link pressure test method, electronic device and storage medium | |
| CN115276844B (en) | Communication module testing method and device, storage medium and electronic equipment | |
| CN115757084A (en) | Test method and test device and storage medium | |
| CN112000579B (en) | Software interface testing method, system, equipment and medium | |
| CN108845932B (en) | Unit testing method and device of network library, storage medium and terminal | |
| CN113656314A (en) | Pressure test processing method and device | |
| CN113419738A (en) | Interface document generation method and device and interface management equipment | |
| CN111934949A (en) | Safety test system based on database injection test | |
| CN114816876B (en) | Automatic test system for server Redfish interface specifications | |
| CN111324542B (en) | Web application regression test case selection system, method and equipment | |
| CN114356344B (en) | Application deployment method and device, electronic equipment and storage medium | |
| CN113515401B (en) | Positioning and debugging method, system, electronic equipment and medium for abnormal transaction | |
| CN113485938A (en) | Automatic testing method and device for large host |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |