CN108388501B - Intersystem integration test method - Google Patents
Intersystem integration test method Download PDFInfo
- Publication number
- CN108388501B CN108388501B CN201810024267.2A CN201810024267A CN108388501B CN 108388501 B CN108388501 B CN 108388501B CN 201810024267 A CN201810024267 A CN 201810024267A CN 108388501 B CN108388501 B CN 108388501B
- Authority
- CN
- China
- Prior art keywords
- flow
- servers
- flow request
- calling
- request
- 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/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/323—Visualisation of programs or trace data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The invention provides an intersystem integration test method, which comprises the steps of respectively deploying an agent program on each server of a first system and a second system, wherein the agent program is used for forwarding all flow requests entering and exiting a corresponding server process to a preset central server; the method comprises the steps that a preset center server receives flow requests forwarded by agent programs deployed on servers of a first system and a second system and correspondingly stores the received flow requests and the servers forwarding the flow requests; and displaying the calling relationship and calling data among the servers involved in each complete calling process on a preset page according to the corresponding relationship between the flow request stored in a preset central server and the server for forwarding the flow request, the flow request ID carried in the flow request and the calling time sequence of the flow request. The invention can realize the tracking and page display of each service call in the two systems, thereby effectively shortening the problem troubleshooting time in the integrated test.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an intersystem integration test method.
Background
The micro-servitization trend ensures that respective systems or services are clearly divided and respectively perform their own functions, so that the test is more concentrated on ensuring the functions of single modules, and the quality guarantee among the systems can only be performed by an integrated test mode of joint debugging of the systems, wherein the test is dominated by front-end service test and supported by rear-end test. Once defects or faults are found in the joint debugging test, due to the fact that a calling chain is complex and multiple services are involved, step-by-step positioning and checking are needed to determine which services are caused by problems, and a large amount of labor communication and time cost are generated.
Disclosure of Invention
Aiming at the defects in the prior art, the invention provides an inter-system integration test method, which can realize the tracking and page display of each service call in two systems, thereby effectively shortening the problem troubleshooting time in the integration test.
In order to achieve the purpose, the invention provides the following technical scheme:
the invention provides an intersystem integration test method, which comprises the following steps:
respectively deploying agent programs on each server of the first system and the second system, wherein the agent programs are used for forwarding all flow requests entering and exiting the corresponding server processes to a preset central server; for service call among servers in a first system, among servers in a second system, or among servers in the first system and the second system, in each complete call flow, the earliest caller adds a corresponding flow request ID in a flow request, and each level of servers in the whole call flow also carry the flow request ID when carrying out data transmission;
the preset central server receives flow requests forwarded by the agents deployed on the servers of the first system and the second system and correspondingly stores the received flow requests and the servers forwarding the flow requests;
and displaying the calling relationship and calling data among the servers involved in each complete calling flow on a preset page according to the corresponding relationship between the flow request stored in the preset central server and the server for forwarding the flow request, the flow request ID carried in the flow request and the calling time sequence of the flow request.
Further, the first system and the second system are systems of different development language architectures.
Further, the first system is a merchant terminal system, and the second system is a user terminal system.
Further, the preset page is a front-end page.
Further, the first system comprises more than 3 servers, the second system comprises more than 3 servers, and different servers are used for providing different services.
According to the technical scheme, the inter-system integration test method provided by the invention comprises the steps that firstly, the agent programs are respectively deployed on the servers of the first system and the second system, and the agent programs are used for forwarding all flow requests entering and exiting the corresponding server processes to the preset central server; for service call among servers in a first system, among servers in a second system, or among servers in the first system and the second system, in each complete call flow, the earliest caller adds a corresponding flow request ID in a flow request, and each level of servers in the whole call flow also carry the flow request ID when carrying out data transmission; then the preset central server receives the traffic requests forwarded by the agents deployed on the servers of the first system and the second system and correspondingly stores the received traffic requests and the servers forwarding the traffic requests; and finally, displaying the calling relationship and calling data among the servers involved in each complete calling process on a preset page according to the corresponding relationship between the flow request stored in the preset central server and the server for forwarding the flow request, the flow request ID carried in the flow request and the calling time sequence of the flow request. Therefore, the inter-system integration test method provided by the invention can realize the tracking and page display of each service call in the two systems, thereby effectively shortening the problem troubleshooting time in the integration test.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of a method for testing integration between systems according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of service invocation between a merchant-side and a user-side heterogeneous system;
fig. 3 is a schematic diagram illustrating a method for testing inter-system integration according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
An embodiment of the present invention provides an intersystem integration test method, and referring to fig. 1, the method includes the following steps:
step 101: respectively deploying agent programs on each server of the first system and the second system, wherein the agent programs are used for forwarding all flow requests entering and exiting the corresponding server processes to a preset central server; for service invocation among servers in a first system, among servers in a second system, or among servers in the first system and the second system, in each complete invocation flow, the earliest invoker adds a corresponding flow request ID into a flow request, and each level of servers in the whole invocation flow also carry the flow request ID when data transmission is carried out.
In this step, it can be understood that the traffic request ID carried in each traffic request is an ID that can uniquely represent the traffic request.
Step 102: the preset center server receives the traffic requests forwarded by the agents deployed on the servers of the first system and the second system and correspondingly stores the received traffic requests and the servers forwarding the traffic requests.
Step 103: and displaying the calling relationship and calling data among the servers involved in each complete calling flow on a preset page according to the corresponding relationship between the flow request stored in the preset central server and the server for forwarding the flow request, the flow request ID carried in the flow request and the calling time sequence of the flow request.
In this step, the preset page may be a front-end page.
It can be understood that, during the front-end service test, by displaying the calling relationship and data condition among the system servers, once a defect is found in the test process, the front-end service tester can quickly locate and check which services (services provided by the servers) are caused by the fault, thereby greatly reducing the communication cost of each service line tester and research and development personnel, and improving the integration test efficiency among the heterogeneous systems.
As can be seen from the foregoing technical solutions, in the inter-system integration test method provided in this embodiment, first, an agent is respectively deployed on each server of the first system and the second system, where the agent is used to forward all traffic requests coming in and going out of a corresponding server process to a preset central server; for service call among servers in a first system, among servers in a second system, or among servers in the first system and the second system, in each complete call flow, the earliest caller adds a corresponding flow request ID in a flow request, and each level of servers in the whole call flow also carry the flow request ID when carrying out data transmission; then the preset central server receives the traffic requests forwarded by the agents deployed on the servers of the first system and the second system and correspondingly stores the received traffic requests and the servers forwarding the traffic requests; and finally, displaying the calling relationship and calling data among the servers involved in each complete calling process on a preset page according to the corresponding relationship between the flow request stored in the preset central server and the server for forwarding the flow request, the flow request ID carried in the flow request and the calling time sequence of the flow request. Therefore, the inter-system integration test method provided by the embodiment can realize the tracking and page display of each service call in the two systems, thereby effectively shortening the problem troubleshooting time in the integration test.
It will be appreciated that in two systems developed using the same language, it is also relatively simple to expose multiple levels of system call relationships and data through unified definition of some frameworks, such as through logs and the like. However, for two systems developed in different languages, the multi-level system calling relationship and data cannot be or are inconvenient to be displayed through logs and the like, and the inter-system integration testing method provided by the invention does not need to unify the logs of the systems through the bottom-layer flow forwarding and the unique ID transmission method in the process level, so that the method is also suitable for system testing of different development language architectures.
As shown in fig. 2, the first system is a merchant end system and the second system is a user end system. The method for testing the inter-system integration provided by the present embodiment is described in detail below by taking the class of micro services shown in fig. 2 as an example.
Referring to fig. 2, a typical call process is as follows:
1. the merchant terminal personnel initiates operation to generate calling of the service A;
2. the service A generates an event, such as a database change operation, and triggers the service B;
3. the service B receives the event, sends out the call to the service C, processes the returned data of the service C, and transmits the data to the user side through the message system;
4. e, the service consumes and processes the message, possibly initiating a client database operation;
5. and the user side personnel access the D service through the front end to obtain the latest data synchronized from the merchant side.
For the integrated test of the two systems of the merchant end and the user end, referring to fig. 3, the implementation scheme is as follows:
and realizing a resident agent program, deploying on the 5 service hosts (A, B, C, D and E), copying the request traffic of all the access corresponding service processes, and forwarding the request to a central server.
And secondly, realizing a central server service, receiving the flow requests forwarded by the host programs in the step 1, and storing the data in the requests.
And thirdly, realizing a front-end page, and counting and displaying the storage data in the step 2.
When each service is called, the earliest calling party adds a unique ID in a request in a calling process, and each level of service carries the unique ID when data is transmitted; the unique ID is also carried in the message at the time of message delivery in the heterogeneous system. All the service access requests forwarded by the agent program on the host where the services at all levels are located are collected in the stored data in the storage area 2, and the calling relation and the data in one calling can be restored on the page in the storage area 3 according to the unique ID and the calling time sequence, so that the calling is tracked, the problems found in the joint debugging test can be conveniently located, and the requirements of monitoring part of the services can be met.
Therefore, the inter-system integration test method provided by the embodiment can meet the requirement of integration test. Meanwhile, the monitoring requirements of partial services and services can be met by slight expansion, and the automation requirements in back-end data testing can also be met
It can be understood that, currently, the mainstream integrated test scheme often involves multi-system joint debugging and participation of multiple personnel, and is time-consuming and labor-consuming in positioning and troubleshooting, and the problem troubleshooting time in the integrated test can be effectively shortened by realizing the tracking and page display of each service invocation in the embodiment of the invention. In addition, the test method provided by the embodiment of the invention can also complete the test automation in the back-end service, and improve the working efficiency of back-end testers.
The above examples are only for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (5)
1. An inter-system integration test method, comprising:
respectively deploying agent programs on each server of the first system and the second system, wherein the agent programs are used for forwarding all flow requests entering and exiting the corresponding server processes to a preset central server; for service call among servers in a first system, among servers in a second system, or among servers in the first system and the second system, in each complete call flow, the earliest caller adds a corresponding flow request ID in a flow request, and each level of servers in the whole call flow also carry the flow request ID when carrying out data transmission; the flow request ID carried in each flow request is the unique ID capable of representing the flow request;
the preset central server receives flow requests forwarded by the agents deployed on the servers of the first system and the second system and correspondingly stores the received flow requests and the servers forwarding the flow requests;
and displaying the calling relationship and calling data among the servers involved in each complete calling flow on a preset page according to the corresponding relationship between the flow request stored in the preset central server and the server for forwarding the flow request, the flow request ID carried in the flow request and the calling time sequence of the flow request.
2. The method of claim 1, wherein the first system and the second system are systems of different development language architectures.
3. The method of claim 1, wherein the first system is a merchant end system and the second system is a user end system.
4. The method of claim 1, wherein the default page is a front page.
5. The method of claim 1, wherein the first system comprises more than 3 servers and the second system comprises more than 3 servers, and wherein different servers are configured to provide different services.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810024267.2A CN108388501B (en) | 2018-01-10 | 2018-01-10 | Intersystem integration test method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810024267.2A CN108388501B (en) | 2018-01-10 | 2018-01-10 | Intersystem integration test method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108388501A CN108388501A (en) | 2018-08-10 |
| CN108388501B true CN108388501B (en) | 2021-09-17 |
Family
ID=63077089
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810024267.2A Active CN108388501B (en) | 2018-01-10 | 2018-01-10 | Intersystem integration test method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108388501B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112905486B (en) * | 2021-03-26 | 2022-07-08 | 建信金融科技有限责任公司 | Service integration test method, device and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101140541A (en) * | 2007-09-29 | 2008-03-12 | 中兴通讯股份有限公司 | Integration test system of distributed software system and method thereof |
| CN102694866A (en) * | 2012-06-01 | 2012-09-26 | 北京首钢自动化信息技术有限公司 | Service request broker system in distributed network environment |
| CN106489251A (en) * | 2015-12-21 | 2017-03-08 | 华为技术有限公司 | The methods, devices and systems that applied topology relation finds |
| CN106855795A (en) * | 2015-12-08 | 2017-06-16 | 上海复亚通信科技有限公司 | A kind of Proxy program operated between App and server software |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7197559B2 (en) * | 2001-05-09 | 2007-03-27 | Mercury Interactive Corporation | Transaction breakdown feature to facilitate analysis of end user performance of a server system |
| US7631354B2 (en) * | 2004-12-30 | 2009-12-08 | Intel Corporation | System security agent authentication and alert distribution |
-
2018
- 2018-01-10 CN CN201810024267.2A patent/CN108388501B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101140541A (en) * | 2007-09-29 | 2008-03-12 | 中兴通讯股份有限公司 | Integration test system of distributed software system and method thereof |
| CN102694866A (en) * | 2012-06-01 | 2012-09-26 | 北京首钢自动化信息技术有限公司 | Service request broker system in distributed network environment |
| CN106855795A (en) * | 2015-12-08 | 2017-06-16 | 上海复亚通信科技有限公司 | A kind of Proxy program operated between App and server software |
| CN106489251A (en) * | 2015-12-21 | 2017-03-08 | 华为技术有限公司 | The methods, devices and systems that applied topology relation finds |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108388501A (en) | 2018-08-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9172593B2 (en) | System and method for identifying problems on a network | |
| CN110069354A (en) | The full link trace method of micro services and micro services framework | |
| CN110730246A (en) | Distributed link tracking method under micro-service architecture | |
| WO2021129008A1 (en) | Service invocation method, apparatus and device, and medium | |
| CN109408310B (en) | Debugging method of server, server and readable storage medium | |
| CN109495655B (en) | Call center agent line testing method and device, electronic equipment and storage medium | |
| CN110457176B (en) | Monitoring method and device for distributed system, storage medium and electronic equipment | |
| CN110659109A (en) | Openstack cluster virtual machine monitoring system and method | |
| CN104090839A (en) | Simulation test method and device for abnormal scene | |
| CN110730472B (en) | Communication certificate state detection method and server | |
| CN110018956B (en) | Application debugging method and related device | |
| CN112291082B (en) | Disaster recovery processing method, terminal and storage medium for machine room | |
| CN108388501B (en) | Intersystem integration test method | |
| CN116016123A (en) | Fault processing method, device, equipment and medium | |
| CN113179295A (en) | Message processing method and device | |
| CN111639086B (en) | Data reconciliation method, device, equipment and storage medium | |
| CN109587349B (en) | Multimedia agent line testing method and device, electronic equipment and storage medium | |
| CN111245939B (en) | Data synchronization method, device and system | |
| CN105025179A (en) | Method and system for monitoring service agents of call center | |
| CN107291575B (en) | Processing method and equipment for data center fault | |
| CN109743367B (en) | Service processing method and device, electronic equipment and readable storage medium | |
| CN108154343B (en) | Emergency processing method and system for enterprise-level information system | |
| CN109672788B (en) | Incoming call monitoring method and device for user, electronic equipment and storage medium | |
| US11036624B2 (en) | Self healing software utilizing regression test fingerprints | |
| CN112650815A (en) | Method and device for synchronizing environmental data, storage medium and electronic device |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 100085 Floor 101 102-1, No. 35 Building, No. 2 Hospital, Xierqi West Road, Haidian District, Beijing Applicant after: Seashell Housing (Beijing) Technology Co.,Ltd. Address before: 100085 Floor 101 102-1, No. 35 Building, No. 2 Hospital, Xierqi West Road, Haidian District, Beijing Applicant before: LIANJIA(BEIJING) TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |