Distributed SDK (Software Development Kit) actuator implementation method and device

Abstract

The invention relates to an implementation method of a distributed SDK (Software Development Kit) executor, which comprises the following steps of: providing a development kit for quickly establishing a distributed SDK execution server, wherein the development kit supports one-key import and generates a basic server framework; automatically scanning a system imported by a user through a universal view scanner built in the development kit, and injecting into an execution entry; an extensible top-level parent class is provided, and a developer realizes customized SDK execution logic by inheriting the parent class; according to parameters transmitted by a front end, an execution request is routed to a corresponding SDK execution logic through an SDK type analyzer and a routing table; and the execution server receives the execution result and returns the execution result to the test server, and the test server analyzes and stores the result and returns a final result to the user. According to the method, free switching and concurrent testing of SDKs of any version are achieved, the testing efficiency is greatly improved, a large number of resources are saved, and the testing quality is guaranteed.

Description

Technical Field

[0001] The present invention relates to the field of automated testing technology, and in particular to a distributed SDK executor implementation method and device. Background Art

[0002] For microservice testing scenarios, the existing technology requires that the microservice middle platform provide the front-end system SDK. Each microservice platform has its own SDK, and a single microservice platform SDK often has multiple versions of the SDK. The current technology for SDK testing only supports the execution of a single version of the SDK in a single scenario. It cannot achieve universal coverage for test scenarios with multiple versions of SDK for a single system or multiple SDKs for multiple systems.

[0003] Therefore, the existing technology still has the problem that the automated testing platform cannot simultaneously integrate multiple versions of SDK for a single system, resulting in test omissions, inability to achieve unified testing, and frequent changes in SDK versions of different systems, resulting in frequent changes to the automated testing platform, affecting the stability of the test environment. Summary of the Invention

[0004] To address the shortcomings of the existing technology, the present invention provides an SDK version that integrates various micro-testing platforms. In actual testing scenarios, it can realize free switching and concurrent testing of any version of SDK, greatly improving testing efficiency and saving a lot of resources. The SDK test coverage rate reaches more than 90%, greatly ensuring the quality of project testing.

[0005] The present invention provides a method for implementing a distributed SDK executor, which is characterized by comprising:

[0006] S1 provides a development toolkit for quickly building a distributed SDK execution server. The development toolkit supports one-click import and generation of a basic server framework.

[0007] S2 automatically scans the system imported by the user through the universal view scanner built into the development toolkit and injects the execution entry;

[0008] S3 provides an extensible top-level parent class, and developers can implement customized SDK execution logic by inheriting the parent class.

[0009] S4 routes the execution request to the corresponding SDK execution logic based on the parameters passed in by the front-end through the SDK type parser and routing table;

[0010] S5 The execution server receives the execution results and transmits them back to the test server, which analyzes and stores the results and returns the final results to the user.

[0011] Exemplarily, the development toolkit generates a basic distributed server framework through a preset template and includes an execution logic configuration file.

[0012] Exemplarily, the universal view scanner analyzes the classes and methods imported into the system based on dynamic proxy technology, and automatically generates code logic for the execution entry according to preset rules.

[0013] For example, the top-level parent class uses the template method pattern to encapsulate the default SDK execution logic, and the developer implements customized execution logic by overriding the reserved method;

[0014] The top-level parent class includes but is not limited to extension methods for pre-execution parameter verification and post-execution result processing.

[0015] Exemplarily, the SDK type parser extracts the SDK type based on the parameters passed in by the front end, matches the corresponding SDK execution logic through the dynamic routing table, and distributes the execution request to the target SDK.

[0016] Exemplarily, the test server performs automated analysis on the returned execution results, including log parsing, performance indicator extraction, and error information location, and generates a structured test report that is stored in a database for user query and feedback.

[0017] The present invention also provides a distributed SDK executor device, characterized by comprising:

[0018] The development toolkit module provides a development toolkit for quickly building a distributed SDK execution server. The development toolkit supports one-click import and generation of a basic server framework.

[0019] A view scanning module, used to automatically scan the system imported by the user through the universal view scanner built into the development toolkit and inject an execution entry;

[0020] The parent class extension module is used to provide an extensible top-level parent class. Developers can implement customized SDK execution logic by inheriting the parent class.

[0021] The routing parsing module is used to route the execution request to the corresponding SDK execution logic based on the parameters passed in by the front-end through the SDK type parser and routing table;

[0022] The result feedback module is used for the execution server to receive the execution results and transmit them back to the test server, which analyzes and stores the results and returns the final results to the user.

[0023] The present invention also provides a computer-readable storage medium, characterized in that a computer program is stored on the storage medium, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

[0024] The present invention also provides an electronic device, characterized in that it includes a processor and a memory;

[0025] The memory is used to store computer programs;

[0026] The processor is configured to execute the method according to any one of claims 1 to 6 by calling a stored computer program.

[0027] The present invention also relates to a computer program product, comprising a computer program and / or instructions, characterized in that the computer program and / or instructions implement the steps of the above method when executed by a processor.

[0028] The beneficial effects of the present invention are: (1) rapid implementation of distributed SDK execution server construction without complex manual configuration, significantly reducing the development threshold and improving development efficiency; (2) providing modular function expansion to support rapid integration of complex business scenarios; (3) flexibly supporting the execution logic differences of different SDKs, enhancing system adaptability, reducing the development cost of duplicate code, and ensuring the stability and maintainability of the extension logic; (4) users are unaware of SDK differentiation and execution operations, providing a simple and smooth user experience. At the same time, the automated routing logic reduces human operational errors and improves system reliability. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 This is a flow chart of the implementation method of the distributed SDK executor of the present invention.

[0030] Figure 2 This is a schematic diagram of the device structure of the distributed SDK executor of the present invention. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0032] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are used only to distinguish the description and should not be understood as indicating or implying relative importance.

[0033] The first aspect of the present invention provides a method for implementing a distributed SDK executor, such as Figure 1 Shown, including:

[0034] S1 provides a development toolkit for quickly building a distributed SDK execution server. The development toolkit supports one-click import and generation of a basic server framework.

[0035] Specifically, developers download and import the ServerClient package to initialize the core executor modules. The toolkit comes with preconfigured templates that automatically generate the basic components required for a distributed SDK execution server and provides executable examples to help developers verify the correctness of basic functions. A standardized ServerClient development toolkit is provided. Its modular design integrates common execution logic and tools, reducing developer workload, significantly lowering the development threshold, and improving development efficiency.

[0036] S2 automatically scans the user-imported system through the universal view scanner built into the development toolkit and injects an execution entry;

[0037] Specifically, the view scanner uses dynamic proxies and reflection mechanisms to analyze the classes and methods imported into the system, and identifies potential execution entries based on preset rules (such as annotations and naming conventions). Automatically generate code for the execution logic entry and integrate it with the system to achieve low-code quick startup capabilities. Through dynamic injection technology, the execution entry is bound to the execution process of ServerClient. The view scanner generates a simplified configuration file to help users quickly start and debug the executor. This design method eliminates the need for users to manually write entry code, reduces code redundancy, improves development efficiency, and supports the rapid integration of complex business scenarios by providing modular function extensions.

[0038] S3 provides an extensible top-level parent class, and developers can implement customized SDK execution logic by inheriting the parent class.

[0039] Specifically, a top-level parent class is provided to encapsulate common execution logic and support the extension of customized logic through inheritance. ServerClient provides a default parent class that encapsulates core processes (such as request parsing and result processing). Developers can override key methods by inheriting the parent class based on subtle differences in SDK execution logic, such as pre-execution parameter checking and post-execution result formatting. Custom logic is automatically integrated into the execution process of ServerClient without modifying other modules. This design can flexibly support the differences in execution logic of different SDKs and enhance system adaptability. It reduces the development cost of duplicate code and ensures the stability and maintainability of the extended logic.

[0040] S4 routes the execution request to the corresponding SDK execution logic based on the parameters passed in by the front-end through the SDK type parser and routing table;

[0041] Specifically, the execution request parameters passed in by the front-end are identified through a parameter parser (such as one based on JSON Schema or other protocol parsing libraries). After receiving the request, the test server parses the parameters to extract the target SDK type and execution command. According to the SDK type, the dynamic routing table is matched to locate the corresponding execution logic (such as class, module, method). The execution request is passed to the execution environment of the target SDK and the result is returned. The user is unaware of the SDK differentiation and execution operations, providing a simple and smooth user experience. The automated routing logic reduces human operational errors and improves system reliability.

[0042] S5 The execution server receives the execution results and transmits them back to the test server, which analyzes and stores the results and returns the final results to the user.

[0043] Specifically, the original results returned by the execution server are used in conjunction with the analysis engine to automatically process the results (such as log parsing, error location, and performance statistics). The execution server transmits the results back to the test server through a standard protocol, including the original data of the test execution. The test server calls the analysis engine to process the results, such as filtering non-critical information, extracting key performance indicators, marking abnormal results, etc. After the result analysis is completed, the final data is stored in the database and returned to the user with the help of the database storage module. The automated analysis and storage process improves the accuracy and efficiency of result processing, provides users with clear test feedback and reports, and facilitates subsequent problem location and optimization.

[0044] The second aspect of the present invention is a distributed SDK executor device, such as Figure 2 Shown, including:

[0045] The development toolkit module provides a development toolkit for quickly building a distributed SDK execution server. The development toolkit supports one-click import and generation of a basic server framework.

[0046] A view scanning module, used to automatically scan the system imported by the user through the universal view scanner built into the development toolkit and inject an execution entry;

[0047] The parent class extension module is used to provide an extensible top-level parent class. Developers can implement customized SDK execution logic by inheriting the parent class.

[0048] The routing parsing module is used to route the execution request to the corresponding SDK execution logic based on the parameters passed in by the front-end through the SDK type parser and routing table;

[0049] The result feedback module is used for the execution server to receive the execution results and transmit them back to the test server, which analyzes and stores the results and returns the final results to the user.

[0050] By using this device, the above-mentioned processing method can be executed and the corresponding technical effects can be achieved.

[0051] An embodiment of the present invention also provides a computer-readable storage medium capable of implementing all steps of the method in the above embodiment. The computer-readable storage medium stores a computer program that implements all steps of the method in the above embodiment when executed by a processor.

[0052] An embodiment of the present invention also provides an electronic device for executing the above-mentioned method. As an implementation device of the method, the electronic device has at least a processor and a memory, and in particular, the memory stores the data and related computer programs required for executing the method, and the processor calls the data and programs in the memory to execute all the steps of the implementation method and obtains the corresponding technical effect.

[0053] Preferably, the electronic device may include a bus architecture, which may include any number of interconnected buses and bridges, and the bus will include various circuits linked together by one or more processors and memories. The bus may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and, therefore, will not be described further herein. The bus interface provides an interface between the bus and the receiver and transmitter. The receiver and transmitter can be the same component, namely a transceiver, which provides a unit for communicating with various other systems over a transmission medium. The processor is responsible for managing the bus and general processing, while the memory can be used to store data used by the processor when performing operations.

[0054] Additionally, the electronic device may further include components such as a communication module, an input unit, an audio processor, a display, and a power supply. The processor (or controller, operating control) employed may include a microprocessor or other processor device and / or logic device, which receives input and controls the operation of various components of the electronic device. The memory may be one or more of a cache, flash memory, a hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices, and may store the aforementioned data and information. It may also store programs for executing the relevant information, and the processor may execute the programs stored in the memory to implement information storage or processing. The input unit is used to provide input to the processor, and may, for example, be a keypad or touch input device. The power supply is used to provide power to the electronic device. The display is used to display objects such as images and text, and may, for example, be an LCD display. The communication module is a transmitter / receiver that sends and receives signals via an antenna. The communication module (transmitter / receiver) is coupled to the processor to provide input signals and receive output signals, similar to the case of a conventional mobile communication terminal. Based on different communication technologies, multiple communication modules can be provided in the same electronic device, such as a cellular network module, a Bluetooth module, and / or a wireless local area network module. The communication module (transmitter / receiver) is also coupled to a speaker and a microphone via an audio processor to provide audio output via the speaker and receive audio input from the microphone, thereby implementing common telecommunications functions. The audio processor may include any suitable buffer, decoder, amplifier, etc. In addition, the audio processor is also coupled to a central processing unit, enabling local recording via the microphone and playback of stored audio via the speaker.

[0055] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0056] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A system that specifies the functions of a box or boxes.

[0057] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction system that is implemented in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0058] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The present invention is described in detail below. ...

[0059] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention are intended to be covered by the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A method for implementing a distributed SDK executor, characterized in that: include: S1 provides a development toolkit for quickly building a distributed SDK execution server. The development toolkit supports one-click import and generation of the basic server framework. S2 automatically scans the system imported by the user through the universal view scanner built into the development toolkit and injects the execution entry; S3 provides an extensible top-level parent class, and developers can implement customized SDK execution logic by inheriting the parent class. S4 uses the SDK type parser and routing table according to the parameters passed in by the front end. Routing execution requests to the corresponding SDK execution logic; S5 The execution server receives the execution results and transmits them back to the test server, which analyzes and stores the results and returns the final results to the user.

2. The method according to claim 1, characterized in that The development toolkit generates a basic distributed server framework through a preset template and includes an execution logic configuration file.

3. The method according to claim 1, characterized in that The universal view scanner analyzes the classes and methods of the imported system based on dynamic proxy technology, and automatically generates the code logic of the execution entry according to preset rules.

4. The method according to claim 1, characterized in that The top-level parent class uses the template method pattern to encapsulate the default SDK execution logic, and developers implement customized execution logic by overriding reserved methods; The top-level parent class includes but is not limited to extension methods for pre-execution parameter verification and post-execution result processing.

5. The method according to claim 1, characterized in that The SDK type parser extracts the SDK type based on the parameters passed in by the front end, matches the corresponding SDK execution logic through the dynamic routing table, and distributes the execution request to the target SDK.

6. The method according to claim 1, characterized in that The test server automatically analyzes the returned execution results, including log parsing, performance indicator extraction, and error information location, and generates a structured test report that is stored in a database for user query and feedback.

7. A distributed SDK executor device, characterized in that: include: The development toolkit module provides a development toolkit for quickly building a distributed SDK execution server. The development toolkit supports one-click import and generation of a basic server framework. A view scanning module, used to automatically scan the system imported by the user through the universal view scanner built into the development toolkit and inject an execution entry; The parent class extension module is used to provide an extensible top-level parent class. Developers can implement customized SDK execution logic by inheriting the parent class. The routing parsing module is used to route the execution request to the corresponding SDK execution logic based on the parameters passed in by the front-end through the SDK type parser and routing table; The result feedback module is used for the execution server to receive the execution results and transmit them back to the test server, which analyzes and stores the results and returns the final results to the user.

8. A computer-readable storage medium, characterized in that The storage medium stores a computer program, which implements the method according to any one of claims 1 to 6 when executed by a processor.

9. An electronic device, characterized in that: including processor and memory; The memory is used to store computer programs; The processor is configured to execute the method according to any one of claims 1 to 6 by calling a stored computer program.

10. A computer program product comprising a computer program and / or instructions, characterized in that When the computer program and / or instructions are executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images