Test environment view generation method and device

Abstract

The invention discloses a test environment view generation method and device, and the method comprises the steps: obtaining a mapping relation among a plurality of system deployment resources for each system in a test environment; the mapping relationship among the plurality of system deployment resources is used for recording the connection relationship between every two system deployment resources; constructing a longitudinal view structure of the system based on the mapping relationship among the plurality of system deployment resources; constructing a transverse view structure among the plurality of systems based on the transaction path between the micro-services corresponding to each system; and based on the longitudinal view structures of the systems, the transverse view structures among the plurality of systems and the performance indexes corresponding to the plurality of system deployment resources, determining an overall associated view of the test environment. According to the method, the overall association view of the test environment can be determined, so that the association relationship among the systems and the corresponding complete and detailed related test data are obtained from the overall association view, and the test efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method and apparatus for generating a test environment view. Background Technology

[0002] With the development of information technology, the scale of information system construction is gradually expanding. At the same time, the relationships between the testing environments of various systems are becoming more complex. This can easily lead to situations where the relationships between various systems and the complete and detailed relevant test data for each system cannot be obtained, resulting in insufficient testing or testing failures, poor testing efficiency, and ultimately affecting production.

[0003] Currently, network packet capture is commonly used when constructing a view of the relationship between test environments, and transaction tracking and analysis are performed using network packet capture tools. However, network packet capture tools can only analyze a single target system. That is, network packet capture tools cannot reveal the relationship between various information systems, nor can they obtain complete and detailed relevant test data, thus failing to solve the aforementioned problems. Summary of the Invention

[0004] In view of this, embodiments of this application provide a test environment view generation method and apparatus, which aim to determine the overall relational view of the test environment, so as to know the relational relationship between various systems and their corresponding complete and detailed related test data, thereby improving test efficiency.

[0005] In a first aspect, embodiments of this application provide a method for generating a test environment view, the method comprising:

[0006] For each system in the test environment, obtain the mapping relationship between multiple system deployment resources; the mapping relationship between multiple system deployment resources is used to record the connection relationship between every two system deployment resources.

[0007] Based on the mapping relationship between the resources deployed in the multiple systems, a vertical view structure of the system is constructed.

[0008] Based on the transaction paths between the microservices corresponding to each system, a horizontal view structure is constructed between multiple systems;

[0009] Based on the vertical view structure of the system, the horizontal view structure among the multiple systems, and the performance indicators corresponding to the deployment resources of each of the multiple systems, the overall related view of the test environment is determined.

[0010] Secondly, embodiments of this application provide a test environment view generation apparatus, the apparatus comprising:

[0011] The acquisition module is used to acquire the mapping relationship between multiple system deployment resources for each system in the test environment; the mapping relationship between the multiple system deployment resources is used to record the connection relationship between every two system deployment resources;

[0012] The first construction module is used to construct the vertical view structure of the system based on the mapping relationship between the multiple system deployment resources;

[0013] The second building module is used to build a horizontal view structure between multiple systems based on the transaction paths between the microservices corresponding to each system.

[0014] The determination module is used to determine the overall associated view of the test environment based on the vertical view structure of the system, the horizontal view structure among the multiple systems, and the performance indicators corresponding to the deployment resources of the multiple systems.

[0015] Thirdly, embodiments of this application provide a test environment view generation device, the device comprising:

[0016] Memory, used to store computer programs;

[0017] A processor is configured to execute the computer program to cause the device to perform the test environment view generation method described in the first aspect above.

[0018] Fourthly, embodiments of this application provide a computer storage medium on which a computer program is stored. When the computer program is run, a device running the computer program implements the test environment view generation method described in the first aspect above.

[0019] Compared with the prior art, the embodiments of this application have the following beneficial effects:

[0020] This application provides a method for generating a test environment view, which innovatively proposes a scheme for constructing an overall relational view of the various systems involved in the test environment. The method includes: for each system in the test environment, obtaining the mapping relationships between multiple system deployment resources, which are used to record the connection relationships between every two system deployment resources. Next, based on the mapping relationships between the multiple system deployment resources, a vertical view structure of the system can be constructed; that is, based on the connection relationships between every two system deployment resources, the top-to-bottom connection relationships of the various system deployment resources included in the system can be determined, thereby determining the vertical view structure of each system. Then, based on the transaction paths between the microservices corresponding to each system, a horizontal view structure between the multiple systems can be constructed; that is, based on the transaction paths between the microservices corresponding to each system, the relational relationships between the microservices of the various systems that generate interactions can be linked, thereby constructing a horizontal view structure representing the interaction relationships between multiple systems. Finally, based on the vertical view structure of each system, the horizontal view structure between multiple systems, and the performance indicators corresponding to the deployment resources of each system, an overall relational view of the test environment can be constructed. As can be seen, the horizontal view structure between multiple systems can reveal the relationships between various information involved in the test environment. The vertical view structure of each system and the performance indicators corresponding to the deployment resources of multiple systems within the system can reveal the complete and detailed relevant test data for each system. Therefore, based on the overall relational view of the test environment, not only can the relationships between various systems be known, but also the complete and detailed relevant test data for each system can be obtained. This avoids the problem of insufficient testing or inability to conduct tests normally due to a lack of relevant test data, thereby improving testing efficiency and reducing the impact on final production issues. Attached Figure Description

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

[0022] Figure 1 This is a schematic diagram illustrating an application scenario of a test environment view generation method provided in an embodiment of this application.

[0023] Figure 2 A flowchart illustrating a method for generating a test environment view, as provided in an embodiment of this application;

[0024] Figure 3A schematic diagram of the longitudinal view structure provided in the embodiments of this application;

[0025] Figure 4 A schematic diagram of the horizontal view structure provided in the embodiments of this application;

[0026] Figure 5 A schematic diagram of the overall associated view provided for an embodiment of this application;

[0027] Figure 6 This is a schematic diagram of a test environment view generation device provided in an embodiment of this application. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0029] In the fintech sector, as the scale of information system construction expands, the relationships between the testing environments of various systems become increasingly complex. For example, R&D resources have evolved from Infrastructure as a Service (IaaS) to Platform as a Service (PaaS), deployment environments have shifted from cloud to on-premises, and application deployment methods have evolved from manual to automated deployment via DevOps pipelines. Furthermore, numerous tools within organizations are used for application deployment, further tightening the connections between information systems. However, during development and testing, the complex inter-system communication relationships can lead to situations where the relationships between systems and their corresponding complete and detailed test data are not readily available. This can result in insufficient testing or testing failures, leading to poor testing efficiency and ultimately impacting production.

[0030] Currently, network packet capture tools are primarily used to track and analyze transactions on on-premises IaaS resources, such as virtual machines running Linux or Windows. These tools intercept and view network data packets, capturing and disassembling them layer by layer. Specifically, a packet capture tool can be bound to a specific network interface to begin detecting data packets flowing through that interface. As packets pass through, the tool captures and stores them on the local computer, allowing for detailed analysis of the captured packets, including protocols, source and destination addresses, port numbers, and included data. However, network packet capture tools can only analyze a single target system; they cannot reveal the relationships between different information systems or obtain complete and detailed related test data, thus failing to address the aforementioned issues.

[0031] To address the aforementioned issues, this application provides a test environment view generation method. This method determines the top-to-bottom connection relationships of all system deployment resources within a system based on the connection relationships between every two system deployment resources, thus establishing the vertical view structure of each system. Then, based on the transaction paths between the microservices corresponding to each system, the relationships between the microservices of the interacting systems can be linked, constructing a horizontal view structure representing the interaction relationships between multiple systems. Finally, the horizontal view structure of multiple systems reveals the relationships between various pieces of information involved in the test environment. Furthermore, the vertical view structure of each system and the performance metrics corresponding to the deployment resources within each system provide complete and detailed relevant test data for each system. Therefore, based on the overall relational view of the test environment, not only are the relationships between systems revealed, but also the complete and detailed relevant test data for each system is available. This avoids the problem of insufficient testing or testing failure due to a lack of relevant test data, thereby improving testing efficiency and reducing the impact on final production issues.

[0032] For example, one scenario in the embodiments of this application can be applied to, such as Figure 1The scenario shown includes a database 101 and a terminal device 102. Database 101 stores mapping relationships between multiple system deployment resources and transaction paths between microservices corresponding to each system. Terminal device 102, using the implementation method provided in this application, obtains the mapping relationships between multiple system deployment resources from database 101 and constructs a vertical view structure of the system based on these relationships. It can also obtain the transaction paths between microservices corresponding to each system to construct a horizontal view structure between multiple systems. Finally, based on the vertical view structure of each system, the horizontal view structure between multiple systems, and the performance indicators corresponding to the deployment resources of each system, the overall associated view of the test environment is determined.

[0033] First, in the above application scenarios, although the action description of the implementation method provided in this application is executed by the terminal device 102, the implementation method of this application is not limited in terms of the execution subject, as long as the actions disclosed in the implementation method provided in this application are executed.

[0034] Secondly, the above scenario is only one example provided by the embodiments of this application, and the embodiments of this application are not limited to this scenario.

[0035] The following detailed description, in conjunction with the accompanying drawings and embodiments, illustrates the specific implementation of the test environment view generation method and apparatus in this application.

[0036] See Figure 2 This figure is a flowchart of a test environment view generation method provided in an embodiment of this application, combined with... Figure 2 As shown, it can specifically include:

[0037] S201: For each system in the test environment, obtain the mapping relationship between multiple system deployment resources; the mapping relationship between multiple system deployment resources is used to record the connection relationship between every two system deployment resources.

[0038] The system in the test environment refers to the system used for testing. For example, the system in the test environment may include the consumer system, the target system, and the service system. Taking the test of the transfer business in mobile banking as an example, the consumer system can call the target system, and the target system can also call the service system. The consumer system can be the mobile banking, the target system can be the transfer module, and the service system can be the accounting module called by the transfer module, etc. This application does not specifically limit the system in the test environment.

[0039] System deployment resources refer to the computing resources required for system operation. For example, system deployment resources may include, but are not limited to, servers, switches, routers, storage devices, container clouds, middleware, load balancers, domain names, container cloud namespaces, and corresponding virtual machines and physical machines. This application does not specifically limit the system deployment resources.

[0040] The mapping relationship between multiple system deployment resources is used to record the connection relationship between every two system deployment resources. That is, through the mapping relationship between multiple system deployment resources, the top-down connection relationship of the various system deployment resources included in a system can be obtained. Specifically, taking the above-mentioned multiple system deployment resources as an example, the mapping relationship between multiple system deployment resources can include a first mapping relationship for recording the connection relationship between domain name and load balancer, a second mapping relationship for recording the connection relationship between load balancer and container cloud ingress, a third mapping relationship for recording the connection relationship between container cloud ingress and container cloud namespace, and the connection relationship between container cloud namespace and database load balancer, and a fourth mapping relationship for recording the connection relationship between database load balancer and database node.

[0041] For example, the first mapping relationship can be a domain name mapping relationship relying on Domain Name System (DNS) records. Given a domain name, the load balancer corresponding to that domain name can be determined based on this first mapping relationship. The second mapping relationship can be a mapping relationship relying on Virtual Server Pool Members (VS-Poolmember) records on the load balancer server. Given a load balancer, the container cloud ingress / server corresponding to that load balancer can be determined based on this second mapping relationship. The third mapping relationship can be determined based on the container cloud configuration file. This configuration file can include the container cloud namespace corresponding to the container cloud ingress, and also the database load balancer corresponding to the container cloud namespace. This container cloud configuration file can be a markup language (YAML) file. The third mapping relationship can be extracted from the container cloud configuration file through automated parameter extraction. That is, given a container cloud ingress, the container cloud namespace corresponding to that ingress can be determined based on this third mapping relationship. Then, given the container cloud namespace, the database load balancer corresponding to that container cloud namespace can be determined based on this third mapping relationship. The fourth mapping relationship can be the mapping relationship of VS-Poolmember recorded by the database load balancer server. When the database load balancer is determined, the database node corresponding to the database load balancer can be determined based on the fourth mapping relationship.

[0042] For example, for each system in the test environment, the mapping relationships between multiple system deployment resources can be obtained from the test environment deployment information recorded in the R&D resource product repository. The R&D resource product repository refers to a product repository used to record relevant information about the runtime deployment of various systems in various environments (such as test environments, development environments, and production environments). In other words, the mapping relationships between multiple system deployment resources can be obtained from the test environment-related deployment information (i.e., the relevant data on the runtime deployment of various systems in the test environment) recorded in the R&D resource product repository. For example, the repository data model included in the R&D resource product repository stores the mapping relationships between multiple system deployment resources. Based on the repository data model, the mapping relationships between multiple system deployment resources can be extracted. Furthermore, the various environments recorded in the aforementioned R&D resource product repository are collections of various technology stacks.

[0043] S202: Based on the mapping relationship between resources deployed in multiple systems, construct the vertical view structure of the system.

[0044] The vertical view structure of a system refers to the logical architecture of the test environment when testing the system, that is, the physical connection relationship of the resources deployed in various systems under the test environment, or the calling relationship between software components (such as front-end-back-end application programming interface (API)-database-server load balancing, etc.).

[0045] When constructing the vertical view structure of the system, that is, constructing the logical architecture of multiple system deployment resources in the test environment, the logical architecture usually takes the domain name or load balancer as the entry point, followed by the content on the cloud (container cloud) or on-premises (server), then reaches the database layer, and finally performs the storage process.

[0046] For each system, based on the mapping relationships between resources deployed across multiple systems—that is, based on the connection relationships between every two system deployment resources—the top-to-bottom connection relationships of the various system deployment resources included in the test environment can be determined. For example, by integrating the first, second, third, and fourth mapping relationships, the vertical view structure of the system can be constructed. (See reference...) Figure 3 , Figure 3The schematic diagram of the vertical view structure provided in this application embodiment shows that the domain name of the tested system can be obtained from the R&D resource product repository. Once the system's domain name is determined, the load balancer corresponding to that domain name can be determined based on a first mapping relationship. Next, based on a second mapping relationship, the container cloud entry point corresponding to that load balancer can be determined. Based on a third mapping relationship, the container cloud namespace corresponding to that container cloud entry point can be determined. Based on the third mapping relationship, the database load balancer corresponding to that container cloud namespace can also be determined. Finally, based on a fourth mapping relationship, the database node corresponding to that database load balancer can be determined, and the storage address can be determined based on the database node. Thus, following the above method, a vertical view corresponding to each system can be constructed. It can be seen that by continuously drilling down the mapping relationships between the deployment resources of multiple systems, a visual vertical view of the system can ultimately be observed.

[0047] S203: Based on the transaction paths between the microservices corresponding to each system, construct a horizontal view structure between multiple systems.

[0048] Each system's corresponding microservice refers to an independent, deployable small service within the system. For example, taking the target system as an example, the corresponding microservices in the target system may include transfer services, payment services, wealth management services, and loan services, etc. This application does not specifically limit the corresponding microservices for each system.

[0049] The transaction path between the microservices corresponding to each system is used to indicate the path of the business process in each system. That is, the transaction path can show how the system deployment resources support the operation of the business, such as "order system - payment interface - server cluster" in the XX platform.

[0050] For example, transaction paths between microservices in each system can be determined based on the interface call relationships and routing links between microservices in multiple systems, as well as the transaction statistics for each microservice. For instance, a transaction flow between multiple systems in a test environment can be constructed based on the interface call relationships and routing links between microservices in multiple systems. Furthermore, transaction statistics for each microservice can be populated into the determined transaction flow. These statistics indicate whether a transaction was successful and the transaction volume, thus determining the success and volume of transactions for each microservice and constructing a complete transaction path between microservices in each system.

[0051] For example, for each system, the hostname command can be executed in the container group (pod) by relying on the cloud-native management platform (a management platform for processing cloud data) or a self-developed agent component to obtain the name of the microservice (deployment controller name) and subsequent string (image version) where the pod is located. In addition, real-time transaction statistics of the microservice can be collected.

[0052] Furthermore, taking multiple systems as consumer systems, target systems, and service systems as an example, an interface management platform (a platform used to manage interface call relationships between multiple systems) can be used to obtain the interface call relationships and routing links between the corresponding microservices of each system. For example, the interface management platform can first determine the interface call relationships and routing links between the microservices corresponding to the consumer system and the microservices corresponding to the target system, and then determine the interface call relationships and routing links between the microservices corresponding to the target system and the microservices corresponding to the service system.

[0053] Finally, by integrating the transaction statistics of the microservices corresponding to each system, the interface call relationships and routing links between the microservices corresponding to multiple systems, the transaction paths between the microservices corresponding to each system can be determined.

[0054] By identifying the transaction paths between the microservices corresponding to each system, a lateral view structure can be constructed across multiple systems. This lateral view structure refers to the relationships between the microservices of the various systems involved in the overall test environment. For example, after determining the transaction paths between the microservices corresponding to each system, these paths can be integrated within the overall test environment to form a lateral observation mesh, serving as the lateral view structure. Furthermore, different transaction orders generated by microservices can be identified using transaction codes.

[0055] For reference Figure 4 , Figure 4 This is a schematic diagram of the horizontal view structure provided in the embodiments of this application. The target system in the overall test environment may include microservice 1, microservice 2 and microservice 3. Taking the transaction path of microservice 1 as an example, the transaction order generated by microservice 1 can be indicated by transaction code 1. Furthermore, the transaction path of microservice 1 is: microservice 1 - service provider system - domain name or service balancer in the service provider system - microservice 1 in the service provider system - routing link 1 corresponding to the first transaction order identified by transaction code 1, routing link 2 corresponding to the second transaction order identified by transaction code 2 and routing link 3 corresponding to the third transaction order identified by transaction code 3.

[0056] S204: Based on the vertical view structure of the system, the horizontal view structure between multiple systems, and the performance indicators corresponding to the deployment resources of multiple systems, determine the overall relational view of the test environment.

[0057] The performance metrics corresponding to system deployment resources are used to indicate the performance changes of system deployment resources during the testing process. For example, the performance metrics corresponding to multiple system deployment resources may include, but are not limited to, the CPU, memory, and disk usage of IaaS resources, the CPU and memory usage of PaaS resources, the running status of microservice Pods, the version information of the consumer system, the version information of the service system, the version of the program deployed in the current test environment, and whether the microservices in the service system are running stably.

[0058] After determining the vertical view structure corresponding to each system and the horizontal view structure between multiple systems, an overall relational view of the test environment can be integrated based on these two. Furthermore, real-time performance indicators of the resources deployed in each system can be added to the overall relational view to enrich the ability of the overall relational view to observe resource usage in real time.

[0059] In addition, a dynamic view drawing tool can be used to draw and display the overall relational view of the test environment, so as to ensure that the resource usage in the overall relational view can be automatically synchronized with resource changes, and to avoid the static relational diagram not conforming to the actual operation.

[0060] For reference Figure 5 , Figure 5 A schematic diagram of the overall associated view provided for embodiments of this application, such as... Figure 5 As shown, the horizontal view structure allows you to view the overall transaction path, that is, the transaction paths between the various microservices in the consumer system, the various microservices in the target system, and the various microservices in the service system. The vertical view structure allows you to view the microservices included in each system within the overall test environment. Furthermore, by clicking on a specific system, you can view the top-down connectivity of the various system deployment resources within that system. Additionally, you can view the real-time performance metrics corresponding to the deployment resources of multiple systems within the system.

[0061] In this way, by providing a holistic view of the test environment, the complex resource network operation within the test environment can be transformed into an easily understandable "digital map." This enables financial institutions to create and display viewable diagrams of test environment relationships with minimal resource consumption, thereby improving the efficiency and accuracy of information technology (IT) management and decision-making. Furthermore, this holistic view allows for a more accurate, comprehensive, and concrete display of the overall test environment, facilitating more precise use and analysis of the test environment and preventing confusion from impacting final production.

[0062] In this application embodiment, the method innovatively proposes a scheme for constructing an overall relational view of the various systems involved in the test environment. This method can reveal the relationships between various pieces of information involved in the test environment through the horizontal view structure between multiple systems. Through the vertical view structure of each system and the performance indicators corresponding to the resources deployed in each system, complete and detailed relevant test data for each system can be obtained. Therefore, based on the overall relational view of the test environment, not only can the relationships between various systems be understood, but also the complete and detailed relevant test data for each system can be obtained. This avoids the problem of insufficient testing or inability to conduct tests normally due to a lack of relevant test data, thereby improving testing efficiency and reducing the impact on final production issues.

[0063] The above describes some specific implementations of the test environment view generation method provided in this application. Based on this, this application also provides a corresponding apparatus. The apparatus provided in this application will be described below from the perspective of functional modularity.

[0064] See Figure 6 The figure is a schematic diagram of a test environment view generation device 600 provided in an embodiment of this application. The device 600 may include:

[0065] The acquisition module 601 is used to acquire the mapping relationship between multiple system deployment resources for each system in the test environment; the mapping relationship between the multiple system deployment resources is used to record the connection relationship between every two system deployment resources;

[0066] The first construction module 602 is used to construct the vertical view structure of the system based on the mapping relationship between the multiple system deployment resources;

[0067] The second construction module 603 is used to construct a horizontal view structure between multiple systems based on the transaction paths between the microservices corresponding to each system.

[0068] The determination module 604 is used to determine the overall associated view of the test environment based on the vertical view structure of the system, the horizontal view structure among the multiple systems, and the performance indicators corresponding to the deployment resources of the multiple systems.

[0069] In one possible implementation, the acquisition module 601 is specifically used for:

[0070] Based on the test environment deployment information recorded in the R&D resource product warehouse, obtain the mapping relationship between the deployment resources of the multiple systems.

[0071] In one possible implementation, the mapping relationship between the multiple system deployment resources includes a first mapping relationship for recording the connection relationship between domain names and load balancers, a second mapping relationship for recording the connection relationship between the load balancer and the container cloud ingress, a third mapping relationship for recording the connection relationship between the container cloud ingress and the container cloud namespace, and the connection relationship between the container cloud namespace and the database load balancer, and a fourth mapping relationship for recording the connection relationship between the database load balancer and the database node; the first construction module 602 is specifically used for:

[0072] The vertical view structure of the system is constructed by integrating the first mapping relationship, the second mapping relationship, the third mapping relationship, and the fourth mapping relationship.

[0073] In one possible implementation, the apparatus includes the following units for determining transaction paths between the microservices corresponding to each system:

[0074] The first determining unit is used to determine the transaction path between the microservices corresponding to each system based on the interface call relationship and routing link between the microservices corresponding to each of the multiple systems, as well as the transaction statistics information corresponding to the microservices corresponding to each system.

[0075] In one possible implementation, the first determining unit is specifically used for:

[0076] For each system, obtain the corresponding microservice transaction statistics;

[0077] The interface management platform is used to obtain the interface call relationships and routing links between the microservices of multiple systems.

[0078] By combining the transaction statistics of the microservices corresponding to each system, the interface call relationships and routing links between the microservices corresponding to multiple systems, the transaction paths between the microservices corresponding to each system are determined.

[0079] In one possible implementation, the device further includes:

[0080] The display module is used to display the overall associated view of the test environment based on the dynamic view drawing tool.

[0081] This application also provides corresponding devices and computer storage media for implementing the solutions provided in this application.

[0082] The device includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to enable the device to perform the test environment view generation method according to any embodiment of this application.

[0083] The computer storage medium stores a computer program. When the code is run, the device running the computer program implements the test environment view generation method described in any embodiment of this application.

[0084] In the embodiments of this application, the terms "first" and "second" (if they exist) are used only as name identifiers and do not represent the order of first and second.

[0085] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the methods of the above embodiments can be implemented by means of software plus a general-purpose hardware platform. Based on this understanding, the technical solution of this application can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as a read-only memory (ROM) / RAM, magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network communication device such as a router) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0086] It should be noted that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments. The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate. The components indicated as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment solution according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0087] The above description is merely one specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for generating a test environment view, characterized in that, The method includes: For each system in the test environment, obtain the mapping relationship between multiple system deployment resources; the mapping relationship between multiple system deployment resources is used to record the connection relationship between every two system deployment resources. Based on the mapping relationship between the resources deployed in the multiple systems, a vertical view structure of the system is constructed. Based on the transaction paths between the microservices corresponding to each system, a horizontal view structure is constructed between multiple systems; Based on the vertical view structure of the system, the horizontal view structure among the multiple systems, and the performance indicators corresponding to the deployment resources of each of the multiple systems, the overall related view of the test environment is determined.

2. The method according to claim 1, characterized in that, The process of obtaining the mapping relationship between multiple system deployment resources includes: Based on the test environment deployment information recorded in the R&D resource product warehouse, obtain the mapping relationship between the deployment resources of the multiple systems.

3. The method according to claim 1, characterized in that, The mapping relationship between the multiple system deployment resources includes a first mapping relationship for recording the connection relationship between domain names and load balancers, a second mapping relationship for recording the connection relationship between the load balancer and the container cloud entry point, a third mapping relationship for recording the connection relationship between the container cloud entry point and the container cloud namespace, and the connection relationship between the container cloud namespace and the database load balancer, and a fourth mapping relationship for recording the connection relationship between the database load balancer and the database node. The construction of the system's vertical view structure based on the mapping relationship between the multiple system deployment resources includes: The vertical view structure of the system is constructed by integrating the first mapping relationship, the second mapping relationship, the third mapping relationship, and the fourth mapping relationship.

4. The method according to claim 1, characterized in that, The transaction paths between the microservices corresponding to each system are determined in the following way: Based on the interface call relationships and routing links between the microservices corresponding to each of the multiple systems, as well as the transaction statistics information corresponding to the microservices corresponding to each system, the transaction paths between the microservices corresponding to each system are determined.

5. The method according to claim 4, characterized in that, The process of determining the transaction path between the microservices of each system based on the interface call relationships and routing links between the microservices of each system, and the transaction statistics information of the microservices of each system, includes: For each system, obtain the corresponding microservice transaction statistics; The interface management platform is used to obtain the interface call relationships and routing links between the microservices of multiple systems. By combining the transaction statistics of the microservices corresponding to each system, the interface call relationships and routing links between the microservices corresponding to multiple systems, the transaction paths between the microservices corresponding to each system are determined.

6. The method according to claim 1, characterized in that, The method further includes: The overall associated view of the test environment is displayed using the dynamic view drawing tool.

7. A test environment view generation device, characterized in that, The device includes: The acquisition module is used to acquire the mapping relationship between multiple system deployment resources for each system in the test environment; the mapping relationship between the multiple system deployment resources is used to record the connection relationship between every two system deployment resources; The first construction module is used to construct the vertical view structure of the system based on the mapping relationship between the multiple system deployment resources; The second building module is used to build a horizontal view structure between multiple systems based on the transaction paths between the microservices corresponding to each system. The determination module is used to determine the overall associated view of the test environment based on the vertical view structure of the system, the horizontal view structure among the multiple systems, and the performance indicators corresponding to the deployment resources of the multiple systems.

8. The apparatus according to claim 7, characterized in that, The acquisition module is specifically used for: Based on the test environment deployment information recorded in the R&D resource product warehouse, obtain the mapping relationship between the deployment resources of the multiple systems.

9. A test environment view generation device, characterized in that, The device includes: Memory, used to store computer programs; A processor for executing the computer program to cause the device to perform the test environment view generation method as described in any one of claims 1 to 6.

10. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, implements the test environment view generation method as described in any one of claims 1 to 6.

Images