CN116302907A - Joint debugging test method and device for service system and joint debugging test system - Google Patents
Joint debugging test method and device for service system and joint debugging test system Download PDFInfo
- Publication number
- CN116302907A CN116302907A CN202111565355.1A CN202111565355A CN116302907A CN 116302907 A CN116302907 A CN 116302907A CN 202111565355 A CN202111565355 A CN 202111565355A CN 116302907 A CN116302907 A CN 116302907A
- Authority
- CN
- China
- Prior art keywords
- joint debugging
- debugging test
- service
- module
- sub
- 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.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 273
- 238000010998 test method Methods 0.000 title claims abstract description 11
- 238000012795 verification Methods 0.000 claims abstract description 108
- 238000000034 method Methods 0.000 claims abstract description 74
- 238000004088 simulation Methods 0.000 claims abstract description 70
- 238000012545 processing Methods 0.000 claims abstract description 55
- 230000008569 process Effects 0.000 claims abstract description 22
- 239000003999 initiator Substances 0.000 claims description 6
- 230000000977 initiatory effect Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 15
- 238000004590 computer program Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000006872 improvement Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013079 data visualisation Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- PCHJSUWPFVWCPO-UHFFFAOYSA-N gold Chemical compound [Au] PCHJSUWPFVWCPO-UHFFFAOYSA-N 0.000 description 1
- 239000010931 gold Substances 0.000 description 1
- 229910052737 gold Inorganic materials 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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/362—Software debugging
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a joint debugging test method, a device and a joint debugging test system of a service system, wherein the method is executed by a server of the joint debugging test system and comprises the following steps: receiving a joint debugging test task; generating joint debugging test simulation data according to the joint debugging test task; generating a transaction request according to joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify the processing result, wherein the service system comprises a plurality of service sub-modules; and obtaining a verification result of at least one service sub-module, and obtaining a joint debugging test result of the service system according to the verification result of the service sub-module. According to the method and the system, the verification results of all the business sub-modules related in the business system can be collected uniformly, joint debugging test of the whole business system is achieved, business simulation degree is greatly improved through generation of simulation data, participation of related personnel of all the business sub-modules is not needed, joint debugging test cost is reduced, and joint debugging test efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of testing technologies, and in particular, to a method and an apparatus for testing a joint debugging of a service system, and a joint debugging testing system.
Background
In the field of financial business, a business system is generally composed of a plurality of business sub-modules, and as business is deepened, the number of modules is also increasing.
When the scenes such as business regression or business joint debugging test of the full link are involved, two modes are generally adopted to realize the simulation verification of the inside of a certain business sub-module in a Mock (a simulation test technology) mode, and the other mode is that each business sub-module participates in the whole joint debugging test by a responsible person.
However, the two modes cannot realize the real full-link service joint debugging test, or have the problem of high cost of manual participation, so that the conventional joint debugging test mode cannot meet the actual test requirement.
Disclosure of Invention
The embodiment of the application provides a joint debugging test method and device of a service system and a joint debugging test system, so as to realize the joint debugging test of the service of a full link and reduce the test cost.
The embodiment of the application adopts the following technical scheme:
in a first aspect, an embodiment of the present application provides a joint debugging method for a service system, which is executed by a joint debugging system server, where the method includes:
Receiving a joint debugging test task;
generating joint debugging test simulation data according to the joint debugging test task;
generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify a processing result, wherein the service system comprises a plurality of service sub-modules;
and obtaining a verification result of at least one service sub-module, and obtaining a joint debugging test result of the service system according to the verification result of the service sub-module.
Optionally, the generating joint debugging test simulation data according to the joint debugging test task includes:
determining a service scene type according to the joint debugging test task;
and generating the joint debugging simulation data according to the service scene type, wherein the joint debugging simulation data comprises one or more dimensions of a transaction initiator, a transaction amount, a transaction type and an institution role.
Optionally, the generating a transaction request according to the joint debugging simulation data and sending the transaction request to a service system includes:
determining basic parameters of a transaction request according to the joint debugging test task, wherein the basic parameters comprise one or more of a service type, a message type and service processing logic;
And generating the transaction request according to the basic parameters of the transaction request and the joint debugging test simulation data.
Optionally, after obtaining the verification result of at least one service sub-module, the method further includes:
checking the checking result of each business sub-module;
and determining whether to terminate the joint debugging test task according to the checking result.
Optionally, the determining whether to terminate the joint debugging test task according to the checking result includes:
if the verification result of the service sub-module is verification failure and the failure cause in the verification result is a first type of failure cause, terminating the joint debugging test task;
if the verification result of the service sub-module is verification success, or the verification result of the service sub-module is verification failure and the failure in the verification result is a second type failure reason, continuing to execute the joint debugging test task.
Optionally, after generating a transaction request according to the joint debugging simulation data and sending the transaction request to a business system, the method further comprises:
determining check nodes of each service sub-module according to the joint debugging test task;
and acquiring the check progress of the check nodes of each service sub-module, and displaying the check progress.
Optionally, after receiving the joint debugging test task, the method further comprises:
generating a joint debugging test task identifier according to the joint debugging test task;
the step of obtaining the check progress of the check nodes of each service sub-module comprises the following steps:
and acquiring the check progress of the check nodes of each service sub-module according to the joint debugging test task identifier.
Optionally, the method further comprises:
acquiring an execution log of the joint debugging test task;
and storing the execution log of the joint debugging test task and the joint debugging test result of the service system into a joint debugging test database.
Optionally, the method further comprises:
providing a front page;
and displaying the joint debugging test result of the service system through the front-end page.
In a second aspect, an embodiment of the present application further provides a joint debugging device of a service system, which is applied to a joint debugging test system server, where the device is used to implement any one of the foregoing methods.
In a third aspect, embodiments of the present application further provide a joint debugging test system, where the system includes:
the front end display module is used for receiving the joint debugging test task;
the data simulation module is used for generating joint debugging test simulation data according to the joint debugging test task;
And the transaction initiating module is used for generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify the processing result, and the service system comprises a plurality of service sub-modules.
And the verification module is used for obtaining the verification result of at least one service sub-module and obtaining the joint debugging test result of the service system according to the verification result of the service sub-module.
In a fourth aspect, embodiments of the present application further provide an electronic device, including:
a processor; and
a memory arranged to store computer executable instructions which, when executed, cause the processor to perform any of the methods described hereinbefore.
In a fifth aspect, embodiments of the present application also provide a computer-readable storage medium storing one or more programs that, when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform any of the methods described above.
The above-mentioned at least one technical scheme that this application embodiment adopted can reach following beneficial effect: the joint debugging test method of the service system can be executed by the joint debugging test system server, and joint debugging test tasks can be received firstly when the joint debugging test of the service system is carried out; then generating joint debugging test simulation data according to the joint debugging test task; then generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify the processing result, wherein the service system comprises a plurality of service sub-modules; and finally, acquiring a verification result of at least one service sub-module, and acquiring a joint debugging test result of the service system according to the verification result of the service sub-module. The joint debugging test system of the embodiment of the application can uniformly collect the verification result of each business sub-module related in the business system, so that the joint debugging test of the whole business system is realized, the business simulation degree is greatly improved through the generation of the simulation data in the process, the participation of related personnel of each business sub-module is not needed, the joint debugging test cost is greatly reduced, and the joint debugging test efficiency is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
fig. 1 is a flow chart of a joint debugging test method of a service system in an embodiment of the present application;
fig. 2 is a schematic diagram of a joint debugging test flow of a service system in an embodiment of the present application;
fig. 3 is a schematic structural diagram of a joint debugging test device of a service system in an embodiment of the present application;
FIG. 4 is a system architecture diagram of a joint debugging test system according to an embodiment of the present application
Fig. 5 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.
The embodiment of the application provides a joint debugging test method of a service system, which is executed by a joint debugging test system server, as shown in fig. 1, and provides a flow diagram of the joint debugging test method of the service system in the embodiment of the application, wherein the method at least comprises the following steps S110 to S140:
step S110, receiving a joint debugging test task.
The joint debugging test method of the service system in the embodiment of the application can be executed by a joint debugging test system which is built in advance, wherein the joint debugging test system can be regarded as a system platform integrated with a plurality of functional modules, and each functional module in the system platform can be uniformly deployed on one server, and of course, the system platform can also be respectively deployed on different servers to respectively execute corresponding operations.
When the joint debugging test is carried out, the joint debugging test task of the service system can be received first, and various modes for triggering the joint debugging test task can be adopted, for example, the joint debugging test of the service system can be triggered according to the actual test requirement of a tester in an actual application scene, and the joint debugging test of the service system can be automatically triggered in a mode of setting a timing task or an irregular task according to the service condition of the service system. The method for receiving the joint debugging test task is specifically adopted, and can be flexibly set by a person skilled in the art according to actual conditions, and is not particularly limited herein.
And step S120, generating joint debugging test simulation data according to the joint debugging test task.
After receiving the joint debugging test task, joint debugging test simulation data can be generated according to test requirement information carried in the joint debugging test task, wherein the joint debugging test simulation data is various business data such as transaction data, reconciliation data, clearing data and the like which are received and processed by a business system under an actual use scene, so that the joint debugging test result can be ensured to reflect the service condition of the business system under the actual business scene as far as possible.
And step S130, generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify the processing result, wherein the service system comprises a plurality of service sub-modules.
After generating the joint debugging test simulation data, in order to simulate the real use scene, the business system can perform corresponding business processing according to the business data, wherein a transaction request is further generated according to the generated joint debugging test simulation data, and then the transaction request is issued to the business system, so that each business sub-module in the business system performs corresponding business processing, and a business processing result is obtained.
Under the actual use situation, the service system has self verification logic, namely, a strategy for verifying the obtained service processing result, such as verifying whether the transaction processing result is accurate or not according to the transaction processing result, and the like, so that the verification result of the whole service system can be obtained.
It should be noted that, since the transaction initiation is generally the first link of the whole service system for processing the service, whether the joint debugging test of the whole link of the service system is to be implemented or the joint debugging test of only part of the links of the service system is to be implemented, the transaction request can be used as the starting point for triggering the joint debugging test, so that the authenticity of the input data and the output result of each service sub-module in the service system can be improved, and the service simulation degree is improved.
And step 140, obtaining a verification result of at least one service sub-module, and obtaining a joint debugging test result of the service system according to the verification result of the service sub-module.
The joint debugging test result of the service system can be determined according to the check result of the service system by acquiring the check result of the whole service system, wherein the joint debugging test result can specifically comprise detail information of the check result of at least one service sub-module in the service system, so that the follow-up file reservation and reference can be facilitated. The verification results of which service sub-modules are included in particular are mainly dependent on requirements of joint debugging test tasks.
According to the business joint debugging test scheme, the checking results of all business sub-modules related in the business system can be uniformly collected through the joint debugging test system constructed in advance, so that joint debugging test of the whole business system is realized, the business simulation degree is greatly improved through generation of simulation data in the process, and related personnel of all the business sub-modules are not required to participate, so that joint debugging test cost is greatly reduced, and joint debugging test efficiency is improved.
In one embodiment of the present application, the generating the joint debugging test simulation data according to the joint debugging test task includes: determining a service scene type according to the joint debugging test task; and generating the joint debugging simulation data according to the service scene type, wherein the joint debugging simulation data comprises one or more dimensions of a transaction initiator, a transaction amount, a transaction type and an institution role.
As described above, the joint debugging test task in the embodiment of the present application may carry joint debugging test requirement information, which may specifically include types of service scenarios, where service data received by a service system and service processing results obtained in different service scenarios are different, for example, a small-amount secret payment-free scenario, a large-amount gold transaction scenario, etc., so that the embodiment of the present application may generate corresponding joint debugging test simulation data according to the types of service scenarios.
Taking transaction service as an example, the generated joint debugging test simulation data can specifically include one or more dimensions of a transaction initiator, transaction amount, transaction type, mechanism role and the like, and of course, the data of other dimensions can be set by a person skilled in the art according to actual requirements, which is not listed here.
Of course, besides the above-mentioned mode of dynamically generating simulation data according to service scene, the mode of static selection can also be adopted to generate simulation data, and no influence is caused on the subsequent test flow by any mode.
In one embodiment of the present application, the generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a business system includes: determining basic parameters of a transaction request according to the joint debugging test task, wherein the basic parameters comprise one or more of a service type, a message type and service processing logic; and generating the transaction request according to the basic parameters of the transaction request and the joint debugging test simulation data.
When the transaction request is generated according to the joint debugging test simulation data, the basic parameters of the transaction request can be determined according to the joint debugging requirement information carried in the joint debugging test task, and the basic parameters can specifically comprise service types, message types, logic customization information and the like, wherein the service types can be understood to be which service sub-modules in a service system need to be concerned by the joint debugging test task, the message types are, for example, IPC (Internet protocol) message protocol or HTTP (hyper text transport protocol) protocol and the like, the logic customization information is defined in advance, and the like, and then the corresponding transaction data can be generated according to the basic parameters of the transaction request and the joint debugging test data.
It should be noted that, a piece of joint debugging test simulation data correspondingly generates a transaction request, and each transaction request is issued to the service system for service processing, so that the whole transaction request issuing process is an asynchronous processing process, further the service processing efficiency can be improved, and meanwhile, the requirements of actual service scenes are met.
In one embodiment of the present application, the service system includes a plurality of service sub-modules, and the obtaining a verification result of at least one service sub-module, and determining, according to the verification result of the service system, a joint debugging test result of the service system includes: determining a target service sub-module according to the joint debugging test task, wherein the target service sub-module is one or more of a plurality of service sub-modules; and obtaining the verification result of each target service sub-module, and obtaining the joint debugging test result of the service system according to the verification result of each target service sub-module.
As described above, the business system of the embodiment of the present application may be covered with a plurality of business sub-modules, for example, may include a transaction sub-module, a reconciliation sub-module, a clearing sub-module, and the like, where different business sub-modules are responsible for processing different businesses. When issuing a transaction request to a service system, each service submodule carries out corresponding service processing according to a service logic relation among the service submodules, for example, after receiving the transaction request, the transaction submodule carries out transaction processing and stores a transaction processing result, and the subsequent reconciliation submodule and the clearing submodule respectively carry out reconciliation processing and clearing processing according to the transaction processing result output by the transaction submodule and respectively obtain a reconciliation processing result and a clearing processing result.
Based on this, the service processing result and the verification result output by each service sub-module in the service system under the full link can be obtained by triggering the transaction request once, however, in the actual application scenario, the tester may only want to pay attention to or test the functions of a certain service sub-module, so the embodiment of the application can determine the target service sub-module according to the joint debugging test task, and the target service sub-module can be understood as the service sub-module actually to be tested by the tester, and further can obtain the joint debugging test result of the final service system according to the verification result of the target service sub-module.
In one embodiment of the present application, after obtaining the verification result of at least one service sub-module, the method further includes: checking the checking result of each business sub-module; and determining whether to terminate the joint debugging test task according to the checking result.
After receiving the verification results of each service sub-module, the embodiment of the application can analyze the verification results of each service sub-module, wherein the verification results can specifically comprise verification success and verification failure results, the verification success indicates that the service processing results are correct, the verification failure can be caused by various reasons, and the two reasons mainly include that the verification results can be faults of a database layer on one hand and faults of a non-service layer such as network abnormality on the other hand.
Different verification results obtained by each service sub-module have a certain influence on the execution of the joint debugging test task, and in order to save test resources and improve test efficiency, whether the current joint debugging test task needs to be terminated can be determined according to the specific verification results.
In one embodiment of the present application, the determining whether to terminate the joint debugging test task according to the checking result includes: if the verification result of the service sub-module is verification failure and the failure cause in the verification result is a first type of failure cause, terminating the joint debugging test task; if the verification result of the service sub-module is verification success, or the verification result of the service sub-module is verification failure and the failure in the verification result is a second type failure reason, continuing to execute the joint debugging test task.
For the service sub-module currently executing the task, if the verification result output by the service sub-module is verification failure, it is indicated that the service request received by the service sub-module is not successfully processed or the processing result is wrong, at this time, the specific reason for the verification failure can be further analyzed, if the first type of failure reason such as database failure is caused, for example, the processing result cannot fall into a database, and if the failure of the database is not processed in time, the subsequent service request also fails to be processed, further the continuous execution of the present joint debugging test task is meaningless, and at this time, the present joint debugging test task can be terminated, so that the execution is repeated after the failure is eliminated.
If the specific reasons for the verification failure are due to some faults of a non-service level, namely the second type of failure reasons, such as temporary abnormal alarms triggered by network interruption, the abnormal conditions are usually automatically eliminated in a short time, so that the subsequent service request processing is not excessively influenced, and the joint debugging test task can be continuously executed. And if the verification result output by the current service sub-module is successful, continuing to execute the joint debugging test task.
It should be noted that, the above embodiments are mainly directed to processing logic between service sub-modules having a sequential execution order, and for parallel service sub-modules, the execution of tasks by the verification results output by each other will not be substantially affected, for example, for a clearing service sub-module and a checking service sub-module, the clearing task and the checking task may be executed simultaneously by both the clearing service sub-module and the checking service sub-module, so that even if the verification result output by the clearing service sub-module is that the verification fails and the failure is due to the first type of failure, the checking task performed by the checking service sub-module will not be affected.
According to the embodiment of the application, the execution process of each service sub-module in the service system can be automatically advanced through the judgment logic, so that the joint debugging test efficiency is greatly improved, and the joint debugging test cost is reduced.
In one embodiment of the present application, after generating a transaction request from the joint debugging test emulation data and sending the transaction request to a business system, the method further comprises: determining check nodes of each service sub-module according to the joint debugging test task; and acquiring the check progress of the check nodes of each service sub-module, and displaying the check progress.
In an actual application scenario, a tester can set data dimensions, i.e. check nodes, to be tested by the service submodules of different service types according to actual test requirements, for example, for the reconciliation service submodule, check nodes including transaction numbers, transaction amounts, bills of an initiator, transaction details, summaries and the like can be set, and of course, the types of check nodes can be set specifically, so that a person skilled in the art can flexibly set the check nodes according to actual requirements, and the check nodes are not limited specifically.
Based on the above, after generating the transaction request according to the joint debugging test simulation data and sending the transaction request to the service system, the embodiment of the application can determine the check node of each service sub-module selected or input by the tester according to the joint debugging test task, and then can further acquire the check progress of the check node of each service sub-module, i.e. whether the check node is currently checked, so that the tester can know the test progress of each service sub-module in time.
In one embodiment of the present application, after receiving the joint debugging test task, the method further comprises: generating a joint debugging test task identifier according to the joint debugging test task; the step of obtaining the check progress of the check nodes of each service sub-module comprises the following steps: and acquiring the check progress of the check nodes of each service sub-module according to the joint debugging test task identifier.
After receiving the joint debugging test task, the embodiment of the invention can also generate a unique joint debugging test task identifier corresponding to the task according to the joint debugging test task, such as a task ID, each transaction request generated later, the processing result obtained, the verification result obtained and the like can carry the task ID, so that the task ID can be used for inquiring if the requirement for inquiring the verification progress of the verification node of each business sub-module or other inquiring requirements exist later, and further, on one hand, the inquiring efficiency can be improved, and on the other hand, the data in the whole joint debugging test task can be managed conveniently.
Of course, besides the above method of inquiring the check progress of the check nodes through joint debugging test task identification, each business sub-module can actively report the check progress of the check nodes related to the check progress, and specifically how to obtain the check progress of the check nodes of each business sub-module, so that the person skilled in the art can flexibly adjust the check progress according to actual requirements, and the check progress is not listed here one by one.
In one embodiment of the present application, the method further comprises: acquiring an execution log of the joint debugging test task; and storing the execution log of the joint debugging test task and the joint debugging test result of the service system into a joint debugging test database.
In order to provide basis for subsequent service system improvement, test flow improvement and the like, the embodiment of the application also acquires the execution log generated in the execution process of the joint debugging test task, and particularly can comprise detailed information such as the execution process of a full link, an execution result and the like, and then stores the execution log of the joint debugging test task and the joint debugging test result of the service system into a joint debugging test database together so as to facilitate subsequent checking.
In one embodiment of the present application, the method further comprises: providing a front page; and displaying the joint debugging test result of the service system through the front-end page.
In order to provide a data visualization function, the joint debugging test system of the embodiment of the application is further provided with a front-end page, on which a user can input various requirement information of the joint debugging test task, and the front-end page can also display the verification progress of each service sub-module in the service system, the joint debugging test result of the whole service system and the like for the user.
The specific displayed content and policy can be set according to actual requirements, for example, only the check progress and check result of check nodes of the service sub-modules concerned by the joint debugging test task can be displayed, and the check progress and check result of check nodes of all the service sub-modules in the whole service system can be displayed. The progress and the result of the verification presented for the front-end page may be updated in a manner that the page is refreshed in real time or at intervals.
The joint debugging test flow of the service system in each embodiment can be executed in the service low peak period of the service system or in the unused time of the service system, so as to avoid excessive influence on the actual service. For the case of executing in the low peak period of the service, since the actual service request enters the service system in the low peak period of the service, in order to distinguish the actual service request and the processing result from the transaction request and the processing result of the joint debugging test, the method can be implemented by using the joint debugging test task identifier generated in the embodiment, that is, each processing result in the joint debugging test scene is carried with the joint debugging test task identifier, and the processing result corresponding to the actual service request does not carry the joint debugging test task identifier, so that the method can be used as a basis for obtaining the joint debugging test result subsequently.
It should be noted that, the joint debugging test method of the service system in the embodiment of the present application may be applied in a joint debugging test scenario, and may also be expanded into a service regression scenario, where the joint debugging test scenario in the embodiment of the present application mainly refers to a test that needs to be performed after a certain service sub-module is updated or a certain service sub-module is newly added in the service system, and the service regression scenario generally does not involve a change of a specific service sub-module, and mainly aims at daily test work.
In order to facilitate understanding of the embodiments of the present application, as shown in fig. 2, a schematic diagram of a joint debugging test flow of a service system in the embodiments of the present application is provided. Firstly, receiving a joint debugging test task triggered by a tester through a front-end page, generating joint debugging test simulation data according to the joint debugging test task, generating a transaction request according to the joint debugging test simulation data, and then issuing the transaction request to a business sub-module in a business system, wherein the business sub-module comprises a real-time business sub-module such as a channel business sub-module, a transaction business sub-module, a payment Jin Yewu sub-module and the like, and a non-real-time business sub-module such as a clearing business sub-module, a reconciliation business sub-module and the like.
The embodiment of the application also provides a joint debugging testing device 300 of a service system, which is applied to a joint debugging testing system server, as shown in fig. 3, and provides a structural schematic diagram of the joint debugging testing device of the service system in the embodiment of the application, where the device 300 includes: a receiving unit 310, a first generating unit 320, a second generating unit 330, and a first acquiring unit 340, wherein:
a receiving unit 310, configured to receive a joint debugging test task;
a first generating unit 320, configured to generate joint debugging test simulation data according to the joint debugging test task;
a second generating unit 330, configured to generate a transaction request according to the joint debugging test simulation data and send the transaction request to a service system, so that the service system performs service processing on the transaction request and verifies a processing result, where the service system includes a plurality of service sub-modules;
the first obtaining unit 340 is configured to obtain a verification result of at least one service sub-module, and obtain a joint debugging test result of the service system according to the verification result of the service sub-module.
In one embodiment of the present application, the first generating unit 320 is specifically configured to: determining a service scene type according to the joint debugging test task; and generating the joint debugging simulation data according to the service scene type, wherein the joint debugging simulation data comprises one or more dimensions of a transaction initiator, a transaction amount, a transaction type and an institution role.
In one embodiment of the present application, the second generating unit 330 is specifically configured to: determining basic parameters of a transaction request according to the joint debugging test task, wherein the basic parameters comprise one or more of a service type, a message type and service processing logic; and generating the transaction request according to the basic parameters of the transaction request and the joint debugging test simulation data.
In one embodiment of the present application, the service system includes a plurality of service sub-modules, and the first obtaining unit 340 is specifically configured to: determining a target service sub-module according to the joint debugging test task, wherein the target service sub-module is one or more of a plurality of service sub-modules; and obtaining the verification result of each target service sub-module, and obtaining the joint debugging test result of the service system according to the verification result of each target service sub-module.
In one embodiment of the present application, the apparatus further comprises: the checking unit is used for checking the checking result of each business sub-module; and the first determining unit is used for determining whether to terminate the joint debugging test task according to the checking result.
In one embodiment of the present application, the first determining unit is specifically configured to: if the verification result of the service sub-module is verification failure and the failure cause in the verification result is a first type of failure cause, terminating the joint debugging test task; if the verification result of the service sub-module is verification success, or the verification result of the service sub-module is verification failure and the failure in the verification result is a second type failure reason, continuing to execute the joint debugging test task.
In one embodiment of the present application, the apparatus further comprises:
the second determining unit is used for determining check nodes of each service sub-module according to the joint debugging test task;
the second acquisition unit is used for acquiring the check progress of the check nodes of each business sub-module and displaying the check progress.
In one embodiment of the present application, the apparatus further comprises: the third generation unit is used for generating a joint debugging test task identifier according to the joint debugging test task; the second obtaining unit is specifically configured to: and acquiring the check progress of the check nodes of each service sub-module according to the joint debugging test task identifier.
In one embodiment of the present application, the apparatus further comprises: the third acquisition unit is used for acquiring an execution log of the joint debugging test task; and the storage unit is used for storing the execution log of the joint debugging test task and the joint debugging test result of the service system into a joint debugging test database.
In one embodiment of the present application, the apparatus further comprises: the providing unit is used for providing a front-end page; and the display unit is used for displaying the joint debugging test result of the service system through the front-end page.
The embodiment of the application also provides a joint debugging test system, as shown in fig. 4, and provides a system architecture diagram of the joint debugging test system in the embodiment of the application, where the system includes:
the front end display module is used for receiving the joint debugging test task;
the data simulation module is used for generating joint debugging test simulation data according to the joint debugging test task;
and the transaction initiating module is used for generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify the processing result, and the service system comprises a plurality of service sub-modules.
And the verification module is used for obtaining the verification result of at least one service sub-module and obtaining the joint debugging test result of the service system according to the verification result of the service sub-module.
The front-end display module of the embodiment of the application is mainly used for testers to trigger joint debugging test tasks, display joint debugging test progress and joint debugging test results and the like. The data simulation module is mainly used for providing input data of the whole joint debugging test system and is responsible for simulating service data according to different service descriptions. The transaction initiating module is mainly responsible for assembling and initiating transaction requests based on simulation data, and parameters of specific assembling comprise dimensions such as service types, message types, logic customization and the like. The verification module can be regarded as a main control module of the whole system and is mainly responsible for the overall arrangement of each service sub-module in the service system, namely, the configuration of each service application and the control of the processing flow of each service sub-module, and also is responsible for informing each service sub-module of joint debugging test tasks, inquiring and collecting the verification results of each service sub-module, relevant analysis persistence and other works.
In addition, the joint debugging test system of the embodiment of the application further comprises an application management module, a log acquisition module, a data storage module and the like. The application management module is mainly responsible for the state inspection and maintenance of each service sub-module, wherein the service sub-module mainly comprises real-time service sub-modules such as channel service, transaction service, payment service, charging service and the like, non-real-time service sub-modules such as clearing service, checking service, accounting service, charging service and the like, and further comprises other service sub-modules such as payment service, national library service, wind control and verification service sub-modules and the like. The log acquisition module is mainly responsible for recording detailed information such as an execution process and an execution result of the full link. The data storage module is mainly responsible for storing simulation data of joint debugging test, verification data of each service sub-module and the like, and can also be used for configuring organization information and the like.
The joint debugging test system of the embodiment of the application adopts a unified verification mode, can uniformly manage the automatic verification results of all the service sub-modules of the full link, realizes the integral regression or joint debugging test of the service sub-modules of the full link, and further realizes the maximization of service simulation. The verification flow and the verification points of each business sub-module can be defined in advance, and the verification module is responsible for receiving or collecting the automatic verification progress and verification result of each business sub-module, so that the automatic propulsion of business regression or joint debugging test tasks is realized.
In addition, the joint debugging test system of the embodiment of the application can also greatly improve the service simulation degree, simultaneously can reduce the degree of manual participation, saves the labor cost and improves the joint debugging test efficiency.
It can be understood that the joint debugging device and the joint debugging system of the service system can implement each step of the joint debugging method of the service system, which is executed by the joint debugging system server and provided in the foregoing embodiment, and the relevant explanation about the joint debugging method of the service system is applicable to the joint debugging device and the joint debugging system of the service system, which are not described herein again.
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application. Referring to fig. 5, at the hardware level, the electronic device includes a processor, and optionally an internal bus, a network interface, and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory (non-volatile Memory), such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, network interface, and memory may be interconnected by an internal bus, which may be an ISA (Industry Standard Architecture ) bus, a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus, or EISA (Extended Industry Standard Architecture ) bus, among others. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in FIG. 5, but not only one bus or type of bus.
And the memory is used for storing programs. In particular, the program may include program code including computer-operating instructions. The memory may include memory and non-volatile storage and provide instructions and data to the processor.
The processor reads the corresponding computer program from the nonvolatile memory to the memory and then runs the computer program to form the joint debugging test device of the service system on a logic level. The processor is used for executing the programs stored in the memory and is specifically used for executing the following operations:
receiving a joint debugging test task;
generating joint debugging test simulation data according to the joint debugging test task;
generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify a processing result, wherein the service system comprises a plurality of service sub-modules;
and obtaining a verification result of at least one service sub-module, and obtaining a joint debugging test result of the service system according to the verification result of the service sub-module.
The method executed by the joint debugging device of the service system disclosed in the embodiment shown in fig. 1 of the present application may be applied to a processor or implemented by the processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
The electronic device may further execute the method executed by the joint debugging device of the service system in fig. 1, and implement the function of the joint debugging device of the service system in the embodiment shown in fig. 1, which is not described herein again.
The embodiments of the present application also provide a computer readable storage medium storing one or more programs, where the one or more programs include instructions, which when executed by an electronic device that includes a plurality of application programs, enable the electronic device to perform a method performed by a joint debugging device of a service system in the embodiment shown in fig. 1, and specifically is configured to perform:
receiving a joint debugging test task;
generating joint debugging test simulation data according to the joint debugging test task;
generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify a processing result, wherein the service system comprises a plurality of service sub-modules;
and obtaining a verification result of at least one service sub-module, and obtaining a joint debugging test result of the service system according to the verification result of the service sub-module.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.
Claims (10)
1. A joint debugging test method of a service system, which is executed by a joint debugging test system server, wherein the method comprises the following steps:
receiving a joint debugging test task;
generating joint debugging test simulation data according to the joint debugging test task;
generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify a processing result, wherein the service system comprises a plurality of service sub-modules;
And obtaining a verification result of at least one service sub-module, and obtaining a joint debugging test result of the service system according to the verification result of the service sub-module.
2. The method of claim 1, wherein the generating joint debugging test simulation data from the joint debugging test task comprises:
determining a service scene type according to the joint debugging test task;
and generating the joint debugging simulation data according to the service scene type, wherein the joint debugging simulation data comprises one or more dimensions of a transaction initiator, a transaction amount, a transaction type and an institution role.
3. The method of claim 1, wherein the generating a transaction request from the joint debugging test emulation data and transmitting the transaction request to a business system comprises:
determining basic parameters of a transaction request according to the joint debugging test task, wherein the basic parameters comprise one or more of a service type, a message type and service processing logic;
and generating the transaction request according to the basic parameters of the transaction request and the joint debugging test simulation data.
4. The method of claim 1, wherein after obtaining the verification result of the at least one service sub-module, the method further comprises:
Checking the checking result of each business sub-module;
and determining whether to terminate the joint debugging test task according to the checking result.
5. The method of claim 4, wherein the determining whether to terminate the joint debugging test task based on the checking result comprises:
if the verification result of the service sub-module is verification failure and the failure cause in the verification result is a first type of failure cause, terminating the joint debugging test task;
if the verification result of the service sub-module is verification success, or the verification result of the service sub-module is verification failure and the failure in the verification result is a second type failure reason, continuing to execute the joint debugging test task.
6. The method of claim 1, wherein after generating a transaction request from the joint debugging test emulation data and sending the transaction request to a business system, the method further comprises:
determining check nodes of each service sub-module according to the joint debugging test task;
and acquiring the check progress of the check nodes of each service sub-module, and displaying the check progress.
7. The method of claim 6, wherein after receiving the joint debugging test task, the method further comprises:
Generating a joint debugging test task identifier according to the joint debugging test task;
the step of obtaining the check progress of the check nodes of each service sub-module comprises the following steps:
and acquiring the check progress of the check nodes of each service sub-module according to the joint debugging test task identifier.
8. The method of claim 1, wherein the method further comprises:
acquiring an execution log of the joint debugging test task;
and storing the execution log of the joint debugging test task and the joint debugging test result of the service system into a joint debugging test database.
9. A joint debugging testing device of a service system, which is applied to a joint debugging testing system server, wherein the device is used for realizing the method of any one of claims 1-8.
10. A joint debugging test system, the system comprising:
the front end display module is used for receiving the joint debugging test task;
the data simulation module is used for generating joint debugging test simulation data according to the joint debugging test task;
and the transaction initiating module is used for generating a transaction request according to the joint debugging test simulation data and sending the transaction request to a service system so that the service system can process the transaction request and verify the processing result, and the service system comprises a plurality of service sub-modules.
And the verification module is used for obtaining the verification result of at least one service sub-module and obtaining the joint debugging test result of the service system according to the verification result of the service sub-module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111565355.1A CN116302907A (en) | 2021-12-20 | 2021-12-20 | Joint debugging test method and device for service system and joint debugging test system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111565355.1A CN116302907A (en) | 2021-12-20 | 2021-12-20 | Joint debugging test method and device for service system and joint debugging test system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116302907A true CN116302907A (en) | 2023-06-23 |
Family
ID=86830985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111565355.1A Pending CN116302907A (en) | 2021-12-20 | 2021-12-20 | Joint debugging test method and device for service system and joint debugging test system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116302907A (en) |
-
2021
- 2021-12-20 CN CN202111565355.1A patent/CN116302907A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9672137B1 (en) | Shadow test replay service | |
| CN112073269B (en) | Block chain network testing method, device, server and storage medium | |
| CN106487603B (en) | Response testing method and device | |
| CN111752850B (en) | Method and related equipment for testing block chain system | |
| CN109299015B (en) | Software testing method, device and system | |
| CN110060139B (en) | Accounting processing method and device | |
| CN115271736B (en) | Method, device, equipment and storage medium for verifying transaction consistency | |
| CN110503297B (en) | Service scene acquisition method and device, electronic equipment and medium | |
| CN110659870A (en) | Business audit test method, device, equipment and storage medium | |
| CN112202647B (en) | Test method, device and test equipment in block chain network | |
| CN114691473A (en) | Test method, test device and electronic equipment | |
| CN111861472B (en) | Service monitoring processing method and device | |
| CN117234916A (en) | Workflow application testing method and device, electronic equipment and storage medium | |
| RU2532714C2 (en) | Method of acquiring data when evaluating network resources and apparatus therefor | |
| CN116302907A (en) | Joint debugging test method and device for service system and joint debugging test system | |
| CN113225218A (en) | Method and device for checking call ticket quality | |
| CN113535538A (en) | Application full-link automatic testing method and device, electronic equipment and storage medium | |
| CN116266328A (en) | Account data checking method and device and electronic equipment | |
| CN112860562B (en) | Automatic test method and device | |
| CN113282496B (en) | Automatic interface testing method, device, equipment and storage medium | |
| CN111679924B (en) | Reliability simulation method and device for componentized software system and electronic equipment | |
| CN112988591A (en) | Charging logic verification method, device, equipment and storage medium | |
| CN111198798B (en) | Service stability measuring method and device | |
| CN112948262A (en) | System test method, device, computer equipment and storage medium | |
| CN110020670B (en) | Model iteration method, device and equipment |
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 |