An automated integration testing method and system for TIPU network offloading storage offloading and trusted sandbox

Abstract

The application belongs to the technical field of automatic testing, and discloses an automatic integration testing method and system for TIPU network offloading, storage offloading and a trusted sandbox, the method comprising the following steps: S1, testing configuration initialization, and combination into a test case set; S2, automatic creation of a test environment, automatic creation of a test instance environment based on a cloud platform scheduling engine, deployment of a behavior collection component and a trusted state collection component; S3, offloading behavior data collection, execution of network offloading testing and storage offloading testing cases on the created test instance; S4, trusted state acquisition, parallel or according to a preset strategy, execution of a trusted measurement instruction in the trusted sandbox, and acquisition of trusted state data; S5, consistency analysis and diagnosis, comparison according to a consistency determination rule, judgment of whether the offloading behavior is enabled and path executed as expected, judgment of whether the offloading behavior and the trusted sandbox state are consistent, positioning and classification of abnormal behaviors; and S6, test result output.

Description

Technical Field

[0001] This application belongs to the field of automated testing technology, and particularly relates to an automated integrated testing method and system for TIPU network offloading, storage offloading, and trusted sandboxing. It is used to automate the detection of hardware offloading behavior, joint verification of trusted states, and cross-node test scheduling in a trusted execution environment that includes TIPU-like hardware offloading capabilities. Background Technology

[0002] Trusted execution and trusted sandbox A Trusted Execution Environment (TEE) is an execution space that provides security through hardware isolation and metric chains. It is used to run sensitive code and data, ensuring that they are protected from unauthorized access or malicious interference within an isolated area. A Trusted Sandbox is a higher-level isolated execution space built upon the TEE concept and is commonly found in virtualization and containerized systems.

[0003] Network uninstallation and storage uninstallation To improve overall system performance, modern network and storage systems widely employ hardware offloading mechanisms. Network offloading transfers some network protocol processing tasks from the host CPU to dedicated network hardware to reduce host load and improve data transfer performance; storage offloading transfers some I / O data processing from the host system to coprocessors or storage controllers to improve storage processing efficiency.

[0004] Current Status of Automated Testing Technology Automated testing is an indispensable part of the modern software development process, primarily used for functional, performance, regression, and integration testing. Existing automated testing tools and methods typically focus on software logic or business layer behavior, without addressing the path verification of underlying hardware offloading behavior or consistency verification with trusted execution states. Furthermore, security sandbox testing is mainly used for isolating malicious behavior analysis and is not directly related to the automated integration verification of underlying hardware offloading behavior.

[0005] Current technologies lack an automated verification system for network and storage offloading behaviors. Existing automated testing focuses on application-layer testing and lacks the ability to verify the correctness of the network / storage offloading behavior's activation status and execution path. Current technologies cannot jointly verify offloading behavior and trusted execution status. In a trusted sandbox environment, consistency confirmation is required between the offloading behavior execution results and the trusted metric chain results, but current testing technologies cannot achieve this. Existing testing systems struggle to cover cross-node / cross-capability integrated testing scenarios. In cloud-native, multi-node environments, offloading capabilities may span different nodes and virtualization environments, and traditional testing methods cannot effectively achieve comprehensive automated testing across capabilities. Current technologies lack fine-grained analysis of the relationship between offloading execution paths and trusted characteristics. Existing tests primarily focus on the final execution result, without addressing the detailed relationship between offloading path behavior and trusted execution status.

[0006] Furthermore, existing automated testing technologies mainly focus on software function verification, interface correctness verification, and performance regression testing, which have significant shortcomings when facing trusted execution environments with hardware offloading capabilities. It is impossible to automatically determine whether network offloading and storage offloading behaviors are truly enabled and effectively executed. Existing automated testing systems cannot automatically detect hardware coprocessing behavior, focusing only on final functions or performance indicators, and lack observable analysis of offloading execution path behavior.

[0007] The consistency between the unloading behavior and the trusted execution state cannot be jointly verified. The trustworthiness of trusted execution environments (such as trusted sandboxes) is often evaluated through mechanisms such as metric chains or remote proofs, but existing automated tests cannot jointly determine the consistency between the unloading behavior execution result and the trusted metric state, which can lead to missing test coverage in security-sensitive scenarios.

[0008] It cannot cover comprehensive integration testing scenarios in actual cloud platforms or multi-node environments. With the popularization of cloud-native and multi-node collaborative work, the offloading behavior may span multiple nodes and multiple virtualization environments, but existing testing tools do not provide the ability to automatically schedule integration tests across nodes and resources.

[0009] Therefore, there is an urgent need for an automated integrated testing method and system that can comprehensively verify the network offloading, storage offloading, and trusted sandbox operation status, so as to achieve more comprehensive and reliable trusted offloading system testing support. Summary of the Invention

[0010] The purpose of this application is to overcome the problems of the prior art by disclosing an automated integrated testing method and system for TIPU network offloading, storage offloading and trusted sandbox. It provides a systematic, automated and cross-scenario solution to address the shortcomings of the prior art in effectively testing hardware offloading behavior and determining its trusted execution state.

[0011] The objective of this application is achieved through the following technical solution: An automated integration testing method for TIPU network offloading, storage offloading, and trusted sandboxing, the automated integration testing method comprising: S1: Test configuration initialization, receiving network unloading test parameters, storage unloading test parameters and trusted sandbox trustworthiness verification parameters configured by users or automated systems, and combining them into a test case set; S2: Automatic creation of test environment. Based on the cloud platform scheduling engine, test instance environment is automatically created, and behavior collection components and trusted status collection components are deployed. S3: Uninstallation behavior data collection. Execute network uninstallation tests and storage uninstallation test cases on the created test instances, including: triggering network I / O processing behavior and collecting the triggering status of uninstallation path behavior; triggering storage I / O processing behavior and collecting the uninstallation execution status; and collecting behavior statistics and related event logs in real time. S4: Trusted State Acquisition. Execute trusted measurement instructions in parallel or according to a preset strategy within the trusted sandbox to acquire trusted state data, including: startup trusted measurement of the virtual machine / container sandbox, dynamic running trusted measurement value, and trusted measurement report returned by the trusted proof service. S5: Consistency analysis and diagnosis, compare according to consistency judgment rules, determine whether the uninstallation behavior is enabled and executed as expected, determine whether the uninstallation behavior is consistent with the trusted sandbox state, and locate and classify abnormal behaviors; S6: Test result output.

[0012] According to a preferred embodiment, step S2 includes: starting a virtual machine or security container with a specified configuration; mounting a preset driver or monitoring agent; and initializing the test data storage and log collection mechanism.

[0013] According to a preferred embodiment, step S6 includes generating an automated test result report, which includes: test pass / fail markers, behavioral consistency analysis graphs, and anomaly diagnostic details; and supports export, display, and regression analysis.

[0014] On the other hand, this application also discloses: An automated integration testing system for TIPU network offloading, storage offloading, and trusted sandboxing, wherein the automated integration testing system is implemented using the aforementioned method, and the automated integration testing system includes: The test-driven module receives test configurations and generates an actual executable sequence of test tasks and a corresponding data acquisition plan based on the configurations. The behavior acquisition module is used to monitor network offloading and storage offloading behavior during the test instance operation and write it to the acquisition cache or transmit it to the analysis engine in real time. The trusted state acquisition module is used to acquire trusted execution state information from the trusted sandbox during the testing process; The automatic scheduling and execution module is used to interface with the cloud platform scheduling engine, dynamically create test environments based on test tasks, and automatically arrange test tasks to be distributed and executed among various nodes according to the reservation strategy. The results analysis and reporting module is used to perform consistency analysis on the collected uninstallation behavior data and trusted status data, including: determining whether the test passes or fails based on predefined rules, locating abnormal behavior, and outputting a structured test report.

[0015] According to a preferred embodiment, the test configuration includes network offload test parameters, storage offload test parameters, and trusted sandbox configuration parameters.

[0016] According to a preferred embodiment, the network unloading and storage unloading behavior includes: unloading function enabled status, unloading path triggering event, I / O function call trajectory and related statistical data.

[0017] According to a preferred embodiment, the trusted execution status information includes trusted metric chain data, remote proof return information, and sandbox operation attitude value.

[0018] According to a preferred embodiment, the cloud platform scheduling engine includes Kubernetes and OpenStack.

[0019] According to a preferred embodiment, the structured test report output by the results analysis and reporting module supports chart visualization.

[0020] According to a preferred embodiment, the test-driven module, behavior acquisition module, trusted state acquisition module, automatic scheduling and execution module, and result analysis and reporting module are interconnected through standardized APIs and message buses to collaboratively complete the entire automated integration testing process.

[0021] The aforementioned main solution and its various further alternative solutions can be freely combined to form multiple solutions, all of which are solutions that can be adopted and are claimed in this application. Those skilled in the art, after understanding the solution of this application, will realize that there are many combinations based on the prior art and common general knowledge, all of which are technical solutions to be protected in this application, and will not be exhaustively listed here.

[0022] The beneficial effects of this application are: (1) Automated verification of the effectiveness of hardware unloading behavior This application achieves automated detection of network unloading and storage unloading behavior through behavior acquisition module and consistency judgment rules. It can automatically determine whether the specified unloading mechanism is enabled and whether it is executed according to the design path, thereby overcoming the defect of traditional testing system that the unobservable unloading behavior is not possible.

[0023] Unlike relying solely on performance metrics, behavior acquisition and path analysis provide a fine-grained observation of the dynamic execution of unloading behavior.

[0024] (2) Enhance trusted detection capabilities through joint trusted state verification This application combines the results of unloading behavior collection with the trusted measurement status data in the trusted sandbox to objectively determine the consistency and security of unloading behavior in the trusted environment, thus achieving "two-way verification" (behavioral consistency + trusted measurement consistency).

[0025] Compared to verifying only the trust status or the result of the behavior execution, this invention realizes the linkage judgment between behavior and trustworthiness.

[0026] (3) Support automatic integration test execution across nodes of the cloud platform The automatic scheduling and execution module can interface with various cloud scheduling platforms to automatically schedule test tasks in a wide-area deployment environment, thereby improving the test coverage and repeatability in large-scale deployment scenarios.

[0027] This is especially important for distributed, cloud-native, and containerized application deployment environments, effectively reducing testing and maintenance costs.

[0028] (4) Automatic analysis and reporting capabilities and anomaly diagnosis capabilities This application integrates structured data analysis and visualization output mechanisms, which can automatically generate detailed test reports and provide location suggestions for consistency anomalies, enhancing the readability and operability of test results.

[0029] (5) Improve testing efficiency and comprehensive coverage By automating the entire process, this invention avoids manual intervention, automating everything from test configuration, execution, data collection to result output, improving testing efficiency and ensuring multi-dimensional test coverage (unload behavior + reliability). Attached Figure Description

[0030] Figure 1 This is a schematic diagram of the automated integration testing method of this application; Figure 2 This is a schematic diagram of the principle structure of the automated integration testing system of this application. Detailed Implementation

[0031] The following specific examples illustrate the implementation of this application. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be noted that, unless otherwise specified, the following embodiments and features in the embodiments can be combined with each other.

[0032] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0033] In the description of this application, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, or the orientation or positional relationship commonly used when the product of this application is in use. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation on this application. In addition, the terms "first," "second," and "third," etc., are only used to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0034] In the description of this application, it should also be noted that, unless otherwise expressly specified and limited, the terms "set up," "install," "connect," and "link" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0035] Furthermore, it should be noted that unless otherwise specified in this application, the specific structures, connections, positions, power sources, etc. involved are all things that a person skilled in the art can know without creative effort based on the prior art.

[0036] Example 1 refer to Figure 1 As shown in the figure, an automated integration testing method for TIPU network offloading, storage offloading, and trusted sandbox is illustrated. The automated integration testing method includes the following steps.

[0037] Step S1: Test configuration initialization, collect network unloading test parameters, storage unloading test parameters and trusted sandbox trustworthiness verification parameters configured by users or automated systems, and combine them into a test case set.

[0038] Step S2: Automatic creation of the test environment. The test instance environment is automatically created based on the cloud platform scheduling engine, and the behavior collection component and trusted status collection component are deployed.

[0039] Prior to this, step S2 includes: starting a virtual machine or security container with the specified configuration; mounting a preset driver or monitoring agent; and initializing the test data storage and log collection mechanism.

[0040] Step S3: Unloading Behavior Data Collection. Execute network unloading and storage unloading test cases on the created test instance, including: triggering network I / O processing behavior and collecting the triggering status of unloading path behavior; triggering storage I / O processing behavior and collecting the unloading execution status; and collecting behavior statistics and related event logs in real time. Supports different hardware unloading platforms (such as DPU, SmartNIC, IPU, etc.).

[0041] Step S4: Trusted State Acquisition. Execute trusted measurement instructions in parallel or according to a preset strategy within the trusted sandbox to acquire trusted state data, including: the startup trusted measurement of the virtual machine / container sandbox, the dynamic running trusted measurement value, and the trusted measurement report returned by the trusted proof service.

[0042] Step S5: Consistency analysis and diagnosis. Based on the consistency judgment rules, compare the results to determine whether the uninstallation behavior is enabled and executed as expected, whether the uninstallation behavior is consistent with the trusted sandbox state, and locate and classify abnormal behaviors.

[0043] Step S6: Test Result Output. This includes generating an automated test result report, which includes: test pass / fail markers, behavioral consistency analysis graphs, and anomaly diagnostic details; and supports export, display, and regression analysis.

[0044] This method can dynamically adjust the scheduling mode according to the test scale, task priority and node resources, and supports parallel execution and result merging.

[0045] Example 2 refer to Figure 2As shown, based on Embodiment 1, this embodiment also discloses an automated integration testing system for TIPU network offloading, storage offloading, and trusted sandbox, which is implemented using the method described in Embodiment 1.

[0046] The automated integration testing system of this application includes: a test-driven module, a behavior acquisition module, a trusted state acquisition module, an automatic scheduling and execution module, and a result analysis and reporting module.

[0047] Preferably, the test driver module is used to receive test configuration and generate an actual executable test task sequence and a corresponding data acquisition plan based on the configuration.

[0048] Furthermore, the test configuration includes network offload test parameters, storage offload test parameters, and trusted sandbox configuration parameters.

[0049] Preferably, the behavior acquisition module is used to monitor network unloading and storage unloading behaviors during the test instance operation, and write them to the acquisition cache or transmit them to the analysis engine in real time.

[0050] The network unloading and storage unloading behaviors include: the unloading function's enabled status, unloading path trigger events, I / O function call trajectories, and related statistical data.

[0051] Preferably, the trusted state acquisition module is used to acquire trusted execution state information from the trusted sandbox during the testing process. The trusted execution state information includes trusted metric chain data, remote proof return information, and sandbox operation attitude values.

[0052] Preferably, the automatic scheduling and execution module is used to interface with the cloud platform scheduling engine, dynamically create test environments based on test tasks, and automatically distribute and execute test tasks across various nodes according to a reservation strategy. The cloud platform scheduling engine includes Kubernetes and OpenStack.

[0053] Preferably, the results analysis and reporting module is used to perform consistency analysis on the collected uninstallation behavior data and trusted status data, including: judging whether the test passes or fails based on predefined rules, locating abnormal behavior, and outputting a structured test report.

[0054] By jointly analyzing the results of unloading behavior collection with the trust measurement status data within the trusted sandbox, the consistency and security of unloading behavior in a trusted environment can be objectively determined, achieving "two-way verification" (behavioral consistency + trust measurement consistency). Compared to verifying only the trust status or behavior execution results separately, this invention achieves a linked judgment of behavior and trustworthiness.

[0055] The structured test report output by the results analysis and reporting module supports chart visualization.

[0056] Preferably, the test-driven module, behavior acquisition module, trusted state acquisition module, automatic scheduling and execution module, and result analysis and reporting module are interconnected through standardized APIs and message buses to collaboratively complete the entire automated integration testing process.

[0057] This application achieves automated detection of network and storage unloading behaviors through a behavior acquisition module and consistency judgment rules. It can automatically determine whether a specified unloading mechanism is enabled and whether the designed path is followed, thereby overcoming the shortcomings of traditional testing systems that cannot observe unloading behavior. Unlike relying solely on performance indicators, behavior acquisition and path analysis provide a fine-grained ability to observe the dynamic execution of unloading behavior.

[0058] It supports automatic cross-node integration and test execution on cloud platforms. Through its automatic scheduling module, it can interface with various cloud scheduling platforms to automatically schedule test tasks in wide-area deployment environments, improving test coverage and repeatability in large-scale deployment scenarios. This is particularly important for distributed, cloud-native, and containerized application deployment environments, effectively reducing test maintenance costs.

[0059] This invention integrates structured data analysis and visualization output mechanisms, which can automatically generate detailed test reports and provide location suggestions for consistency anomalies, enhancing the readability and operability of test results. It improves testing efficiency and comprehensive coverage by automating the entire process, eliminating manual intervention. From test configuration, execution, data collection to result output, everything is automated, improving testing efficiency and ensuring multi-dimensional test coverage (unloading behavior + reliability).

[0060] This application can be applied to virtual machine integration testing based on TIPU Trusted Computing Board and container automated testing based on TIPU Trusted Computing Board.

[0061] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. An automated integration testing method for TIPU network offloading, storage offloading, and trusted sandbox, characterized in that, The automated integration testing method includes: S1: Test configuration initialization, receiving network unloading test parameters, storage unloading test parameters and trusted sandbox trustworthiness verification parameters configured by users or automated systems, and combining them into a test case set; S2: Automatic creation of test environment. Based on the cloud platform scheduling engine, test instance environment is automatically created, and behavior collection components and trusted status collection components are deployed. S3: Uninstallation behavior data collection. Execute network uninstallation tests and storage uninstallation test cases on the created test instances, including: triggering network I / O processing behavior and collecting the triggering status of uninstallation path behavior; triggering storage I / O processing behavior and collecting the uninstallation execution status; and collecting behavior statistics and related event logs in real time. S4: Trusted State Acquisition. Execute trusted measurement instructions in parallel or according to a preset strategy within the trusted sandbox to acquire trusted state data, including: startup trusted measurement of the virtual machine / container sandbox, dynamic running trusted measurement value, and trusted measurement report returned by the trusted proof service. S5: Consistency analysis and diagnosis, compare according to consistency judgment rules, determine whether the uninstallation behavior is enabled and executed as expected, determine whether the uninstallation behavior is consistent with the trusted sandbox state, and locate and classify abnormal behaviors; S6: Test result output.

2. The automated integration testing method for TIPU network offloading, storage offloading, and trusted sandbox as described in claim 1, characterized in that, Step S2 includes: starting a virtual machine or security container with the specified configuration; mounting a preset driver or monitoring agent; and initializing the test data storage and log collection mechanism.

3. The automated integration testing method for TIPU network offloading, storage offloading, and trusted sandbox as described in claim 1, characterized in that, Step S6 includes generating an automated test result report, which includes: test pass / fail markers, behavioral consistency analysis graphs, and anomaly diagnosis details; and supports export, display, and regression analysis.

4. An automated integration testing system for TIPU network offloading, storage offloading, and trusted sandboxing, characterized in that, The automated integration testing system is implemented using the method described in any one of claims 1 to 3, and the automated integration testing system comprises: The test-driven module receives test configurations and generates an actual executable sequence of test tasks and a corresponding data acquisition plan based on the configurations. The behavior acquisition module is used to monitor network offloading and storage offloading behavior during the test instance operation and write it to the acquisition cache or transmit it to the analysis engine in real time. The trusted state acquisition module is used to acquire trusted execution state information from the trusted sandbox during the testing process; The automatic scheduling and execution module is used to interface with the cloud platform scheduling engine, dynamically create test environments based on test tasks, and automatically arrange test tasks to be distributed and executed among various nodes according to the reservation strategy. The results analysis and reporting module is used to perform consistency analysis on the collected uninstallation behavior data and trusted status data, including: determining whether the test passes or fails based on predefined rules, locating abnormal behavior, and outputting a structured test report.

5. The automated integration testing system for TIPU network offloading, storage offloading, and trusted sandbox as described in claim 4, characterized in that, The test configuration includes network unloading test parameters, storage unloading test parameters, and trusted sandbox configuration parameters.

6. The automated integration testing system for TIPU network offloading, storage offloading, and trusted sandbox as described in claim 5, characterized in that, The network unloading and storage unloading behaviors include: the unloading function's enabled status, unloading path trigger events, I / O function call trajectories, and related statistical data.

7. The automated integration testing system for TIPU network offloading, storage offloading, and trusted sandbox as described in claim 6, characterized in that, The trusted execution status information includes trusted metric chain data, remote proof return information, and sandbox operation attitude value.

8. The automated integration testing system for TIPU network offloading, storage offloading, and trusted sandbox as described in claim 4, characterized in that, The cloud platform scheduling engine includes Kubernetes and OpenStack.

9. The automated integration testing system for TIPU network offloading, storage offloading, and trusted sandbox as described in claim 4, characterized in that, The structured test report output by the results analysis and reporting module supports chart visualization.

10. The automated integration testing system for TIPU network offloading, storage offloading, and trusted sandbox as described in claim 4, characterized in that, The test-driven module, behavior acquisition module, trusted state acquisition module, automatic scheduling and execution module, and result analysis and reporting module are interconnected through standardized APIs and message buses to collaboratively complete the entire automated integration testing process.

Images