Distributed test management system

Through the distributed computer management system and many-to-many management architecture, the problems of high hardware requirements and unstable test results in the existing technology are solved, efficient test management and unified results are achieved, and maintenance costs and user technical thresholds are reduced.

CN119025434AInactive Publication Date: 2024-11-26MIKAS (ZHEJIANG) TECH CO LTD
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
CN202411501696.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-25
Publication Date
2024-11-26
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The existing test management system has high hardware requirements, high update costs, unstable test results, and is not suitable for unified management and result summary of large-scale use and mass production test scenarios.

Method used

Adopt a distributed computer management system, including test function servers, C/S connection management modules and user management solutions with different levels of permissions. Each system connects through the network to support many-to-management scenarios, reducing hardware dependence and maintenance costs, and increasing The independence and scalability of the subsystem.

Benefits of technology

Simplify the complexity, enhance the independence and stability of the subsystem, reduce maintenance costs, support many-to-management scenarios, improve the functions and performance of the subsystem, and reduce the user's technical threshold, which is suitable for large-scale and mass production testing scenarios. unified management and result summary.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025434A_ABST
    Figure CN119025434A_ABST
Patent Text Reader

Abstract

The invention relates to a distributed test management system, which solves the problems of high hardware requirement, high updating cost, unstable test result and the like of a management system in the prior art. According to the invention, a distributed computer management system is connected with a client, and a test function server, a C / S connection management module and user management schemes of different levels of permissions are included; all systems of the test function server are connected through a network or a communication interface; and the client controls and monitors a tested object through the test main system. According to the invention, an integrated multi-module combined architecture is replaced by a distributed subsystem architecture, so that the complexity is simplified, and the independence and stability of each subsystem are enhanced; a many-to-many management scene is supported, and the multiplexing degree and the specialty of the subsystem are improved; and mutual calling of codes is replaced by interface docking, so that the coupling degree between subsystems is reduced to the minimum, and the maintenance cost is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of test management, and in particular to a distributed test management system. Background Art

[0002] Test Management System (TMS) refers to a software tool or platform used to plan, manage, monitor the test process and generate test results. Currently, TMS is widely used in various testing activities in the software and product development life cycle. The software or product to be tested is generally called DUT, including test plan formulation, test environment planning, test case writing, test defect tracking, test process control, test report generation and analysis and other functions. TMS in the existing technology generally has the following characteristics: using WEB architecture to provide cross-platform device access capabilities; having data storage and management functions; having authority control and security management functions and other functions.

[0003] There are two management systems in the prior art: the on-site test solution adopts an integrated test management and test execution system, that is, all the basic functions of the TMS mentioned above are made into a complete app or background service system, which runs on a hardware platform with an operating system such as Windows or Linux. At the same time, the test management interface also runs on this hardware platform, which can be a WEB or an app program; because users need to deploy the TMS to any DUT site, this means that multiple DUTs may need to deploy multiple TMSs, including the hardware platform running the TMS: if the hardware meets the requirements, one TMS can test multiple DUT scenarios at the same time.

[0004] The remote testing solution deploys a test management server and client for local or remote management, and deploys the TMS on a server with higher hardware configuration. It is usually built as a WEB server, and then the DUT and TMS are deployed on the same test LAN. Users only need to access the TMS server through any client machine in the LAN to complete the test management function. During the test process, the test server and DUT need to be placed together, and the client can access them remotely through the network.

[0005] The above two testing schemes have the following disadvantages: All functions must be bound to a single hardware platform. As TMS functions become more and more complex, the operating conditions of the hardware platform will become more and more demanding, resulting in the difficulty of upgrading the already deployed hardware platform. Some hardware platforms may even need to be re-deployed due to limitations of certain hardware platforms. In addition, the platform must be bound one-to-one with the DUT, resulting in high hardware costs. For large-scale scenarios such as production lines, the human costs of system upgrades, synchronization, and maintenance of each TMS are often high; Since the hardware platform and software environment of TMS are not absolutely the same, they cannot achieve completely unified standards for the control of the test process and the judgment of the test results. There is a chance that the test results of the same DUT on different TMS will be inconsistent; For mass production testing scenarios, it is not conducive to the unified induction and summary of test results, and requires manual secondary integration, which is not in line with the original intention of automated testing; The layout and management of test cases, control of the test process, and sharing of test technology will all be blocked by the space of the test site.

[0006] There is an urgent need for a new testing system that can solve the above problems. Summary of the invention

[0007] The present invention provides a distributed test management system, which solves the problems of high hardware requirements, high update cost, unstable test results, etc. in the prior art management system.

[0008] The technical solution of the present invention is implemented as follows: a distributed test management system, which adopts a distributed computer management system to connect to a client, including a test function server, a C / S connection management module and a user management solution with different levels of authority; the test function server includes a test main system, a drive subsystem, a simulation subsystem, a security subsystem, a storage subsystem, a defect subsystem, and a log subsystem; the systems of the test function server are connected through a network or a communication interface; the client controls and monitors the object under test through the test main system.

[0009] Furthermore, the driver subsystem includes drivers for classifying and managing DUT peripheral devices and a driver library that can be shared.

[0010] Furthermore, the simulation subsystem includes algorithm simulation.

[0011] Furthermore, the security subsystem includes a user management module, a security connection module, a security communication module, and an installation and storage module; the user management module is connected to the C / S connection management module and user management schemes with different levels of authority; the test main system calls the security connection module and the security communication module algorithms to complete security authentication.

[0012] Furthermore, the log subsystem provides log recording and access interface to the test main system.

[0013] Preferably, the test function server includes a custom system that defines an API in accordance with a standard format of the system.

[0014] A distributed test management system disclosed in the present invention replaces an integrated multi-module combination architecture with a distributed subsystem architecture, simplifies the complexities, and enhances the independence and stability of each subsystem; eliminates the over-reliance on hardware platforms and the trouble of upgrading and replacing them; the reusable CBB subsystem design supports many-to-many management scenarios, and improves the reusability and professionalism of the subsystem; replaces mutual code calls with interface docking, and reduces the coupling between subsystems to a minimum, thereby reducing maintenance costs; each subsystem is a complete and independent existence, which greatly improves the upper limit of subsystem functions and performance, and has extremely high scalability; the refined subsystem framework leaves the complex processing mechanism to the distributed platform itself, and leaves the simple and clear usage method to the user, so that the user can easily use the system without having to control the overall situation, which greatly reduces the user's technical threshold. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0016] Figure 1 : System block diagram of the present invention. DETAILED DESCRIPTION

[0017] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0018] The present invention discloses a distributed test management system, which adopts a distributed computer management system to connect to a client, including a test function server, a C / S connection management module and user management solutions with different levels of authority; the test function server includes a test main system, a drive subsystem, a simulation subsystem, a security subsystem, a storage subsystem, a defect subsystem and a log subsystem; the systems of the test function server are connected through a network or a communication interface; the client controls and monitors the object under test through the test main system.

[0019] The main test system is responsible for connecting to the client upwards and forming a complete distributed test control management system with each subsystem downwards. It directly or indirectly connects and controls the DUT array, is responsible for controlling the execution process of the entire test and data collection and summarization, and ultimately generates test reports and other information.

[0020] A TMS can have one or more test master systems. A client can only connect to one test master system for control and management at the same time. However, a test master system allows multiple clients to log in at the same time, but there can only be one master client, and the others are slave clients. The master client has the highest controller, and the slave client only has a subordinate controller. That is to say, when the master and slave control or edit a test case at the same time, only the master can take effect, and the master and slave roles are not fixed. As the test business is executed, each client can re-election for the master. This management method is particularly suitable for clustered test management scenarios such as schools, laboratories or related verification institutions.

[0021] Furthermore, the driver subsystem includes drivers for classifying and managing DUT peripheral devices and a driver library that can be shared. This distributed TMS supports testing scenarios of physical products such as mobile phone signal testing, router traffic testing, and Bluetooth headset wireless communication quality testing. In this scenario, most DUTs require the cooperation of peripheral instruments or peripheral devices to complete the test. For example, to test mobile phone signals or traffic, the test process requires at least one wireless RRU or DU device. In order to achieve the effect of automated testing, the distributed TMS independently defines a driver subsystem to classify and manage drivers for various DUT peripheral devices and form a driver library that can be shared.

[0022] These drivers are actually API interfaces that can control devices or instruments through the network or other peripheral interfaces, such as controlling the DU / RRU to send traffic of specified bandwidth, controlling the mobile phone to wirelessly send and receive packets to simulate Internet access, etc.

[0023] Furthermore, the simulation subsystem includes algorithm simulation. The simulation subsystem is also called a simulator, and there are mainly two types of simulation objects: one is to simulate actual instruments, such as using software to write a TCP / UDP packet sending tool. Under the condition that there is no need to accurately control the flow or simulate the packet loss environment of the real network, it can completely use software programming to simulate this function, which not only saves the cost of the test instrument but also improves the integration of the system; the other is to simulate the real scene that cannot be completed by instruments and meters, but is not convenient to implement, such as the base station switching of mobile phones, the hotspot switching of WIFI, and the external environment such as rainy and snowy weather, sports collision, high temperature and high pressure, etc. These can be simulated by certain software algorithms, without having to place the DUT in a real environment for testing.

[0024] The implementation of some simulators is extremely complex and requires a higher hardware platform to run. For example, channel simulation is generally deployed on a separate hardware platform, and then connected to our distributed TMS network through an interface and accessed through a unified encapsulated API interface.

[0025] Furthermore, the security subsystem includes a user management module, a security connection module, a security communication module, and an installation and storage module; the user management module is connected to the C / S connection management module and user management schemes with different levels of authority; the test main system calls the security connection module and the security communication module algorithms to complete security authentication.

[0026] The entire subsystem is mainly responsible for ensuring the user management, secure connection, secure communication, installation and storage functions of the test system. The user login and permission management system controls the complex connection scenarios of multiple clients to multiple TMSs.

[0027] In terms of user management, this system divides users into five roles: super administrator, administrator, engineer, operator, and maintainer. Each role has different operating permissions. They can only enter the TMS system and perform corresponding controls within their assigned permissions. For example, we design the operator to not have the permission to edit test cases. He can only execute mechanically, and the editing of test cases is done by the engineer role. The engineer must be someone who is very familiar with the functional characteristics of the DUT.

[0028] In terms of secure connection and communication, this system provides highly secure encryption, decryption and verification algorithms. The test main system can use API to call these algorithms to complete security authentication and other functions.

[0029] The main feature of the storage subsystem is that it has high requirements for disk capacity and access speed. There are two purposes for dividing it independently: one is that it is not tied to the main system and any functional business, and runs as a storage service to prevent other systems or business crashes from affecting data storage. For example, the crash of the main service A will not affect the continued execution of the main service B; the other purpose is to facilitate the transfer of test data or the expansion of disk capacity, and this process can be completed while the storage business is running without interrupting the business. The storage subsystem does not have high requirements for its own CPU and other hardware, as long as it can drive the memory and ensure basic communication efficiency.

[0030] The defect management of the defect subsystem is also known as BUG management, which is mainly used to record and trace back the problems that occurred during the DUT test process, as well as the probability, time, and cause of the problems. Therefore, the simplest defect management subsystem mainly has storage and indexing functions. In this case, it can be merged with the main system or storage subsystem. However, a slightly more complex defect management system generally also has the following functions: defect status management, defect allocation and responsible person management, defect update, defect report generation and analysis, defect notification and reminder, etc. These functions should be able to be seen without in-depth analysis. It is similar to a defect tracking management system, that is, in addition to basic storage and indexing permissions, it must also support a complete defect tracking management system. In this case, it is not suitable to integrate it with the TMS main system or storage subsystem, but it should be laid out as a separate subsystem. Similarly, it should be merged into the TMS system through a unified encapsulated API.

[0031] Furthermore, the log subsystem provides log recording and access interfaces to the test main system. Log management is a key function of the test system, and is a key module related to how the data automatically recorded by the machine during the test process is converted into test data or meaningful test reports that can be easily read by the test user. The primary task of the log subsystem is to provide log recording and access interfaces to the TMS main system for use in recording or viewing the original log information automatically generated during the execution of the use case; secondly, it has a log analysis function, which can calculate the success rate or failure rate based on pass / fail statistics from the original log, obtain test parameter values ​​as the basis for product quality binning, read detailed error logs and trends, etc., to help users discover and solve potential problems, and provide reasons for test failures and possible solutions. At the same time, it also supports the export and sharing of logs, and supports control measures such as security authorization for sensitive logs.

[0032] Preferably, the test function server includes a custom system that defines an API in accordance with the standard format of the system. The custom subsystem is added to the distributed TMS architecture for use.

[0033] When executing the test task, the background and DUT are built on the distributed test function servers, and each function server, DUT and client are connected through a communication interface.

[0034] The client enters the system through the operation interface, connects to and controls the test main system, monitors and adjusts the test execution process in real time, and can also adjust the DUT array; view logs, defect reports and test reports.

[0035] A distributed test management system disclosed in the present invention replaces an integrated multi-module combination architecture with a distributed subsystem architecture, simplifies the complexities, and enhances the independence and stability of each subsystem; eliminates the over-reliance on hardware platforms and the trouble of upgrading and replacing them; the reusable CBB subsystem design supports many-to-many management scenarios, and improves the reusability and professionalism of the subsystem; replaces mutual code calls with interface docking, and reduces the coupling between subsystems to a minimum, thereby reducing maintenance costs; each subsystem is a complete and independent existence, which greatly improves the upper limit of subsystem functions and performance, and has extremely high scalability; the refined subsystem framework leaves the complex processing mechanism to the distributed platform itself, and leaves the simple and clear usage method to the user, so that the user can easily use the system without having to control the overall situation, which greatly reduces the user's technical threshold.

[0036] Of course, without departing from the spirit and essence of the invention, technicians familiar with the field should be able to make various corresponding changes and modifications based on the invention, but these corresponding changes and modifications should all fall within the scope of protection of the claims attached to the invention.

Claims

1. A distributed test management system, using a distributed computer management system to connect clients, characterized in that: Including test function server, C / S connection management module and user management solutions with different levels of authority; The test function server includes a test main system, a drive subsystem, a simulation subsystem, a security subsystem, a storage subsystem, a defect subsystem, and a log subsystem; The test function server systems are connected via a network or communication interface; The client controls and monitors the object under test through the test main system.

2. A distributed test management system according to claim 1, characterized in that: The driver subsystem includes drivers for classifying and managing DUT peripheral devices and a driver library that can be shared.

3. A distributed test management system according to claim 2, characterized in that: The simulation subsystem includes algorithm simulation.

4. A distributed test management system according to claim 3, characterized in that: The security subsystem includes a user management module, a security connection module, a security communication module, and an installation and storage module; the user management module is connected to the C / S connection management module and user management schemes with different levels of authority; the test main system calls the security connection module and the security communication module algorithms to complete security authentication.

5. A distributed test management system according to claim 4, characterized in that: The log subsystem provides log recording and access interface to the test main system.

6. A distributed test management system according to any one of claims 1 to 5, characterized in that: The test function server includes a custom system that defines an API in accordance with the standard format of the system.

Citation Information

Patent Citations

  • Integration test system of distributed software system and method thereof

    CN101140541A

  • Distributed test method, system and test server

    CN101447892A

  • Safety distributed test framework system and test method thereof

    CN102141962A

  • Software testing automation framework (STAF)-based fault injection automation testing platform and method for high-end fault-tolerant computer

    CN102354298A

  • A network test management system and method for commercial vehicle based on distributed system

    CN109086213A