Modular test platform based on OSGi. NET framework

Abstract

The invention discloses a modular test platform based on an OSGi. NET framework. The modular test platform physically performs functional layering, functional combination is performed among layers by adopting a plug-in architecture, an automatic test process is decomposed into functional blocks through modular design, functional multiplexing of universal modules and rapid iteration of personalized modules are performed, and the test efficiency is improved. The networking service platform provides related network service interfaces for operation of all functions of the platform, and provides test resource management and maintenance, user permission maintenance, operation management optimization, data management, report management and data acquisition; the hardware support platform provides resource management of the test platform and hardware drive or communication protocols of communication required by the test platform. By adopting a plug-in architecture and a modular design, the efficiency, the flexibility and the maintainability of the test are remarkably improved through efficient resource management, so that the overall efficiency of the automatic test is improved.

Description

Technical Field

[0001] The present application relates to the field of automatic testing technology, and in particular to a modular testing platform based on the OSGi.NET framework. Background Art

[0002] In today's electronic technology field, automatic testing is undoubtedly a key means to improve the efficiency of product production. Products in this field have shown significant characteristics such as complex functions, rapid updates and iterations, and short production cycles, which has led to an increasing demand for automatic testing.

[0003] However, all the test platforms on the market adopt the traditional development model without exception. Their functions are highly coupled with each other, the scalability of the entire system is poor, and the inheritability of common functions is also relatively weak. These unfavorable factors have greatly restricted the rapid and efficient development of the test platform. Summary of the invention

[0004] The purpose of this application is to overcome the existing technical defects and provide a modular testing platform based on the OSGi.NET framework. By adopting a plug-in architecture, modular design, and efficient resource management, the efficiency, flexibility, and maintainability of the test are significantly improved, thereby improving the overall effectiveness of automated testing.

[0005] The purpose of this application is achieved through the following technical solutions:

[0006] In the first aspect, the present application proposes a modular testing platform based on the OSGi.NET framework, wherein the modular testing platform comprises an interconnected modular testing platform, a networked service platform and a hardware support platform;

[0007] The modular test platform is physically layered, with plug-in architecture used between layers for functional combination. The automatic test process is decomposed into functional blocks through modular design, and the function reuse of common modules and rapid iteration of personalized modules are performed to carry out test development and execution, equipment management, driver design, and data storage.

[0008] The network service platform is used to provide relevant network service interfaces for the operation of various functions of the platform, and provide test resource management and maintenance, user authority maintenance, operation management optimization, data management, report management, and data collection;

[0009] The hardware support platform is used to provide resource management of the test platform and the hardware drivers or communication protocols required for the communication of the test platform.

[0010] In one possible implementation, the modular testing platform includes multiple Bundle functional modules, which are used to test the basic functions of the testing platform, including a test execution plug-in, a data management plug-in, an interface control plug-in, a log management plug-in, a permission management plug-in, a report design plug-in, a device driver plug-in, a system management plug-in and a service management plug-in.

[0011] In a possible implementation, the Bundle function module defines a basic interface and plug-in attribute information, where the basic interface includes start, load, stop, uninstall, and update;

[0012] The plug-in attribute information includes basic information and extended information. The basic information defines the name, startup level and version of the plug-in, and the extended information includes node information.

[0013] In a possible implementation, the modular test platform includes a Common interface and a Component interface;

[0014] Common interface, which is used to define the standard way for all functional plug-ins to interact with the modular test platform and to make calls between plug-ins to ensure loose coupling between plug-ins;

[0015] Component interface, used to provide and call the common functional services of the modular test platform to achieve function reuse.

[0016] In one possible implementation, the test execution plug-in is used to load personalized and universally developed test cases provided by the modular testing platform, and provide a human-computer interaction interface, which includes starting a test, stopping a test, displaying a test indicator tree structure, displaying a real-time chart of test data, and displaying a test process log.

[0017] In a possible implementation, the data management plug-in includes a test record area, a test item area, and a detail data area, and is used for saving, querying, exporting, and searching product test record data based on a modular test platform.

[0018] In a possible implementation, the interface control plug-in is used to execute the visual interface protocol design function of the complex interface protocol, the dynamic modification of the protocol format, and the dynamic protocol monitoring function.

[0019] In a possible implementation, the log management plug-in is used to define log level information and record format information.

[0020] In one possible implementation, the permission management plug-in includes a feature set management architecture, a role management architecture, and a user management In one possible implementation, the report design plug-in is used to provide a report editing menu, report components, a report designer, a resource manager, a layer list, and resource properties to implement a custom report design function;

[0021] Device driver plug-in, used to perform visual design, display, and debugging functions of general instrument drivers;

[0022] System management plug-in, used to manage the status of running plug-ins and resources loaded by the test platform;

[0023] The service management plug-in is used to perform WebService service encapsulation and integration and provide external general functional interfaces.

[0024] The above-mentioned main scheme of the present application and its further options can be freely combined to form multiple schemes, all of which are schemes that can be adopted and claimed for protection in the present application; and in the present application, (non-conflicting options) options and other options can also be freely combined. After understanding the scheme of the present application, those skilled in the art can understand that there are multiple combinations based on the prior art and common knowledge, all of which are technical schemes to be protected by the present application, and they are not exhaustively listed here.

[0025] The present application discloses a modular test platform based on OSGi.NET framework. The modular test platform is physically functionally layered, and the layers are combined with plug-in architecture. The automatic test process is decomposed into functional blocks through modular design, and the function reuse of common modules and the rapid iteration of individual modules are performed. Test development and execution, equipment management, driver design, and data storage are performed. The networked service platform provides relevant network service interfaces for the operation of each function of the platform, and provides test resource management and maintenance, user authority maintenance, operation management optimization, data management, report management, and data collection. The hardware support platform provides resource management of the test platform and the hardware driver or communication protocol for communication required by the test platform. By adopting plug-in architecture, modular design, and efficient resource management, the efficiency, flexibility, and maintainability of the test are significantly improved, thereby improving the overall effectiveness of automated testing. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0027] Figure 1An architectural diagram showing the OSGi.NET framework.

[0028] Figure 2 A modular testing platform based on the OSGi.NET framework proposed in an embodiment of the present application is shown.

[0029] Figure 3 The flowchart of the platform loading the bundle according to the embodiment of the present application is shown.

[0030] Figure 4 A schematic diagram of a resource set of a Bundle module provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0031] The following describes the embodiments of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0032] Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making any creative work shall fall within the scope of protection of this application.

[0033] In the existing technology, all the test platforms available on the market adopt the traditional development model without exception. The functions are highly coupled with each other, the scalability of the entire system is poor, and the inheritability of common functions is also relatively weak. These unfavorable factors have greatly restricted the rapid and efficient development of the test platform.

[0034] Therefore, in order to solve the above-mentioned technical problems, the embodiment of the present application proposes a modular testing platform based on the OSGi.NET framework, which significantly improves the efficiency, flexibility and maintainability of the test by adopting a plug-in architecture, modular design and efficient resource management, thereby improving the overall effectiveness of automated testing. The modular testing platform is described in detail below.

[0035] Figure 1The architecture diagram of the OSGi.NET framework is shown, which shows the process of plug-ins with different functions interacting with the system core framework through interfaces. OSGi (Open Service Gateway Initiative) is a Java-based service platform specification that provides a dynamic modular system that allows applications to add, delete or update functional modules without restarting. OSGi.NET is the implementation of similar concepts in the .NET environment, aiming to bring the same dynamic modularity capabilities to .NET applications.

[0036] At the top level, there are n different function plugins (Function Plugin 1 to Function Plugin n), each with its own unique functions. Function plugins are connected to the Plugin Management Engine through the Plugin Interface. The Plugin Management Engine is the core of the entire system, responsible for processing and coordinating the functions of all these plugins to provide a unified user experience. Under the core framework of the system, there is a Common Run-time Library, which is a shared resource or basic tool set that all plugins need to use.

[0037] This structure allows users to add or remove specific functional modules as needed, making the software more flexible and easy to maintain. For example, if a function is no longer needed, the corresponding functional plug-in can be simply removed from the system without affecting other functions that are still in use.

[0038] Please refer to Figure 2 , Figure 2 A modular test platform based on the OSGi.NET framework proposed in an embodiment of the present application is shown, wherein the modular test platform includes an interconnected modular test platform, a networked service platform, and a hardware support platform;

[0039] The modular test platform is physically layered, with plug-in architecture used between layers for functional combination. The automatic test process is decomposed into functional blocks through modular design, and the function reuse of common modules and rapid iteration of personalized modules are performed to carry out test development and execution, equipment management, driver design, and data storage.

[0040] The network service platform is used to provide relevant network service interfaces for the operation of various functions of the platform, and provide test resource management and maintenance, user authority maintenance, operation management optimization, data management, report management, and data collection;

[0041] The hardware support platform is used to provide resource management of the test platform and the hardware drivers or communication protocols required for the communication of the test platform.

[0042] The modular test platform combines physical layering with modular design to achieve functional hierarchical division from hardware to software. Through the plug-in architecture, different functional modules can be flexibly combined, which not only ensures the stability and maintainability of the system, but also promotes rapid innovation and iteration of functions. Its key functions mainly cover core modules such as test development and execution, device management, driver design, and data storage. The test development and execution module supports the writing and execution of automated scripts, device management is responsible for the configuration and status monitoring of test hardware, driver design ensures effective communication between hardware and software, and data storage is used to save test results and related metadata.

[0043] The network service platform provides necessary network service support for various functions of the execution layer, which is used for efficient operation and management of platform services, ensuring smooth scheduling of test tasks and safe flow of data. It can perform but is not limited to allocation and maintenance of test resources, user rights management to ensure data security, continuous optimization of operation efficiency, data management and analysis services (such as report generation), and data collection, ensuring that all test-related data can be collected and analyzed in a timely and accurate manner.

[0044] The hardware support platform is responsible for the interconnection between all hardware devices and the test platform, and provides various drivers and communication protocols required for testing, such as instrument drivers, bus drivers, and fixture control, to ensure that test instructions can be accurately transmitted to physical devices. It not only includes hardware drivers, but also includes the management of the back-end services of the test platform, such as website services, document services, and data services, providing underlying infrastructure support to ensure the overall operating efficiency and stability of the platform.

[0045] In one possible implementation, the modular test platform tests execution plug-ins, data management plug-ins, interface control plug-ins, log management plug-ins, authority management plug-ins, report design plug-ins, device driver plug-ins, system management plug-ins, and service management plug-ins.

[0046] Bundle modules are independent functional components designed based on the OSGi.NET framework, which together constitute the core structure of the test platform. Each Bundle module focuses on a specific aspect of the platform, which improves the flexibility, maintainability and scalability of the system.

[0047] Test execution (BenchManage) is responsible for the execution management of test cases, including the arrangement of test plans, tracking of execution progress, and preliminary processing of test results. Data management (DataManage) handles all data storage, retrieval, and backup work related to testing to ensure data integrity and security. Interface control (InterfaceManage) manages the interface interaction between the platform and other systems or services, including API management and external system integration. Log management (LogManage) records various log information during the operation of the platform to facilitate error tracking, performance monitoring, and audit operations. Permission management (RbacManage) implements role-based access control (RBAC) to ensure that different users can access corresponding platform functions and data according to their roles. Report design (ReportManage) provides customized report generation functions to summarize and analyze test data and provide support for decision-making. Device driver (ResourceManage) manages drivers and services related to test hardware devices to ensure that the test platform can communicate effectively with various hardware devices. System management (RuntimeManage) monitors and manages the runtime status of the platform, including resource allocation, performance optimization, and fault handling. Service Management (ServiceManage) maintains the life cycle management of services within the platform to ensure service availability and service quality.

[0048] In one possible implementation, the test execution plug-in is used to load personalized and universally developed test cases provided by the modular testing platform, and provide a human-computer interaction interface, which includes starting a test, stopping a test, displaying a test indicator tree structure, displaying a real-time chart of test data, and displaying a test process log.

[0049] In a possible implementation, the data management plug-in includes a test record area, a test item area, and a detail data area, and is used for saving, querying, exporting, and searching product test record data based on a modular test platform.

[0050] In a possible implementation, the interface control plug-in is used to execute the visual interface protocol design function of the complex interface protocol, the dynamic modification of the protocol format, and the dynamic protocol monitoring function.

[0051] In a possible implementation, the log management plug-in is used to define log level information and record format information.

[0052] In one possible implementation, the permission management plug-in includes a feature set management architecture, a role management architecture, and a user management In one possible implementation, the report design plug-in is used to provide a report editing menu, report components, a report designer, a resource manager, a layer list, and resource properties to implement a custom report design function;

[0053] Device driver plug-in, used to perform visual design, display, and debugging functions of general instrument drivers;

[0054] System management plug-in, used to manage the status of running plug-ins and resources loaded by the test platform;

[0055] The service management plug-in is used to perform Web Service encapsulation and integration and provide external general functional interfaces.

[0056] The test execution plug-in loading platform provides test cases developed in two ways: personalized development and universal development. It provides a unified human-computer interaction interface, including start test, stop test, test indicator tree structure display, test data real-time chart display, and test process log display functions.

[0057] The data management plug-in implements functions such as saving, querying, exporting, and searching of product test record data based on the test platform, including a three-section clear display interface of the test record area, test item area, and detailed data area.

[0058] The interface control plug-in implements the visual interface protocol design function, dynamic modification of protocol format, and dynamic protocol monitoring function of complex interface protocols. The interface protocol refers to the communication rules agreed upon in advance by the test platform and the thing under test, which can be simply understood as the common constraints used by the communicating parties to conduct mutual conversations. The interface protocol defines the connection method used in the communication process, the data unit format, and the information and meaning that the information unit should contain.

[0059] The log management plug-in defines the log level, record format and other information. The test platform automatically records the loading logs of each plug-in and provides external services for each plug-in to call and fill in log information. The test platform provides users with a log viewing interface. The log information display format is: YYYY-MM-DD HH:MM:SS information level information content.

[0060] The permission management plug-in includes a three-layer management architecture of function set, role, and user. The three-layer architecture has unique identification and record field information. The function set includes basic function blocks such as test resources, basic modules, application market, data dictionary, log management, permission settings, device management, driver management, interface debugging, protocol management, use case editing, quality data, script engine, etc., which are extensible. The roles include system administrator, security administrator, audit administrator, developer, tester, debugger, report designer, use case developer, etc., which are extensible. User refers to a specific person, and the user is assigned a role. According to different roles, different permissions are implemented, that is, different function blocks are used.

[0061] The report design plug-in does not rely on developers, does not need to write code, and can design reports by itself. It provides functions such as report editing menu, report components, report designer, resource manager, layer list, resource properties, etc. to realize the design function of custom reports.

[0062] The device driver plug-in realizes the visual design, display and debugging functions of all general instrument drivers, including device type list, driver function list, driver function editing, adapter device, all supported device list area and debugging area.

[0063] The system management plug-in mainly manages the status of running plug-ins and the resources loaded by the test platform, including test platform authorization management, test platform plug-in management, and management of test resources such as communication bus, personalized device driver, test indicators, test cases, and test reports. Through this functional plug-in, users can quickly start and uninstall functional plug-ins, and realize functions such as importing authorization files and quickly uploading and downloading test resources.

[0064] The service management plug-in mainly implements the encapsulation and integration of the Web Service provided by the enterprise, and provides a general external functional interface, which is a unified entry for the test unit to use the service reference interface, avoiding the problem of repeated references when different functional plug-ins need to use service references. For example, the plug-in integrates the commonly used WebService functional interfaces such as enterprise ESB task data reporting, test report upload, download and deletion. Through the interface provided by this functional plug-in, you can quickly realize the functions of task data completion declaration and test report management.

[0065] The modular architecture based on OSGi.NET in this application enables the test platform to flexibly respond to changing needs. Each module can be upgraded and maintained independently, reducing the coupling between systems and improving the efficiency of development and maintenance.

[0066] In a possible implementation, the Bundle function module defines a basic interface and plug-in attribute information, where the basic interface includes start, load, stop, uninstall, and update;

[0067] The plug-in attribute information includes basic information and extended information. The basic information defines the name, startup level and version of the plug-in, and the extended information includes node information.

[0068] The Bundle functional module implements modular design by defining a set of standard interfaces and attribute information. The basic interface defines the core life cycle behaviors of the Bundle module, including startup, loading, stopping, unloading, and updating. Startup is the logic executed when the Bundle is activated to initialize the resources required by the module. Loading is the process of the Bundle being recognized by the system and loaded into the memory, ready for use. Stopping is the cleanup work performed when the Bundle is no longer needed to release the occupied resources. Uninstalling is to remove the Bundle from the system and completely release the resources and service registrations it occupies. Updating allows the old version of the Bundle to be replaced with the new version without interrupting the entire system service, achieving seamless upgrades.

[0069] The OSGi.NET framework uses standardized interfaces and configuration files to implement the whole process management of functional plug-ins from definition to loading and activation, ensuring the application's high modularity, scalability, and flexible configuration capabilities. The OSGi.NET framework implements the loading, startup, and management mechanisms of functional plug-ins (Bundles).

[0070] Loading and unloading functions: When the platform starts, the OSGi.NET framework automatically discovers and loads all available Bundles (functional plug-ins). The loading, activation, deactivation and unloading functions of these Bundles are managed by the framework itself, ensuring a high degree of modularity and flexibility.

[0071] During the Bundle loading process, please refer to Figure 3 , Figure 3 The sequence diagram of the platform loading the bundle proposed in the embodiment of the present application is shown. The platform is first started and enters the process of loading the bundle, then performs the operations of parsing the bundle dependency and loading the bundle dependency, and after completion enters the internal process of the plug-in startup sequence, including creating the bundle context, registering the extension point and extension information, and registering the service signal. When these processes are completed, the result of "Bundle loading completed" is displayed.

[0072] BundleActivator class: Each Bundle can contain a BundleActivator class, which defines two key methods - Start() and Stop(). The Start() method is called by the framework when the Bundle is activated. It is used to initialize the Bundle's services and register necessary components into the BundleContext context. This is actually loading the core functional interface service of the functional plug-in into the system to enable the function. Correspondingly, the Stop() method is called before the Bundle is deactivated or uninstalled to perform tasks such as resource cleanup and service deregistration.

[0073] Manifest.xml file: This is the metadata description file of each Bundle, which defines the basic information and configuration of the Bundle in detail, such as name, start level, activator class, author, version number, description, etc. This information is crucial for system management and dependency resolution between Bundles.

[0074] Extension points and PageNode: In Manifest.xml, extension points may also be defined, which is a mechanism used in OSGi to achieve interaction between plug-ins and functional extension. Each extension point can have multiple PageNodes, and each PageNode represents a specific functional component or unit in the functional plug-in. The implementation class, icon, classification and other metadata of this component are described in detail through attributes such as Class, Image, and Icon, so that the system can recognize and correctly display or call these functions.

[0075] Plugin properties are divided into two parts: basic information and extended information, which provide metadata support for system management of bundles.

[0076] Basic information is the necessary descriptive data for each bundle, which usually includes: Name: The unique identifier of the bundle, which is convenient for identification and reference. Startup level: Determines the order in which the bundles are loaded when the system starts. Bundles with higher priorities will be loaded before bundles with lower priorities. Version: Identifies the version number of the bundle, which helps manage dependencies and compatibility issues between different versions.

[0077] The extended information provides a more detailed configuration or feature description, for example: Node information: contains the deployment location, target platform or specific configuration details of the Bundle runtime, which helps to achieve more sophisticated inter-module collaboration or environmental adaptability. This design makes each Bundle a self-contained, reusable and easy-to-manage unit, greatly facilitating the expansion, upgrade and maintenance of the system.

[0078] Figure 4 The resource set diagram of the Bundle module provided in the embodiment of the present application is shown, including components such as the Manifest.xml plug-in simple file, .dll assembly files and other resource files, and the subdirectory contains .dll assembly files and other resource files. Different Bundle modules are called using the plug-in registration and release functions. The Bundle modules represent different functional modules within the test platform, and each module encapsulates a set of specific functions. Its modules can be independently developed, tested and deployed.

[0079] The plugin registration and release function means that when the test platform is started, all available plugins (i.e. functional modules) will be automatically discovered and loaded. This process usually involves a registry or central controller that is responsible for recording and managing the status of all plugins. Plugin release occurs when the platform is shut down or the plugin is no longer needed to release resources.

[0080] The present invention implements the design of the test platform in a plug-in manner based on OSGi.NET, and defines two common standard interfaces, Common and Common.Component, and basic function implementation classes to realize the functional interaction and data transmission between the functional units of different plug-ins. Common mainly implements the interface definition of basic common components such as basic functional models, data types, communication buses, test resources, runtime states, test indicators, and the static encapsulation of common methods. Common.Component mainly implements the above interfaces and defines its basic function implementation class. The mutual calls between the functional units of different bundles of the test platform and the calls of common functions are all realized through Common and Component, which greatly reduces the coupling relationship and management complexity between different functional plug-ins, and improves the reuse rate and maintenance efficiency of common functions.

[0081] In a possible implementation, the modular test platform includes a Common interface and a Component interface;

[0082] Common interface, which is used to define the standard way for all functional plug-ins to interact with the modular test platform and to make calls between plug-ins to ensure loose coupling between plug-ins;

[0083] Component interface, used to provide and call the common functional services of the modular test platform to achieve function reuse.

[0084] The Common interface and the Component interface are defined, where the Common interface defines the standard way for all functional plug-ins to interact with the platform. Regardless of the specific functions implemented by the plug-in, it follows the methods specified by the Common interface to expose services and receive requests. This can greatly reduce the coupling between modules, because each plug-in does not need to directly understand the specific implementation of other plug-ins, but only needs to communicate through the Common interface.

[0085] The common interface is used to call plugins, ensuring loose coupling between plugins. Even if a plugin is changed or replaced, as long as it complies with the common interface, it will not affect other plugins, ensuring the stability and scalability of the system.

[0086] The Component interface provides common functional services for the platform. For example, logging, error handling, configuration management, etc. Through the Component interface, functional plug-ins can easily reuse common services without having to re-implement them in each plug-in, which reduces code duplication and improves development efficiency and code quality. Using the Component interface to call common functions enables function reuse. For example, all plug-ins can use a unified logging method, which reduces development workload and maintains consistency within the system.

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

Claims

1. A modular testing platform based on OSGi.NET framework, characterized in that: The modular test platform includes a modular test platform, a networked service platform and a hardware support platform that are interconnected; The modular test platform is physically layered, with plug-in architecture used between layers for functional combination. The automatic test process is decomposed into functional blocks through modular design, and the function reuse of common modules and rapid iteration of personalized modules are performed to carry out test development and execution, equipment management, driver design, and data storage. The network service platform is used to provide relevant network service interfaces for the operation of various functions of the platform, and provide test resource management and maintenance, user authority maintenance, operation management optimization, data management, report management, and data collection; The hardware support platform is used to provide resource management of the test platform and the hardware drivers or communication protocols required for the communication of the test platform.

2. The modular test platform according to claim 1, characterized in that: The modular testing platform includes multiple Bundle functional modules, which are used to test the basic functions of the testing platform, including test execution plug-in, data management plug-in, interface control plug-in, log management plug-in, permission management plug-in, report design plug-in, device driver plug-in, system management plug-in and service management plug-in.

3. The modular test platform according to claim 2, characterized in that: The Bundle function module defines the basic interface and plug-in attribute information. The basic interface includes start, load, stop, unload and update; The plug-in attribute information includes basic information and extended information. The basic information defines the name, startup level and version of the plug-in, and the extended information includes node information.

4. The modular test platform according to claim 1, characterized in that: The modular test platform includes Common interface and Component interface; Common interface, which is used to define the standard way for all functional plug-ins to interact with the modular test platform and to make calls between plug-ins to ensure loose coupling between plug-ins; Component interface, used to provide and call the common functional services of the modular test platform to achieve function reuse.

5. The modular test platform according to claim 2, characterized in that: The test execution plug-in is used to load the personalized and universal test cases provided by the modular test platform, and provide a human-computer interaction interface, which includes starting the test, stopping the test, displaying the test indicator tree structure, displaying the test data in real-time charts, and displaying the test process log.

6. The modular test platform according to claim 2, characterized in that: The data management plug-in includes a test record area, a test item area, and a detailed data area, which are used for saving, querying, exporting, and searching product test record data based on a modular test platform.

7. The modular test platform according to claim 2, characterized in that: The interface control plug-in is used to execute the visual interface protocol design function of complex interface protocols, dynamically modify the protocol format, and dynamically monitor the protocol.

8. The modular test platform according to claim 2, characterized in that: Log management plug-in, used to define log level information and record format information.

9. The modular test platform according to claim 2, characterized in that: The permission management plug-in includes a feature set management architecture, a role management architecture, and a user management architecture. The feature set management architecture, the role management architecture, and the user management architecture all have unique identifiers and record field information.

10. The modular test platform according to claim 2, characterized in that: Report design plug-in, used to provide report editing menu, report components, report designer, resource manager, layer list, resource attributes, and realize the design function of custom reports; Device driver plug-in, used to perform visual design, display, and debugging functions of general instrument drivers; System management plug-in, used to manage the status of running plug-ins and resources loaded by the test platform; The service management plug-in is used to perform Web Service encapsulation and integration and provide external general functional interfaces.

Images