Data Processing Method and System for Low-Code Platform

Abstract

The present application provides a data processing method and system for a low-code platform provided by the present application. The method obtains the original program architecture information of the original business process through the component logic layer, generates an original program architecture diagram according to the original program architecture information, then displays the original program architecture diagram in the visual interaction layer, and in response to a component insertion instruction, inserts a new function component into the original program architecture diagram to generate an updated program architecture diagram, so as to generate updated program architecture information, thereby enabling the component logic layer to generate a set of business paths to be tested according to the updated program architecture information and the original program architecture information, and further enabling the test management layer to obtain test cases according to the first business input node, so as to use the test cases to test each business path to be tested in the set of business paths to be tested, thereby improving the automation level of low-code platform testing, reducing manual intervention, and thus improving the efficiency and accuracy of overall development and testing.

Description

Technical Field

[0001] This application relates to data processing technologies, and in particular, to a data processing method and system for a low-code platform. Background Art

[0002] In the current wave of digital transformation, enterprises are urgently in need of quickly responding to market changes, continuously optimizing and innovating business processes to improve operational efficiency and service quality. Due to its long development time, high cost, and slow iteration, the traditional software development model can no longer meet the rapidly changing market demands. Therefore, the Low-Code Development Platform (LCDP) has emerged as an important driving force for enterprise digital transformation.

[0003] This type of platform greatly reduces the technical threshold of application development through a graphical interface, drag-and-drop components, and configuration rather than coding, enabling non-professional developers to quickly build and adjust business applications. Among them, each modification of the business process, whether adding new functions or adjusting existing logic, may affect the stability and performance of the overall system, especially for complex enterprise-level applications. Traditional testing methods often rely on manually writing test scripts, which are time-consuming, laborious, and prone to omissions, and cannot meet the requirements of the rapid iteration of the low-code platform. Summary of the Invention

[0004] This application provides a data processing method and system for a low-code platform to improve the automation level of low-code platform testing, thereby enhancing the efficiency and accuracy of overall software development and testing.

[0005] In a first aspect, this application provides a data processing method for a low-code platform, which is applied to a low-code platform management system. The low-code platform management system includes a visual interaction layer, a component logic layer, and a test management layer. The component logic layer is respectively connected to the visual interaction layer and the test management layer. The method includes:

[0006] The component logic layer obtains the original program architecture information of the original business process and generates an original program architecture diagram according to the original program architecture information. The original program architecture information includes an original function component set and an original topology structure, and the original topology structure is used to establish the topological relationship between each function component in the original function component set;

[0007] The visual interaction layer displays the original program architecture diagram and, in response to a component insertion instruction, inserts a new function component into the original program architecture diagram to generate an updated program architecture diagram;

[0008] The component logic layer generates update program architecture information according to the update program architecture diagram. The update program architecture information includes an update function component set and an update topology structure. The update function component set includes the original function components and the newly added function components. The update topology structure is used to establish the topological relationship between each function component in the update function component set;

[0009] The component logic layer generates a set of business paths to be tested according to the update program architecture information and the original program architecture information. The business paths to be tested in the set of business paths to be tested are the business execution paths from the first business input node to the corresponding first business output node in the update business process corresponding to the update program architecture information;

[0010] The test management layer obtains test cases according to the first business input node, so as to use the test cases to test each business path to be tested in the set of business paths to be tested.

[0011] In this solution, the business process can be easily modified and extended through a graphical interface, and at the same time, the program architecture diagram is automatically updated, ensuring the visual construction and management of business logic. This solution automatically and adaptively generates test paths through the component logic layer, significantly improving the automation level of testing, reducing manual intervention, and thus improving the efficiency and accuracy of overall development and testing.

[0012] Optionally, the component logic layer obtains the original program architecture information of the original business process and generates an original program architecture diagram according to the original program architecture information, including:

[0013] The component logic layer generates an original node set according to the original function component set. One node in the original node set is used to uniquely represent one function component in the original function component set;

[0014] The component logic layer generates the relationship lines for connecting each node in the original node set according to the original topology structure;

[0015] Correspondingly, in response to the component insertion instruction, a newly added function component is inserted into the original program architecture diagram to generate an update program architecture diagram, including:

[0016] The visualization interaction layer inserts a new node at the target position in the original program architecture diagram in response to the component insertion instruction, establishes a first relationship line between the new node and the previous original node and a second relationship line between the new node and the next original node, and deletes the original relationship line, where the new node is used to uniquely represent the newly added functional component, and the original relationship line is the relationship line in the original program architecture diagram that directly connects the previous original node and the next original node;

[0017] The visualization interaction layer updates the original program architecture diagram according to the new node, the first relationship line, and the second relationship line to generate the updated program architecture diagram.

[0018] In this solution, it further refines how to process the original business process information on the low-code platform and convert it into a visual diagram, enabling users to intuitively understand the current business architecture. Through the component insertion instruction, new functions are dynamically added to the existing architecture, and the program architecture diagram is updated immediately. This immediate feedback mechanism greatly enhances the user experience and work efficiency, reducing the time cost of manual adjustment.

[0019] Optionally, the component logic layer generates a set of business paths to be tested according to the updated program architecture information and the original program architecture information, including:

[0020] The component logic layer generates a set of original business paths according to the original program architecture information, and the original business paths in the set of original business paths include the business execution paths from the original business input nodes to the corresponding original business output nodes;

[0021] The component logic layer generates a set of updated business paths according to the updated program architecture information, and the updated business paths in the set of updated business paths include the business execution paths from the updated business input nodes to the corresponding updated business output nodes, where the first business input node is an updated business input node and the first business output node is an updated business output node;

[0022] The component logic layer generates the set of business paths to be tested according to the set of original business paths and the set of updated business paths, where the set of business paths to be tested is the difference set between the set of updated business paths and the set of original business paths.

[0023] In this solution, by comparing the differences in the business processes before and after the update, the new paths that need to be tested are automatically identified. This method of generating the difference set significantly reduces the test scope, has strong pertinence, effectively utilizes the test resources, and improves the pertinence and efficiency of the test.

[0024] Optionally, testing each to-be-tested service path in the to-be-tested service path set by using the test case includes:

[0025] The test management layer generates a to-be-tested service vector set according to the to-be-tested service path set. The to-be-tested service vectors in the to-be-tested service vector set include a start node, an end node, and a vector edge. The direction of the vector edge is used to represent the service flow direction from the start node to the end node;

[0026] The test management layer determines a set of characteristic start nodes according to the to-be-tested service vector set. The set of characteristic start nodes is a set composed of the start nodes corresponding to all the to-be-tested service vectors in the to-be-tested service vector set that use the new node as the end node;

[0027] When the test management layer uses the test case to test the first to-be-tested service path in the to-be-tested service path set, it saves the first test data when the test case is executed to the first characteristic start node in the cache space. The first characteristic start node is a characteristic start node in the set of characteristic start nodes, and the first to-be-tested service path is the to-be-tested service path in the to-be-tested service path set that the test case first executes to the first characteristic start node;

[0028] When the test management layer uses the test case to test the second to-be-tested service path in the to-be-tested service path set, if all the to-be-tested service vectors of the second to-be-tested service path and the first to-be-tested service path before the new node are the same, it calls the first test data from the cache space and uses the first test data as the data input of the target service vector. The target service vector is the to-be-tested service vector with the new node as the start node in the second to-be-tested service path.

[0029] In this solution, the test management layer guides the application of test cases by generating a service vector set. In particular, it reuses test data by identifying a set of characteristic start nodes, which greatly optimizes the test process, avoids duplicate work, reduces the test cost, and improves the coherence and consistency of the test. Especially in the scenario of dealing with a large number of similar paths, the effect is more significant.

[0030] Optionally, after the test management layer determines the set of characteristic start nodes according to the to-be-tested service vector set, it further includes:

[0031] The test management layer determines a first set of characteristic service vectors based on the newly added node and the set of characteristic starting nodes. The starting nodes of the characteristic service vectors in the first set of characteristic service vectors are the characteristic starting nodes in the set of characteristic starting nodes, and the ending nodes are the newly added nodes;

[0032] The test management layer determines a second set of characteristic service vectors based on the newly added node and the set of characteristic ending nodes. The set of characteristic ending nodes is the set composed of the ending nodes corresponding to all the to-be-tested service vectors in the to-be-tested service vector set that use the newly added node as the starting node. The starting nodes of the characteristic service vectors in the second set of characteristic service vectors are the newly added nodes, and the ending nodes are the characteristic ending nodes in the set of characteristic ending nodes;

[0033] Correspondingly, before using the test case to test each to-be-tested service path in the to-be-tested service path set, it further includes:

[0034] The test management layer generates a set of characteristic service vectors based on the first set of characteristic service vectors and the second set of characteristic service vectors, and based on the set of characteristic service vectors;

[0035] The test management layer obtains corresponding test simulation data according to the starting nodes of each characteristic service vector in the set of characteristic service vectors. The test simulation data is used to represent the output data of the corresponding starting node;

[0036] The test management layer uses the first test simulation data to test the first characteristic service vectors in the set of characteristic service vectors to generate a first test result;

[0037] If the first test result is a failure in execution, the to-be-tested service path including the first characteristic service vector is removed from the to-be-tested service path set to generate an updated to-be-tested service path set, so as to use the test case to test each to-be-tested service path in the updated to-be-tested service path set.

[0038] In this solution, by identifying the service vectors directly related to the newly added node, pre-testing is carried out in advance, and the test strategy is dynamically adjusted according to the results. This mechanism can discover potential problems in advance, make timely adjustments, avoid bottlenecks that may be encountered in subsequent tests, and improve the accuracy of testing and the flexibility of the overall test process.

[0039] Optionally, after removing the to-be-tested service path including the first characteristic service vector from the to-be-tested service path set, it further includes:

[0040] The test management layer generates a first partial test report according to the updated program architecture diagram and the to-be-tested service path including the first characteristic service vector;

[0041] The visualization interaction layer displays the first partial test report, and the first partial test report includes the updated program architecture diagram and a test failure identifier displayed on the relationship line corresponding to the first characteristic service vector.

[0042] In this solution, when the test finds that a certain path fails, the system can immediately generate a partial test report and intuitively display the problem. This instant feedback mechanism helps developers quickly locate the problem, accelerates the problem-solving process. At the same time, by marking the test failure points on the updated program architecture diagram, the visibility of the problem is enhanced, and the team collaboration efficiency is improved.

[0043] Optionally, after the visualization interaction layer displays the first partial test report, it further includes:

[0044] The visualization interaction layer responds to the input first instruction, cancels the relationship line corresponding to the first characteristic service vector in the updated program architecture diagram, and restores the starting node of the first characteristic service vector to the topological relationship of the corresponding starting node on the original program architecture diagram;

[0045] The visualization interaction layer responds to the input second instruction and displays the service code of the first characteristic service vector.

[0046] In this solution, at the user interaction level, a way for direct operation according to the test result feedback is provided, such as canceling the failed path, restoring the original configuration or viewing the problem code. Such an interactive design enables users to quickly respond to the test results, flexibly adjust strategies, enhances the practicality of the platform and user dominance, and further improves the efficiency of problem-solving and user satisfaction.

[0047] In a second aspect, the present application provides a low-code platform management system, including: a visualization interaction layer, a component logic layer, and a test management layer, and the component logic layer is respectively connected to the visualization interaction layer and the test management layer;

[0048] The component logic layer obtains the original program architecture information of the original business process, and generates an original program architecture diagram according to the original program architecture information. The original program architecture information includes an original function component set and an original topological structure, and the original topological structure is used to establish the topological relationship between each function component in the original function components;

[0049] The visualization interaction layer displays the original program architecture diagram and, in response to a component insertion instruction, inserts a new functional component into the original program architecture diagram to generate an updated program architecture diagram;

[0050] The component logic layer generates updated program architecture information according to the updated program architecture diagram. The updated program architecture information includes an updated functional component set and an updated topological structure. The updated functional component set includes the original functional components and the new functional components. The updated topological structure is used to establish the topological relationship between each functional component in the updated functional component set;

[0051] The component logic layer generates a set of business paths to be tested according to the updated program architecture information and the original program architecture information. The business paths to be tested in the set of business paths to be tested are the business execution paths from the first business input node to the corresponding first business output node in the updated business process corresponding to the updated program architecture information;

[0052] The test management layer obtains test cases according to the first business input node to test each business path to be tested in the set of business paths to be tested.

[0053] Optionally, the component logic layer generates an original node set according to the original functional component set. One node in the original node set is used to uniquely represent one functional component in the original functional component set;

[0054] The component logic layer generates the relationship lines for connecting each node in the original node set according to the original topological structure;

[0055] The visualization interaction layer, in response to the component insertion instruction, inserts a new node at the target position of the original program architecture diagram, establishes a first relationship line between the new node and the previous original node and a second relationship line between the new node and the next original node, and deletes the original relationship line. The new node is used to uniquely represent the new functional component, and the original relationship line is the relationship line in the original program architecture diagram for directly connecting the previous original node and the next original node;

[0056] The visualization interaction layer updates the original program architecture diagram according to the new node, the first relationship line, and the second relationship line to generate the updated program architecture diagram.

[0057] Optionally, the component logic layer generates an original business path set according to the original program architecture information. The original business paths in the original business path set include the business execution paths from the original business input node to the corresponding original business output node;

[0058] The component logic layer generates an updated service path set according to the updated program architecture information. The updated service paths in the updated service path set include the service execution paths from the corresponding updated service output nodes of the updated service input nodes. The first service input node is an updated service input node, and the first service output node is an updated service output node;

[0059] The component logic layer generates the to-be-tested service path set according to the original service path set and the updated service path set. Wherein, the to-be-tested service path set is the difference set between the updated service path set and the original service path set.

[0060] Optionally, the test management layer generates a to-be-tested service vector set according to the to-be-tested service path set. The to-be-tested service vectors in the to-be-tested service vector set include a start node, an end node, and vector edges. The direction of the vector edge is used to represent the service flow direction from the start node to the end node;

[0061] The test management layer determines a set of characteristic start nodes according to the to-be-tested service vector set. The set of characteristic start nodes is a set composed of the start nodes corresponding to all the to-be-tested service vectors in the to-be-tested service vector set that take the new node as the end node;

[0062] When the test management layer uses the test case to test the first to-be-tested service path in the to-be-tested service path set, it saves the first test data when the test case is executed to the first characteristic start node in the cache space. The first characteristic start node is a characteristic start node in the set of characteristic start nodes, and the first to-be-tested service path is the to-be-tested service path in the to-be-tested service path set corresponding to the first time the test case is executed to the first characteristic start node;

[0063] When the test management layer uses the test case to test the second to-be-tested service path in the to-be-tested service path set, if all the to-be-tested service vectors of the second to-be-tested service path before the new node are the same as those of the first to-be-tested service path, it calls the first test data from the cache space and uses the first test data as the data input of the target service vector. The target service vector is the to-be-tested service vector in the second to-be-tested service path that takes the new node as the start node.

[0064] Optionally, the test management layer determines a first set of characteristic service vectors based on the newly added node and the set of characteristic starting nodes. The starting nodes of the characteristic service vectors in the first set of characteristic service vectors are the characteristic starting nodes in the set of characteristic starting nodes, and the ending nodes are the newly added nodes;

[0065] The test management layer determines a second set of characteristic service vectors based on the newly added node and the set of characteristic ending nodes. The set of characteristic ending nodes is the set composed of the ending nodes corresponding to all the to-be-tested service vectors in the to-be-tested service vector set that use the newly added node as the starting node. The starting nodes of the characteristic service vectors in the second set of characteristic service vectors are the newly added nodes, and the ending nodes are the characteristic ending nodes in the set of characteristic ending nodes;

[0066] The test management layer generates a set of characteristic service vectors based on the first set of characteristic service vectors and the second set of characteristic service vectors, and based on the set of characteristic service vectors

[0067] The test management layer obtains corresponding test simulation data according to the starting nodes of the respective characteristic service vectors in the set of characteristic service vectors. The test simulation data is used to represent the output data of the corresponding starting nodes;

[0068] The test management layer uses the first test simulation data to test the first characteristic service vectors in the set of characteristic service vectors to generate a first test result;

[0069] If the first test result is a failure to execute, the to-be-tested service path including the first characteristic service vector is removed from the set of to-be-tested service paths to generate an updated set of to-be-tested service paths, so as to use the test cases to test each to-be-tested service path in the updated set of to-be-tested service paths.

[0070] Optionally, the test management layer generates a first partial test report based on the updated program architecture diagram and the to-be-tested service path including the first characteristic service vector;

[0071] The visual interaction layer displays the first partial test report. The first partial test report includes the updated program architecture diagram and a test failure identifier displayed on the relationship line corresponding to the first characteristic service vector.

[0072] Optionally, in response to a first instruction input, the visual interaction layer cancels the relationship line corresponding to the first characteristic service vector in the updated program architecture diagram and restores the starting node of the first characteristic service vector to the topological relationship of the corresponding starting node on the original program architecture diagram;

[0073] The visualization interaction layer displays the service code of the first feature service vector in response to the input of the second instruction.

[0074] In a third aspect, the present application provides an electronic device, including:

[0075] a processor; and,

[0076] a memory for storing executable instructions of the processor;

[0077] wherein, the processor is configured to execute any possible method described in the first aspect by executing the executable instructions.

[0078] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement any possible method described in the first aspect.

[0079] The data processing method and system of the low-code platform provided by the present application obtain the original program architecture information of the original business process through the component logic layer, generate an original program architecture diagram according to the original program architecture information, then display the original program architecture diagram in the visualization interaction layer, and in response to the component insertion instruction, insert a new function component into the original program architecture diagram to generate an updated program architecture diagram, so that the component logic layer generates updated program architecture information according to the updated program architecture diagram, thereby enabling the component logic layer to generate a set of business paths to be tested according to the updated program architecture information and the original program architecture information, and further enabling the test management layer to obtain test cases according to the first service input node, so as to use the test cases to test each business path to be tested in the set of business paths to be tested, thereby improving the automation level of the low-code platform test, reducing manual intervention, and thus improving the efficiency and accuracy of overall development and testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0081] Figure 1 is a schematic flowchart of the data processing method of the low-code platform shown according to an exemplary embodiment of the present application;

[0082] Figure 2 is a schematic flowchart of the data processing method of the low-code platform shown according to another exemplary embodiment of the present application;

[0083] Figure 3 is a schematic structural diagram of the low-code platform management system shown according to an exemplary embodiment of the present application;

[0084] Figure 4 It is a schematic structural diagram of an electronic device shown according to an exemplary embodiment of the present application.

[0085] Through the above-mentioned drawings, specific embodiments of the present application have been shown, and more detailed descriptions will be provided hereinafter. These drawings and textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed Embodiments

[0086] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0087] The inventive concept of the embodiments provided by the present application aims to improve the efficiency of software development and testing by efficiently managing business process changes, automatically generating paths to be tested, and optimizing the testing process. The core of this method lies in integrating three key components: a visual interaction layer, a component logic layer, and a test management layer, forming a collaborative system framework. Among them, the component logic layer is connected to the visual interaction layer and the test management layer respectively. Specifically:

[0088] Visual Interaction and Dynamic Architecture Update: Through the visual interaction layer, users can intuitively view and operate the program architecture diagram of the original business process. When a new functional component needs to be added, the system can dynamically insert nodes at the specified position, and at the same time automatically adjust the topological structure between related nodes to generate an updated program architecture diagram. This process simplifies the complexity of traditional programming, enabling non-technical personnel to easily adjust business logic.

[0089] Automatically Identify Paths to be Tested: Based on the program architecture information before and after the update, the component logic layer intelligently generates a set of business paths to be tested. Through comparative analysis, the system can accurately identify the new paths generated due to business process changes, automatically screen out the parts that need to be tested, avoiding the redundant work of full-scale testing, and significantly improving the pertinence and efficiency of testing.

[0090] Test Data Reuse and Optimization: The test management layer introduces the concepts of test cases and business vectors, which can automatically identify feature paths and reuse test data. When there are common parts in the test paths, the system can call the data from previous tests in the cache, reducing the workload of repeated tests and accelerating the test progress. In addition, by pre-testing the business vectors related to newly added nodes and dynamically adjusting the test strategy according to the test results, the accuracy of testing and the ability to locate faults are effectively improved.

[0091] Through the above inventive concept, the following technical effects can be achieved. Specifically:

[0092] Improve development efficiency: Through the visual interaction of the low-code platform, non-programmers can also quickly adjust the business process, shortening the demand response time and improving the development efficiency.

[0093] Optimize test resource allocation: Automatically identify the paths to be tested and generate a differentiated test set, enabling the test resources to be concentrated on the truly changing parts, reducing the unnecessary test burden and saving time and resources.

[0094] Enhance test intelligence: The test data reuse mechanism and pre-test logic not only accelerate the test process but also improve the accuracy of testing, helping to detect and fix problems early.

[0095] Enhance user experience: Intuitive test reports and problem feedback mechanisms, such as directly marking the test failure points on the updated program architecture diagram, facilitate developers to quickly locate and fix errors, optimizing the user experience during development and debugging.

[0096] In summary, based on the inventive concept of the present invention, through a highly integrated data processing method for the low-code platform, the full automation and intelligence from process design, test planning to test execution are achieved, greatly enhancing the efficiency and quality of the software development life cycle.

[0097] Figure 1 It is a schematic flowchart of the data processing method of the low-code platform shown according to an exemplary embodiment of the present application. As Figure 1 shown, the method provided in this embodiment includes:

[0098] S101. The component logic layer obtains the original program architecture information of the original business process and generates an original program architecture diagram according to the original program architecture information.

[0099] In this step, the component logic layer obtains the original program architecture information of the original business process and generates an original program architecture diagram according to the original program architecture information. The original program architecture information includes an original function component set and an original topology structure, and the original topology structure is used to establish the topological relationship between each function component in the original function component set.

[0100] Optionally, the component logic layer obtains a detailed description of the original business process from a database or an API interface. This information includes all original functional components (e.g., data processing modules, conditional branches, loop controls, etc.) and their attributes, as well as the connection methods between them. The component logic layer uses this information to generate a visual diagram of the original program architecture through a graphics rendering engine. In this diagram, each node represents a functional component, and the connection lines represent the call relationships between components, forming the so-called original topology.

[0101] Specifically, the component logic layer generates an original node set according to the original functional component set. A node in the original node set is used to uniquely represent a functional component in the original functional component set. The component logic layer generates the relationship lines for connecting the various nodes in the original node set according to the original topology.

[0102] S102. The visual interaction layer displays the visual diagram of the original program architecture and, in response to a component insertion instruction, inserts a new functional component into the visual diagram of the original program architecture to generate an updated program architecture diagram.

[0103] In this step, the visual interaction layer displays the visual diagram of the original program architecture and, in response to a component insertion instruction, inserts a new functional component into the visual diagram of the original program architecture to generate an updated program architecture diagram.

[0104] Optionally, in response to a component insertion instruction, the visual interaction layer inserts a new node at the target position in the visual diagram of the original program architecture, establishes a first relationship line between the new node and the previous original node and a second relationship line between the new node and the next original node, and deletes the original relationship line. Here, the new node is used to uniquely represent the new functional component, and the original relationship line is the relationship line in the visual diagram of the original program architecture that directly connects the previous original node and the next original node. The visual interaction layer updates the visual diagram of the original program architecture according to the new node, the first relationship line, and the second relationship line to generate an updated program architecture diagram.

[0105] Specifically, users can view the original program architecture diagram through the visual interaction layer, i.e., the front-end interface. When adding new functional components, the user selects or drags the required components to the specified positions on the architecture diagram and issues a component insertion instruction. This instruction includes the type of the new component, location information, and the IDs of the components it is connected to. After receiving the instruction, the visual interaction layer calls the component logic layer interface in the background. First, it creates a new node at the specified position on the original architecture diagram to represent the newly added functional component. Then, it automatically detects and establishes the logical relationships between the new node and the adjacent nodes before and after, generates the corresponding first relationship line and second relationship line, and removes the original relationship lines that are no longer applicable due to the newly added node, ensuring logical coherence. Subsequently, through the graphical interface update operation, the updated program architecture diagram is displayed to the user in real time.

[0106] S103. The component logic layer generates updated program architecture information based on the updated program architecture diagram. The updated program architecture information includes an updated functional component set and an updated topology structure.

[0107] In this step, the component logic layer generates updated program architecture information based on the updated program architecture diagram. The updated program architecture information includes an updated functional component set and an updated topology structure. The updated functional component set includes the original functional components and the newly added functional components. The updated topology structure is used to establish the topological relationships between the various functional components in the updated functional component set.

[0108] Specifically, the component logic layer can re-parse the updated program architecture information based on the updated program architecture diagram, which includes the updated functional component set and the updated topology structure. The updated functional component set contains the original functional components plus the newly inserted components, and the updated topology structure reflects the call sequence and dependency relationships after the addition of the new components.

[0109] S104. The component logic layer generates a set of business paths to be tested based on the updated program architecture information and the original program architecture information.

[0110] In this step, the component logic layer generates a set of business paths to be tested based on the updated program architecture information and the original program architecture information. The business paths to be tested in the set of business paths to be tested are the business execution paths from the first business input node to the corresponding first business output node in the updated business process corresponding to the updated program architecture information.

[0111] Specifically, the component logic layer generates an original business path set according to the original program architecture information. The original business paths in the original business path set include the business execution paths from the original business input nodes to the corresponding original business output nodes. The component logic layer generates an updated business path set according to the updated program architecture information. The updated business paths in the updated business path set include the business execution paths from the updated business input nodes to the corresponding updated business output nodes. The first business input node is an updated business input node, and the first business output node is an updated business output node. The component logic layer generates a business path set to be tested according to the original business path set and the updated business path set. Among them, the business path set to be tested is the difference set between the updated business path set and the original business path set.

[0112] Optionally, the component logic layer analyzes the original and updated program architecture information through algorithms to construct the original business path set and the updated business path set respectively. Each path defines the complete execution flow from a business input node to the corresponding output node. The business path set to be tested consists of the differences between the updated business path set and the original business path set, which means that only the parts of the business process changes introduced by the newly added components are tested, thus optimizing the allocation of test resources.

[0113] The component logic layer starts from the original program architecture information, traverses the original topology structure, and uses graph traversal algorithms (such as depth - first traversal or breadth - first traversal). Specifically, it constructs a path chain. For each original functional component, it records the path with it as the starting node and gradually constructs the complete path to the corresponding business output node during the traversal process. Each path is represented as an ordered sequence of a series of functional components, starting from the business input node and ending at the corresponding business output node. Path set construction: All the constructed paths are collected into the original business path set, providing a benchmark for subsequent comparison. Generate the updated business path set: Identify changes. Based on the updated program architecture information, identify the newly added functional components and their positions in the topology structure, as well as any changes in the original paths caused by the addition; Update path construction: For each updated path, the graph traversal algorithm is also used, but this time the impact of the newly added nodes needs to be considered specifically to ensure that the path from the new business input node to the new business output node is completely recorded; Update path set: Organize all the updated paths into the updated business path set, which reflects the actual execution paths after the business process changes. Generate the business path set to be tested: Compare differences. Compare the updated business path set with the original business path set through an algorithm (such as set operation) to identify the different parts. This step aims to find out the completely new paths introduced by the newly added functional components or the parts where the original paths have changed due to this; Construct the difference set: Combine the paths that do not exist in the original business path set in the updated business path set and the paths that have changed due to the newly added functional components into a new set, which is the business path set to be tested. This set represents all the business process change paths that need to be tested and verified.

[0114] In summary, through detailed algorithms and logical processing, this step ensures that the low - code platform can accurately identify the business paths that need to be retested due to modifications, providing a clear target path set for the subsequent automated testing link and improving the testing efficiency and accuracy.

[0115] S105. The test management layer obtains test cases according to the first business input node to test each business path to be tested in the business path set to be tested.

[0116] In this step, the test management layer obtains test cases according to the first business input node to test each business path to be tested in the business path set to be tested.

[0117] Specifically, the test management layer generates test cases for each path based on the business path set to be tested. It first creates a set of business vectors to be tested, where each vector represents a segment of the business flow from the starting point to the ending point in the path.

[0118] Specifically, for paths involving newly added functional components, the test management layer will identify the set of characteristic starting nodes, that is, all the starting nodes pointing to the newly added nodes, and execute the intelligent test data reuse strategy for these paths to reduce the workload of repeated testing.

[0119] During the testing process, if any path fails, the test management layer will record the failure details and may take measures such as rolling back changes or notifying the developer to intervene to ensure the stability and reliability of the system.

[0120] In a possible implementation, the test management layer generates a set of business vectors to be tested based on the set of business paths to be tested. The business vectors to be tested in the set of business vectors to be tested include a starting node, an ending node, and vector edges. The direction of the vector edge is used to represent the business flow direction from the starting node to the ending node. The test management layer determines the set of characteristic starting nodes based on the set of business vectors to be tested. The set of characteristic starting nodes is the set composed of the starting nodes corresponding to all the business vectors to be tested in the set of business vectors to be tested that have the newly added node as the ending node. When the test management layer uses a test case to test the first business path to be tested in the set of business paths to be tested, it saves the first test data when the test case is executed to the first characteristic starting node in the cache space. The first characteristic starting node is a characteristic starting node in the set of characteristic starting nodes, and the first business path to be tested is the business path to be tested in the set of business paths to be tested corresponding to the first time the test case is executed to the first characteristic starting node. When the test management layer uses a test case to test the second business path to be tested in the set of business paths to be tested, if all the business vectors to be tested before the newly added node of the second business path to be tested are the same as those of the first business path to be tested, it calls the first test data from the cache space and uses the first test data as the data input of the target business vector. The target business vector is the business vector to be tested in the second business path to be tested with the newly added node as the starting node.

[0121] First, it can be to generate a set of business vectors to be tested, specifically as follows:

[0122] Path vectorization: The test management layer traverses the set of business paths to be tested and converts each business path into a business vector form. Each vector contains a starting node (business input node), an ending node (business output node), and vector edges. The direction of the vector edge represents the execution direction of the business flow.

[0123] Set management: Integrate these business vectors into a set of business vectors to be tested for subsequent operations and analysis.

[0124] Second, it can be to determine the set of characteristic starting nodes, specifically as follows:

[0125] Analyze vector relationships: The test management further analyzes the set of business vectors to be tested, paying particular attention to those vectors with the newly added functional components as the end nodes, and records the start nodes of these vectors.

[0126] Set construction: Aggregate these start nodes to form a set of characteristic start nodes, which will be used to guide specific test strategies and optimizations.

[0127] Again, test execution and data reuse are as follows:

[0128] Initial test: When testing the first business path to be tested, the test management uses the test cases to execute up to the first characteristic start node and saves the first test data generated by this execution in the cache space.

[0129] Data reuse: Subsequently, when testing the second or more business paths to be tested, if their business vectors before the newly added nodes are the same as those of the first business path to be tested, the test management directly calls the first test data from the cache, avoiding repeated execution of the same operations and improving test efficiency. This data serves as the data input for the target business vectors (i.e., the vectors starting from the newly added nodes).

[0130] Next, the optimization and feedback of the test process are as follows:

[0131] Application of simulated data: Before the initial test of the characteristic business vectors using the first test simulation data, the test management obtains the corresponding test simulation data based on the start nodes of the characteristic business vectors. These data simulate the actual outputs of the nodes and are used to verify the coherence of the process.

[0132] Result evaluation: After executing the test based on the simulated data, if the first test result shows a failure, it indicates that there are errors in the newly added functional components or related paths. At this time, the test management will remove the problematic business paths from the set of business paths to be tested, generate an updated set of business paths to be tested, and continue testing only for the paths that have no problems.

[0133] In this embodiment, the component logic layer obtains the original program architecture information of the original business process, generates an original program architecture diagram based on the original program architecture information, then displays the original program architecture diagram in the visual interaction layer, and in response to a component insertion instruction, inserts a new functional component into the original program architecture diagram to generate an updated program architecture diagram, so that the component logic layer generates updated program architecture information based on the updated program architecture diagram, thereby enabling the component logic layer to generate a set of business paths to be tested based on the updated program architecture information and the original program architecture information. Furthermore, the test management layer obtains test cases according to the first business input node, and uses the test cases to test each business path to be tested in the set of business paths to be tested, thereby improving the automation level of low-code platform testing, reducing manual intervention, and thus improving the efficiency and accuracy of overall development and testing.

[0134] Figure 2 FIG. is a schematic flowchart of the data processing method of the low-code platform according to another exemplary embodiment of the present application. As Figure 2 shown, the method provided in this embodiment includes:

[0135] S201. The component logic layer obtains the original program architecture information of the original business process and generates an original program architecture diagram based on the original program architecture information.

[0136] In this step, the component logic layer obtains the original program architecture information of the original business process and generates an original program architecture diagram based on the original program architecture information. The original program architecture information includes an original functional component set and an original topology structure, and the original topology structure is used to establish the topological relationship between each functional component in the original functional component set.

[0137] Optionally, the component logic layer obtains a detailed description of the original business process from a database or an API interface. This information includes all original functional components (for example, data processing modules, conditional branches, loop controls, etc.) and their attributes, as well as the connection methods between them. The component logic layer uses this information to generate a visual original program architecture diagram through a graphics rendering engine. In this diagram, each node represents a functional component, and the connection lines represent the call relationships between components, forming the so-called original topology structure.

[0138] Specifically, the component logic layer generates an original node set according to the original functional component set. A node in the original node set is used to uniquely represent a functional component in the original functional component set. The component logic layer generates relationship lines for connecting each node in the original node set according to the original topology structure.

[0139] S202. The visualization interaction layer displays the original program architecture diagram, and in response to a component insertion instruction, inserts a newly added functional component into the original program architecture diagram to generate an updated program architecture diagram.

[0140] In this step, the visualization interaction layer displays the original program architecture diagram, and in response to a component insertion instruction, inserts a newly added functional component into the original program architecture diagram to generate an updated program architecture diagram.

[0141] Optionally, in response to a component insertion instruction, the visualization interaction layer inserts a newly added node at a target position in the original program architecture diagram, establishes a first relationship line between the newly added node and the previous original node and a second relationship line between the newly added node and the next original node, and deletes the original relationship line, where the newly added node is used to uniquely represent the newly added functional component, and the original relationship line is the relationship line in the original program architecture diagram that directly connects the previous original node and the next original node. The visualization interaction layer updates the original program architecture diagram according to the newly added node, the first relationship line, and the second relationship line to generate an updated program architecture diagram.

[0142] Specifically, the user can browse the original program architecture diagram through the visualization interaction layer, that is, the front-end interface. When a new functional component needs to be added, the user selects or drags the required component to a specified position in the architecture diagram and issues a component insertion instruction. The instruction includes the type, location information of the new component, and the ID of the component it is connected to. After receiving the instruction, the visualization interaction layer calls the component logic layer interface in the background. First, it creates a new node at the specified position in the original architecture diagram to represent the newly added functional component. Then, it automatically detects and establishes the logical relationship between the new node and the adjacent nodes before and after, generates the corresponding first relationship line and second relationship line, and removes the original relationship line that is no longer applicable due to the newly added node, ensuring logical coherence. Subsequently, through the graphic interface update operation, the updated program architecture diagram is displayed to the user in real time.

[0143] S203. The component logic layer generates updated program architecture information according to the updated program architecture diagram. The updated program architecture information includes an updated functional component set and an updated topology structure.

[0144] In this step, the component logic layer generates updated program architecture information according to the updated program architecture diagram. The updated program architecture information includes an updated functional component set and an updated topology structure. The updated functional component set includes the original functional components and the newly added functional components. The updated topology structure is used to establish the topological relationship between the various functional components in the updated functional component set.

[0145] Specifically, the component logic layer can re-parse the updated program architecture information according to the updated program architecture diagram, which includes the updated functional component set and the updated topology. The updated functional component set contains the original functional components plus the newly inserted components, and the updated topology reflects the call sequence and dependency relationship after the new components are added.

[0146] S204. The component logic layer generates a set of business paths to be tested according to the updated program architecture information and the original program architecture information.

[0147] In this step, the component logic layer generates a set of business paths to be tested according to the updated program architecture information and the original program architecture information. The business paths to be tested in the set of business paths to be tested are the business execution paths from the first business input node to the corresponding first business output node in the updated business process corresponding to the updated program architecture information.

[0148] Specifically, the component logic layer generates a set of original business paths according to the original program architecture information. The original business paths in the set of original business paths include the business execution paths from the original business input node to the corresponding original business output node. The component logic layer generates a set of updated business paths according to the updated program architecture information. The updated business paths in the set of updated business paths include the business execution paths from the updated business input node to the corresponding updated business output node. The first business input node is an updated business input node, and the first business output node is an updated business output node. The component logic layer generates a set of business paths to be tested according to the set of original business paths and the set of updated business paths. Among them, the set of business paths to be tested is the difference set between the set of updated business paths and the set of original business paths.

[0149] Optionally, the component logic layer analyzes the original and updated program architecture information through algorithms, and constructs a set of original business paths and a set of updated business paths respectively. Each path defines the complete execution process from a business input node to the corresponding output node. The set of business paths to be tested consists of the differences between the set of updated business paths and the set of original business paths, which means that only the parts of the business process changes introduced by the newly added components are tested, thus optimizing the allocation of test resources.

[0150] Starting from the original program architecture information, the component logic layer traverses the original topology, using graph traversal algorithms (such as depth-first traversal or breadth-first traversal). Specifically, a path chain is constructed. For each original functional component, the path with it as the starting node is recorded, and the complete path to the corresponding business output node is gradually constructed during the traversal process. Each path is represented as an ordered sequence of a series of functional components, starting from the business input node and ending at the corresponding business output node. Path set construction: All the constructed paths are collected into the original business path set, providing a benchmark for subsequent comparison. Generating the updated business path set: Identifying changes, based on the updated program architecture information, identify the newly added functional components and their positions in the topology, as well as any changes in the original paths caused by the addition; Updating path construction, for each updated path, the graph traversal algorithm is also used, but this time the impact of the newly added nodes needs to be specially considered to ensure that the path from the new business input node to the new business output node is completely recorded; Updating the path set, organizing all the updated paths into the updated business path set, which reflects the actual execution paths after the business process changes. Generating the business path set to be tested: Comparing differences, comparing the updated business path set with the original business path set through algorithms (such as set operations) to identify the different parts. This step aims to find out the completely new paths introduced by the newly added functional components or the parts where the original paths have changed due to this; Constructing the difference set, combining the paths that do not exist in the original business path set in the updated business path set and the paths that have changed due to the newly added functional components into a new set, which is the business path set to be tested. This set represents all the business process change paths that need to be tested and verified.

[0151] In summary, through detailed algorithms and logical processing, this step ensures that the low-code platform can accurately identify the business paths that need to be retested due to modifications, providing a clear set of target paths for the subsequent automated testing link, improving the testing efficiency and accuracy.

[0152] S205. The test management layer generates a set of business vectors to be tested based on the set of business paths to be tested. The business vectors to be tested in the set of business vectors to be tested include a starting node, an ending node, and vector edges.

[0153] Specifically, the test management layer first creates a first set of characteristic business vectors based on the determined set of characteristic starting nodes, which are directly associated with the newly inserted functional components. The starting point of each characteristic business vector corresponds to a characteristic starting node, and the ending point is the newly added node, which helps to separately test the path segments directly related to the new component.

[0154] Meanwhile, taking the newly added node as the starting point, identify the end nodes of all business vectors starting from it, and construct a second set of characteristic business vectors. The starting point of each vector is the newly added node, and the end point is the characteristic end node, ensuring that the impact of the new component on the downstream is also fully considered.

[0155] S206. The test management layer determines the set of characteristic starting nodes according to the set of business vectors to be tested.

[0156] Specifically, before comprehensive testing, the test management layer generates a comprehensive set of characteristic business vectors based on the first set of characteristic business vectors and the second set of characteristic business vectors. Perform pre-tests on each characteristic business vector in this set to detect potential problems in advance.

[0157] Then, for the starting node of each characteristic business vector, the test management layer obtains the corresponding test simulation data to simulate the output data that the node may generate during actual operation, providing accurate input conditions for subsequent tests. It should be noted that the simulation data can also be determined based on artificially preset data.

[0158] S207. The test management layer determines the first set of characteristic business vectors according to the newly added node and the set of characteristic starting nodes.

[0159] In this step, the test management layer determines the first set of characteristic business vectors according to the newly added node and the set of characteristic starting nodes. The starting nodes of the characteristic business vectors in the first set of characteristic business vectors are the characteristic starting nodes in the set of characteristic starting nodes, and the end nodes are the newly added nodes.

[0160] S208. The test management layer determines the second set of characteristic business vectors according to the newly added node and the set of characteristic end nodes.

[0161] The test management layer determines the second set of characteristic business vectors according to the newly added node and the set of characteristic end nodes. The set of characteristic end nodes is the set composed of the end nodes corresponding to all the business vectors to be tested with the newly added node as the starting node in the set of business vectors to be tested. The starting nodes of the characteristic business vectors in the second set of characteristic business vectors are the newly added nodes, and the end nodes are the characteristic end nodes in the set of characteristic end nodes.

[0162] S209. The test management layer generates a set of characteristic business vectors based on the first set of characteristic business vectors and the second set of characteristic business vectors, and according to the set of characteristic business vectors.

[0163] S210. The test management layer obtains the corresponding test simulation data according to the starting nodes of the respective characteristic business vectors in the set of characteristic business vectors.

[0164] Specifically, the test management layer obtains corresponding test simulation data according to the starting nodes of the respective characteristic service vectors in the characteristic service vector set, and the test simulation data is used to characterize the output data of the corresponding starting nodes.

[0165] S211. The test management layer uses the first test simulation data to test the first characteristic service vector in the characteristic service vector set to generate a first test result.

[0166] S212. Remove the service path to be tested including the first characteristic service vector from the set of service paths to be tested to generate an updated set of service paths to be tested.

[0167] If the first test result is a failure to execute, then remove the service path to be tested including the first characteristic service vector from the set of service paths to be tested to generate an updated set of service paths to be tested, so as to use test cases to test each service path to be tested in the updated set of service paths to be tested.

[0168] Furthermore, the test management layer generates a first local test report according to the updated program architecture diagram and the service path to be tested including the first characteristic service vector. The visual interaction layer displays the first local test report, and the first local test report includes the updated program architecture diagram and a test failure identifier displayed on the relationship line corresponding to the first characteristic service vector.

[0169] In addition, the visual interaction layer cancels the relationship line corresponding to the first characteristic service vector in the updated program architecture diagram in response to the input of the first instruction, and restores the starting node of the first characteristic service vector to the topological relationship of the corresponding starting node on the original program architecture diagram. The visual interaction layer displays the service code of the first characteristic service vector in response to the input of the second instruction.

[0170] Specifically, using the obtained test simulation data, the test management layer starts to test the first service vector in the characteristic service vector set to generate a first test result. This process verifies the correctness of the new component and its direct impact path. If the first test result indicates a failure to execute, that is, the new component introduces an error or incompatibility problem, the test management layer immediately removes the complete service path containing the characteristic service vector with the problem from the set of service paths to be tested, generating an updated test set without error paths to ensure the effectiveness of subsequent tests.

[0171] For the removed business path with problems, the test management layer will generate a first partial test report based on the updated program architecture diagram and the problem business path, clearly indicating the relationship line where the problem lies, and visually presenting it to the user through the test failure flag. The visual interaction layer provides a user interface, responds to user instructions, and can directly cancel the problem relationship line on the architecture diagram, restoring it to the topological state before insertion, or display the business code segment that causes the test failure, facilitating developers to quickly locate and fix the problem.

[0172] The test management layer generates a first partial test report based on the updated program architecture diagram and the business path with problems. The report not only includes the updated architecture view but also clearly marks the test failure points on the relationship line corresponding to the business vectors with problem characteristics.

[0173] The visual interaction layer is responsible for presenting the first partial test report, enabling users to intuitively see where the problem is and facilitating quick understanding. Users can input instructions through the interface, such as selecting to cancel the problem relationship line, and the system will restore the original architecture, or request to view the source code corresponding to the problem business vector, facilitating in-depth analysis and debugging.

[0174] After the visual interaction layer receives the user input instructions, such as requesting to view specific business code or requesting to restore a specific architecture state, the system responds.

[0175] In response to the user request, the visual interaction layer will display the business code segment related to the problem business vector, helping developers directly locate and understand the context where the error occurs, and accelerating the problem-solving process.

[0176] If the user selects to restore, the system responds to the instruction, cancels the previous operation on the interaction interface, and restores the relationship line and the architecture diagram to the state before inserting the new functional components, facilitating users to re-design or try different configurations.

[0177] Through the above steps, not only is the test process optimized, achieving efficient fault location and feedback, but also a flexible interaction experience is provided, facilitating developers to adjust and optimize immediately, thereby improving the efficiency and quality of the entire development and test cycle.

[0178] S213. The test management layer obtains test cases according to the first business input node to test each to-be-tested business path in the set of to-be-tested business paths using the test cases.

[0179] Specifically, the test management layer generates test cases for each path based on the set of to-be-tested business paths. It first creates a set of to-be-tested business vectors, where each vector represents a business flow from the starting point to the ending point in the path.

[0180] Specifically, for paths involving newly added functional components, the test management layer will identify the set of feature starting nodes, that is, all the starting nodes pointing to the newly added nodes, and execute an intelligent test data reuse strategy for these paths to reduce the workload of repeated testing.

[0181] During the testing process, if any path fails, the test management layer will record the failure details and may take measures such as rolling back changes or notifying developers to intervene to ensure the stability and reliability of the system.

[0182] In a possible implementation, the test management layer generates a set of business vectors to be tested based on the set of business paths to be tested. The business vectors to be tested in the set of business vectors to be tested include a starting node, an ending node, and vector edges. The direction of the vector edges is used to represent the business flow direction from the starting node to the ending node. The test management layer determines the set of feature starting nodes based on the set of business vectors to be tested. The set of feature starting nodes is the set composed of the starting nodes corresponding to all the business vectors to be tested in the set of business vectors to be tested that have the newly added node as the ending node. When the test management layer uses a test case to test the first business path to be tested in the set of business paths to be tested, it saves the first test data when the test case is executed up to the first feature starting node in the cache space. The first feature starting node is a feature starting node in the set of feature starting nodes, and the first business path to be tested is the business path to be tested in the set of business paths to be tested corresponding to the first time the test case reaches the first feature starting node. When the test management layer uses a test case to test the second business path to be tested in the set of business paths to be tested, if all the business vectors to be tested of the second business path to be tested before the newly added node are the same as those of the first business path to be tested, it calls the first test data from the cache space and uses the first test data as the data input of the target business vector. The target business vector is the business vector to be tested in the second business path to be tested with the newly added node as the starting node.

[0183] First, it can be to generate a set of business vectors to be tested, specifically as follows:

[0184] Path vectorization: The test management layer traverses the set of business paths to be tested and converts each business path into a business vector form. Each vector contains a starting node (business input node), an ending node (business output node), and vector edges. The direction of the vector edges represents the execution direction of the business flow.

[0185] Set management: Integrate these business vectors into a set of business vectors to be tested for subsequent operations and analysis.

[0186] Second, it can be to determine the set of feature starting nodes, specifically as follows:

[0187] Analyze vector relationships: The test management further analyzes the set of business vectors to be tested, paying particular attention to those vectors with the newly added functional components as the end nodes, and records the start nodes of these vectors.

[0188] Set construction: Aggregate these start nodes to form a set of characteristic start nodes, which will be used to guide specific test strategies and optimizations.

[0189] Again, test execution and data reuse are as follows:

[0190] Initial test: When testing the first business path to be tested, the test management uses test cases to execute up to the first characteristic start node and saves the first test data generated by this execution in the cache space.

[0191] Data reuse: Subsequently, when testing the second or more business paths to be tested, if their business vectors before the newly added nodes are the same as those of the first business path to be tested, the test management directly calls the first test data from the cache, avoiding repeated execution of the same operations and improving test efficiency. This data is used as the data input for the target business vectors (i.e., the vectors starting from the newly added nodes).

[0192] Next, the optimization and feedback of the test process are as follows:

[0193] Application of simulation data: Before initially testing the characteristic business vectors using the first test simulation data, the test management obtains the corresponding test simulation data based on the start nodes of the characteristic business vectors. These data simulate the actual outputs of the nodes and are used to verify the coherence of the process.

[0194] Result evaluation: After executing the test based on the simulation data, if the first test result shows a failure, it indicates that there are errors in the newly added functional components or related paths. At this time, the test management will remove the problematic business paths from the set of business paths to be tested, generate an updated set of business paths to be tested, and continue testing only the paths that have no problems.

[0195] In this embodiment, the original program architecture information of the original business process is obtained through the component logic layer, and an original program architecture diagram is generated according to the original program architecture information. Then, the original program architecture diagram is displayed in the visual interaction layer, and in response to a component insertion instruction, a new function component is inserted into the original program architecture diagram to generate an updated program architecture diagram, so that the component logic layer generates updated program architecture information according to the updated program architecture diagram, thereby enabling the component logic layer to generate a set of business paths to be tested according to the updated program architecture information and the original program architecture information. Furthermore, the test management layer obtains test cases according to the first business input node, and uses the test cases to test each business path to be tested in the set of business paths to be tested, thereby improving the automation level of low-code platform testing, reducing manual intervention, and thus improving the efficiency and accuracy of overall development and testing.

[0196] Figure 3 It is a schematic structural diagram of a device shown by an example embodiment of the present application. As Figure 3 shown, the low-code platform management system 300 provided in this embodiment includes:

[0197] A visual interaction layer 310, a component logic layer 320, and a test management layer 330, where the component logic layer 320 is respectively connected to the visual interaction layer 310 and the test management layer 330;

[0198] The component logic layer 320 obtains the original program architecture information of the original business process, and generates an original program architecture diagram according to the original program architecture information. The original program architecture information includes an original function component set and an original topology structure, and the original topology structure is used to establish the topological relationship between each function component in the original function components;

[0199] The visual interaction layer 310 displays the original program architecture diagram, and in response to a component insertion instruction, inserts a new function component into the original program architecture diagram to generate an updated program architecture diagram;

[0200] The component logic layer 320 generates updated program architecture information according to the updated program architecture diagram. The updated program architecture information includes an updated function component set and an updated topology structure. The updated function component set includes the original function components and the new function components, and the updated topology structure is used to establish the topological relationship between each function component in the updated function components;

[0201] The component logic layer 320 generates a set of business paths to be tested based on the updated program architecture information and the original program architecture information. The business paths to be tested in the set of business paths to be tested are the business execution paths from the first business input node to the corresponding first business output node in the updated business process corresponding to the updated program architecture information;

[0202] The test management layer 330 obtains test cases according to the first business input node, so as to use the test cases to test each business path to be tested in the set of business paths to be tested.

[0203] Optionally, the component logic layer 320 generates an original node set according to the original function component set. One node in the original node set is used to uniquely represent one function component in the original function component set;

[0204] The component logic layer 320 generates relationship lines for connecting each node in the original node set according to the original topology structure;

[0205] In response to the component insertion instruction, the visual interaction layer 310 inserts a new node at the target position of the original program architecture diagram, and establishes a first relationship line between the new node and the previous original node and a second relationship line between the new node and the next original node, and deletes the original relationship line. The new node is used to uniquely represent the new function component, and the original relationship line is the relationship line in the original program architecture diagram for directly connecting the previous original node and the next original node;

[0206] The visual interaction layer 310 updates the original program architecture diagram according to the new node, the first relationship line and the second relationship line to generate the updated program architecture diagram.

[0207] Optionally, the component logic layer 320 generates an original business path set according to the original program architecture information. The original business paths in the original business path set include the business execution paths from the original business input node to the corresponding original business output node;

[0208] The component logic layer 320 generates an updated business path set according to the updated program architecture information. The updated business paths in the updated business path set include the business execution paths from the updated business input node to the corresponding updated business output node. The first business input node is an updated business input node, and the first business output node is an updated business output node;

[0209] The component logic layer 320 generates the set of service paths to be tested according to the set of original service paths and the set of updated service paths, where the set of service paths to be tested is the difference set between the set of updated service paths and the set of original service paths.

[0210] Optionally, the test management layer 330 generates a set of service vectors to be tested according to the set of service paths to be tested. Each service vector to be tested in the set of service vectors to be tested includes a start node, an end node, and a vector edge. The direction of the vector edge is used to represent the service flow direction from the start node to the end node.

[0211] The test management layer 330 determines a set of characteristic start nodes according to the set of service vectors to be tested. The set of characteristic start nodes is a set composed of start nodes corresponding to all service vectors to be tested in the set of service vectors to be tested that take the new node as the end node.

[0212] When the test management layer 330 uses the test case to test the first service path to be tested in the set of service paths to be tested, it saves the first test data when the test case is executed to the first characteristic start node in the cache space. The first characteristic start node is a characteristic start node in the set of characteristic start nodes, and the first service path to be tested is the service path to be tested in the set of service paths to be tested where the test case first reaches the first characteristic start node.

[0213] When the test management layer 330 uses the test case to test the second service path to be tested in the set of service paths to be tested, if all service vectors to be tested before the new node of the second service path to be tested are the same as those of the first service path to be tested, it calls the first test data from the cache space and uses the first test data as the data input of the target service vector. The target service vector is the service vector to be tested in the second service path to be tested that takes the new node as the start node.

[0214] Optionally, the test management layer 330 determines a first set of characteristic service vectors according to the new node and the set of characteristic start nodes. The start nodes of the characteristic service vectors in the first set of characteristic service vectors are the characteristic start nodes in the set of characteristic start nodes, and the end nodes are the new node.

[0215] The test management layer 330 determines a second set of characteristic service vectors according to the newly added node and the set of characteristic end nodes. The set of characteristic end nodes is a set composed of the end nodes corresponding to all the service vectors to be tested in the service vector set to be tested, where the newly added node is used as the starting node. The starting node of the characteristic service vectors in the second set of characteristic service vectors is the newly added node, and the end node is the characteristic end node in the set of characteristic end nodes;

[0216] The test management layer 330 generates a set of characteristic service vectors according to the first set of characteristic service vectors and the second set of characteristic service vectors, and according to the set of characteristic service vectors

[0217] The test management layer 330 obtains corresponding test simulation data according to the starting nodes of the respective characteristic service vectors in the set of characteristic service vectors. The test simulation data is used to represent the output data of the corresponding starting nodes;

[0218] The test management layer 330 uses the first test simulation data to test the first characteristic service vector in the set of characteristic service vectors to generate a first test result;

[0219] If the first test result is a failure to execute, the service path to be tested including the first characteristic service vector is removed from the set of service paths to be tested to generate an updated set of service paths to be tested, so as to use the test cases to test each service path to be tested in the updated set of service paths to be tested.

[0220] Optionally, the test management layer 330 generates a first local test report according to the updated program architecture diagram and the service path to be tested including the first characteristic service vector;

[0221] The visualization interaction layer 310 displays the first local test report. The first local test report includes the updated program architecture diagram and a test failure identifier displayed on the relationship line corresponding to the first characteristic service vector.

[0222] Optionally, the visualization interaction layer 310, in response to a first instruction input, cancels the relationship line corresponding to the first characteristic service vector in the updated program architecture diagram and restores the starting node of the first characteristic service vector to the topological relationship of the corresponding starting node on the original program architecture diagram;

[0223] The visualization interaction layer 310, in response to a second instruction input, displays the service code of the first characteristic service vector.

[0224] Figure 4It is a schematic structural diagram of an electronic device shown according to an exemplary embodiment of the present application. As Figure 4 shown, an electronic device 400 provided in this embodiment includes: a processor 401 and a memory 402; wherein:

[0225] The memory 402 is used to store a computer program, and this memory can also be a flash (flash memory).

[0226] The processor 401 is used to execute the execution instructions stored in the memory to implement each step in the above method. Specifically, reference can be made to the relevant descriptions in the foregoing method embodiments.

[0227] Optionally, the memory 402 can be either independent or integrated with the processor 401.

[0228] When the memory 402 is a device independent of the processor 401, the electronic device 400 may further include:

[0229] A bus 403 for connecting the memory 402 and the processor 401.

[0230] This embodiment also provides a readable storage medium. A computer program is stored in the readable storage medium. When at least one processor of the electronic device executes this computer program, the electronic device executes the methods provided by the above various embodiments.

[0231] This embodiment also provides a program product. The program product includes a computer program, and this computer program is stored in a readable storage medium. At least one processor of the electronic device can read this computer program from the readable storage medium, and the execution of this computer program by at least one processor enables the electronic device to implement the methods provided by the above various embodiments.

[0232] Those skilled in the art will readily think of other implementation schemes of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptive changes of the present application. These variations, uses, or adaptive changes follow the general principles of the present application and include common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the claims.

[0233] It should be understood that the present application is not limited to the exact structure already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A data processing method for a low-code platform, characterized in that: Applied to a low-code platform management system, the low-code platform management system includes: a visualization interaction layer, a component logic layer and a test management layer, the component logic layer is connected to the visualization interaction layer and the test management layer respectively; the method includes: The component logic layer obtains original program architecture information of the original business process, and generates an original program architecture diagram according to the original program architecture information, wherein the original program architecture information includes an original functional component set and an original topological structure, and the original topological structure is used to establish a topological relationship between each functional component in the original functional component; The visual interaction layer displays the original program architecture diagram, and in response to a component insertion instruction, inserts a newly added functional component into the original program architecture diagram to generate an updated program architecture diagram; The component logic layer generates update program architecture information according to the update program architecture diagram, wherein the update program architecture information includes an update function component set and an update topology structure, wherein the update function component set includes the original function component and the newly added function component, and the update topology structure is used to establish a topological relationship between each function component in the update function component; The component logic layer generates a set of to-be-tested business paths according to the update program architecture information and the original program architecture information, wherein the to-be-tested business paths in the to-be-tested business path set are business execution paths from a first business input node to a corresponding first business output node in the update business process corresponding to the update program architecture information; The test management layer obtains a test case according to the first service input node, so as to test each service path to be tested in the service path set to be tested by using the test case; The component logic layer obtains original program architecture information of the original business process, and generates an original program architecture diagram according to the original program architecture information, including: The component logic layer generates an original node set according to the original functional component set, wherein a node in the original node set is used to uniquely represent a functional component in the original functional component set; The component logic layer generates a relationship line for connecting each node in the original node set according to the original topological structure; Correspondingly, in response to the component insertion instruction, inserting the newly added functional component into the original program architecture diagram to generate an updated program architecture diagram includes: The visual interaction layer, in response to the component insertion instruction, inserts a new node at a target position of the original program architecture diagram, establishes a first relationship line between the new node and a previous original node and a second relationship line between the new node and a next original node, and deletes the original relationship line, wherein the new node is used to uniquely represent the new functional component, and the original relationship line is a relationship line in the original program architecture diagram used to directly connect the previous original node and the next original node; The visual interaction layer updates the original program architecture diagram according to the newly added node, the first relationship line, and the second relationship line to generate the updated program architecture diagram; The component logic layer generates a set of service paths to be tested according to the updated program architecture information and the original program architecture information, including: The component logic layer generates an original business path set according to the original program architecture information, wherein the original business paths in the original business path set include business execution paths of original business output nodes corresponding to original business input nodes; The component logic layer generates an update service path set according to the update program architecture information, wherein the update service path in the update service path set includes a service execution path from an update service input node to a corresponding update service output node, wherein the first service input node is an update service input node, and the first service output node is an update service output node; The component logic layer generates the service path set to be tested according to the original service path set and the updated service path set, wherein the service path set to be tested is a difference set between the updated service path set and the original service path set; The using the test case to test each service path to be tested in the service path set to be tested includes: The test management layer generates a set of service vectors to be tested according to the set of service paths to be tested, wherein the service vectors to be tested in the set of service vectors to be tested include a starting point node, an end point node and a vector edge, and the direction of the vector edge is used to represent the direction of the service flow from the starting point node to the end point node; The test management layer determines a characteristic starting point node set according to the service vector set to be tested, wherein the characteristic starting point node set is a set consisting of starting points corresponding to all service vectors to be tested in the service vector set to be tested that use the newly added node as an end point node; When the test management layer uses the test case to test the first service path to be tested in the service path set to be tested, first test data of the test case executed to a first characteristic starting point node is saved in the cache space, the first characteristic starting point node is a characteristic starting point node in the characteristic starting point node set, and the first service path to be tested is the service path to be tested corresponding to the first characteristic starting point node when the test case in the service path set to be tested is executed for the first time; When the test management layer uses the test case to test the second service path to be tested in the service path set to be tested, if the second service path to be tested is identical to all service vectors to be tested of the first service path to be tested before the newly added node, the first test data is directly called from the cache space, and the first test data is used as the data input of the target service vector, which is the service vector to be tested in the second service path to be tested with the newly added node as the starting point, so as to avoid repeated test operations before the newly added node.

2. The data processing method of the low-code platform according to claim 1 is characterized in that: After the test management layer determines the characteristic starting point node set according to the service vector set to be tested, the method further includes: The test management layer determines a first characteristic service vector set according to the newly added node and the characteristic starting node set, wherein the starting node of the characteristic service vector in the first characteristic service vector set is the characteristic starting node in the characteristic starting node set, and the ending node is the newly added node; The test management layer determines a second characteristic service vector set according to the newly added node and the characteristic terminal node set, wherein the characteristic terminal node set is a set consisting of terminal nodes corresponding to all service vectors to be tested in the service vector set to be tested that use the newly added node as a starting point node, and the starting point node of the characteristic service vector in the second characteristic service vector set is the newly added node, and the terminal node is a characteristic terminal node in the characteristic terminal node set; Correspondingly, before using the test case to test each service path to be tested in the service path set to be tested, the method further includes: The test management layer generates a characteristic service vector set according to the first characteristic service vector set and the second characteristic service vector set, and according to the characteristic service vector set; The test management layer obtains corresponding test simulation data according to the starting point node of each characteristic service vector in the characteristic service vector set, and the test simulation data is used to represent the output data of the corresponding starting point node; The test management layer tests the first characteristic service vector in the characteristic service vector set using the first test simulation data to generate a first test result; If the first test result is execution failure, the service path to be tested including the first characteristic service vector will be removed from the service path set to be tested to generate an updated service path set to be tested, and each service path to be tested in the updated service path set to be tested will be tested using the test case.

3. The data processing method of the low-code platform according to claim 2 is characterized in that: After removing the service path to be tested including the first characteristic service vector from the service path set to be tested, the method further includes: The test management layer generates a first partial test report according to the update program architecture diagram and the service path to be tested including the first characteristic service vector; The visual interaction layer displays the first partial test report, which includes the update program architecture diagram and a test failure mark displayed on a relationship line corresponding to the first characteristic service vector.

4. The data processing method of the low-code platform according to claim 3 is characterized in that: After the visual interaction layer displays the first local test report, the method further includes: The visual interaction layer cancels the relationship line corresponding to the first characteristic business vector in the updated program architecture diagram in response to the input first instruction, and restores the starting point node of the first characteristic business vector to the topological relationship of the corresponding starting point node on the original program architecture diagram; The visual interaction layer displays the service code of the first characteristic service vector in response to the input second instruction.

5. A low-code platform management system, characterized in that: include: A visualization interaction layer, a component logic layer and a test management layer, wherein the component logic layer is connected to the visualization interaction layer and the test management layer respectively; The component logic layer obtains original program architecture information of the original business process, and generates an original program architecture diagram according to the original program architecture information, wherein the original program architecture information includes an original functional component set and an original topological structure, and the original topological structure is used to establish a topological relationship between each functional component in the original functional component; The visual interaction layer displays the original program architecture diagram, and in response to a component insertion instruction, inserts a newly added functional component into the original program architecture diagram to generate an updated program architecture diagram; The component logic layer generates update program architecture information according to the update program architecture diagram, wherein the update program architecture information includes an update function component set and an update topology structure, wherein the update function component set includes the original function component and the newly added function component, and the update topology structure is used to establish a topological relationship between each function component in the update function component; The component logic layer generates a set of to-be-tested business paths according to the update program architecture information and the original program architecture information, wherein the to-be-tested business paths in the to-be-tested business path set are business execution paths from a first business input node to a corresponding first business output node in the update business process corresponding to the update program architecture information; The test management layer obtains a test case according to the first service input node, so as to test each service path to be tested in the service path set to be tested by using the test case; The component logic layer obtains original program architecture information of the original business process, and generates an original program architecture diagram according to the original program architecture information, including: The component logic layer generates an original node set according to the original functional component set, wherein a node in the original node set is used to uniquely represent a functional component in the original functional component set; The component logic layer generates a relationship line for connecting each node in the original node set according to the original topological structure; Correspondingly, in response to the component insertion instruction, inserting the newly added functional component into the original program architecture diagram to generate an updated program architecture diagram includes: The visual interaction layer, in response to the component insertion instruction, inserts a new node at a target position of the original program architecture diagram, establishes a first relationship line between the new node and a previous original node and a second relationship line between the new node and a next original node, and deletes the original relationship line, wherein the new node is used to uniquely represent the new functional component, and the original relationship line is a relationship line in the original program architecture diagram used to directly connect the previous original node and the next original node; The visual interaction layer updates the original program architecture diagram according to the newly added node, the first relationship line, and the second relationship line to generate the updated program architecture diagram; The component logic layer generates a set of service paths to be tested according to the updated program architecture information and the original program architecture information, including: The component logic layer generates an original business path set according to the original program architecture information, wherein the original business paths in the original business path set include business execution paths of original business output nodes corresponding to original business input nodes; The component logic layer generates an update service path set according to the update program architecture information, wherein the update service path in the update service path set includes a service execution path from an update service input node to a corresponding update service output node, wherein the first service input node is an update service input node, and the first service output node is an update service output node; The component logic layer generates the service path set to be tested according to the original service path set and the updated service path set, wherein the service path set to be tested is a difference set between the updated service path set and the original service path set; The using the test case to test each service path to be tested in the service path set to be tested includes: The test management layer generates a set of service vectors to be tested according to the set of service paths to be tested, wherein the service vectors to be tested in the set of service vectors to be tested include a starting point node, an end point node and a vector edge, and the direction of the vector edge is used to represent the direction of the service flow from the starting point node to the end point node; The test management layer determines a characteristic starting point node set according to the service vector set to be tested, wherein the characteristic starting point node set is a set consisting of starting points corresponding to all service vectors to be tested in the service vector set to be tested that use the newly added node as an end point node; When the test management layer uses the test case to test the first service path to be tested in the service path set to be tested, first test data of the test case executed to a first characteristic starting point node is saved in the cache space, the first characteristic starting point node is a characteristic starting point node in the characteristic starting point node set, and the first service path to be tested is the service path to be tested corresponding to the first characteristic starting point node when the test case in the service path set to be tested is executed for the first time; When the test management layer uses the test case to test the second service path to be tested in the service path set to be tested, if the second service path to be tested is identical to all service vectors to be tested of the first service path to be tested before the newly added node, the first test data is directly called from the cache space, and the first test data is used as the data input of the target service vector, which is the service vector to be tested in the second service path to be tested with the newly added node as the starting point, so as to avoid repeated test operations before the newly added node.

6. An electronic device, characterized in that: include: processor; as well as, A memory, configured to store executable instructions of the processor; The processor is configured to perform the method of any one of claims 1 to 4 by executing the executable instructions.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 4 when executed by a processor.

Images