WO2017140084A1

WO2017140084A1 - Test method and device

Info

Publication number: WO2017140084A1
Application number: PCT/CN2016/090182
Authority: WO
Inventors: 陈若愚; 周敏
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-02-15
Filing date: 2016-07-15
Publication date: 2017-08-24
Also published as: CN107085552A

Abstract

A test method and a device, to be applied to a network management alarm, the method comprising: receiving an alarm message generated by a test case library; and performing an alarm test by comparing alarm details in a current version and in historical versions of the received alarm message. The embodiments of the present invention improve the test efficiency of network management alarm.

Description

Test method and device

Technical field

This document relates to, but is not limited to, the field of data network communication, and in particular to a test method and apparatus applied to network management alarms.

Background technique

With the continuous development of network technology, operators' management capabilities and quality requirements for network management software are gradually improving. The testing process must continuously improve fault discovery and analysis capabilities to cope with increasing demands. In the network management system, alarms are a basic function. Almost all network access tests, external tests, and demonstration functions need to display alarm management capabilities. Ensuring the quality of the alarm test is a task that testers need to pay special attention to.

The alarm test phase includes: unit test, integration test, smoke test, system test, regression test, and so on. In the related art, when the alarm test is performed, the test is performed one by one according to the function in a specific version, and the test result and the reason details are independently dispersed. When the convergence trend, the cause of the fault, and the high fault point of the fault need to be analyzed in different dimensions and types, the method cannot be efficiently and quickly. Provides overall data support.

In view of the problem that the efficiency of the network management alarm test in the related art is too low, the related technology has not proposed an effective solution.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a testing method and device, which can improve the efficiency of the network management alarm test.

According to an aspect of the present invention, a test method is provided, including: receiving an alarm message generated by a test case library; and performing an alarm test by comparing the current version of the received alarm message with the alarm details in the historical version.

Optionally, before the alarm test, the testing method further includes:

Obtaining alarm details in the current version and the historical version of the alarm packet;

The alarm details include: an alarm number, an alarm level, a network element location, and an alarm occurrence. Time, alarm code, location within the NE, alarm type, and confirmation status;

And storing the obtained alarm details in the current version of the alarm message in a database.

Optionally, the storing, in the database, the alarm details in the current version of the alarm message includes:

In the case that the current version is the official version, the alarm details of the alarm message are stored in the database.

Optionally, the performing the alarm test comprises:

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message to generate a comparison file; performing an alarm test according to the generated comparison file.

Optionally, comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message includes:

Determining whether the alarm details in the current version of the alarm message are correct;

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message when the alarm details in the current version of the alarm message are correct. .

Optionally, after the comparing the alarm details in the current version with the alarm details in the historical version of the alarm message, the testing method further includes:

If the alarm details in the historical version of the alarm message are in error, modify or delete the alarm details of the error.

Optionally, after comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message, the testing method further includes:

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message to be compared, where the alarm details of the historical version are to be compared;

If there is no alarm detail to be compared with the historical version, it is determined whether there is an alarm message to be tested in the test case database, and the test is received if there is an alarm message to be tested in the test case database. The alarm message to be tested generated by the use case library.

Optionally, the testing method further includes:

When it is determined that there is no alarm message to be tested in the test case database, the data of the comparison file is analyzed, and an alarm analysis report is output.

Optionally, the method for analyzing data of the comparison file includes at least one of the following:

Data drilling, data mining, data storage.

According to another aspect of the embodiments of the present invention, a test apparatus is provided, where the test apparatus is applied to a network management alarm, including:

a receiving module, configured to receive an alarm message generated by the test case library;

The test module is configured to perform an alarm test by comparing the current version of the received alarm message with the alarm details in the historical version.

The testing device further includes:

Obtaining a module, configured to obtain the alarm details in the current version and the historical version of the alarm message;

The alarm details include: an alarm number, an alarm level, a network element location, an alarm occurrence time, an alarm code, an intra-network element location, an alarm type, and an acknowledgement status;

The storage module is configured to store the obtained alarm details in the current version of the obtained alarm message in a database.

Optionally, the test module is set to:

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message to generate a comparison file;

Perform an alarm test based on the generated comparison file.

Optionally, the test module is set to:

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message when the alarm details in the current version of the alarm message are correct. , generating a comparison file;

Perform an alarm test based on the generated comparison file.

Optionally, the testing device further includes an alarm processing module, configured to: after comparing the alarm details in the current version with the alarm details in the historical version of the alarm message, in the alarm message If the alarm details in the historical version are in error, modify or delete the alarm details of the error.

Optionally, the testing device further includes a comparison processing module, configured to compare the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message,

Optionally, the comparison processing module is further configured to:

Compared with the related art, the technical solution provided by the embodiment of the present invention includes: receiving an alarm message generated by the test case database; performing an alarm test by comparing the current version of the received alarm message with the alarm details in the historical version. In the embodiment of the present invention, the technical solution for testing the alarm by comparing the alarm details of the alarm message in the current version and the historical version improves the efficiency of the network management alarm test.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a flow chart of a test method according to an embodiment of the present invention;

2 is a block diagram showing the structure of a test apparatus according to an embodiment of the present invention;

3 is a schematic structural diagram of a testing apparatus according to an embodiment of the present invention;

4 is a flow chart of a test method of an alternative embodiment of the present invention;

FIG. 5 is a flowchart of a test comparison file analysis process according to an embodiment of the present invention.

Embodiments of the invention

Embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

A test method and apparatus are provided in this embodiment. FIG. 1 is a flowchart of a test method according to an embodiment of the present invention. As shown in FIG. 1, the process includes:

Step 102: Receive an alarm message generated by the test case library.

Step 104: Perform an alarm test by comparing the current version of the received alarm message with the alarm details in the historical version.

Optionally, before the alarm test, the testing method of the embodiment of the present invention further includes:

Obtain the alarm details in the current version and the historical version of the alarm packet.

The alarm details in the current version of the obtained alarm packet are stored in the database.

Optionally, the foregoing alarm details include: an alarm number, an alarm level, a network element location, an alarm occurrence time, an alarm code, an intra-network element location, an alarm type, and an acknowledgement status. The test method is applied to the network management alarm;

The invention obtains the alarm details from the current version of the alarm message, and stores the current version of the alarm details in the database, and acquires the historical version of the alarm details.

Optionally, the foregoing database in the embodiment of the present invention may be dedicated to storing the alarm details generated by the testing method of the embodiment of the present invention.

Optionally, in the case that the current version is a temporary version, the alarm details of the temporary version may not be stored to save storage space. When the current version is the official version, the alarm details of the alarm packet are stored in the database.

In the embodiment of the present invention, the correctness of the alarm details can be regarded as a test result.

Optionally, performing the alarm test includes:

Optionally, comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message, including: obtaining the current version of the alarm details from the alarm message; determining the alarm The alarm details in the current version of the packet are correct. If the alarm details in the current version of the alarm packet are correct, the alarm details in the current version of the alarm packet and the alarm details in the history version of the alarm packet are comparing.

Optionally, after comparing the alarm details in the current version with the alarm details in the historical version of the alarm message, the test method further includes: if the alarm details in the current version of the alarm message are in error, Compare the alarm details of the alarm with the alarm details of the corresponding version.

Optionally, the foregoing determining whether the alarm details of the alarm message in the current version are correct may occur after the alarm details are stored in the database, and may be modified or deleted if the alarm details of the historical version of the alarm message are in error. Details of the error alarm.

Optionally, after comparing the alarm details in the current version of the alarm packet with the alarm details in the historical version of the alarm packet, the testing method further includes: if the alarm details of the historical version to be compared exist, the alarm is generated. The alarm details in the current version of the packet are compared with the alarm details in the historical version of the alarm packet to be compared; if there is no alarm detail to be compared with the historical version, it is determined whether there is a test sample library to be tested. The alarm packet receives the alarm packet to be tested generated by the test case database when there is an alarm packet to be tested in the test case database.

Optionally, the method of the embodiment of the present invention further includes: if the next alarm message to be tested does not exist, the data of the comparison file may be analyzed and processed, and an alarm analysis report is output. The above analysis processing may include, but is not limited to, one or more data processing of data drilling, data mining. The data processing methods such as data drilling and data mining are techniques commonly used by those skilled in the art, and the output alarm analysis includes a file report of data comparison generated according to data processing methods such as data drilling and data mining.

Through the above steps, the problem that the network management alarm test efficiency is too low in the related technology is solved, and the test efficiency is improved.

The embodiment of the present invention may be implemented by a server with an operating system as a hardware execution entity, for example, a server of the WINDOWS operating system.

Embodiments of the present invention provide a computer storage medium, which is stored in a computer storage medium. Computer executable instructions, computer executable instructions for performing the above test methods.

2 is a structural block diagram of a testing apparatus according to an embodiment of the present invention. As shown in FIG. 2, the apparatus includes:

The receiving module 22 is configured to receive an alarm message generated by the test case library;

The test module 24 is configured to perform an alarm test by comparing the alarm details in the current version and the historical version of the received alarm message.

The testing device further includes:

The obtaining module 20 is configured to obtain the alarm details in the current version and the historical version of the alarm message;

The storage module is configured to store the obtained alarm details in the current version of the alarm message in a database.

Optionally, the test module is set to:

The alarm details in the current version of the alarm packet are compared with the alarm details in the historical version of the alarm packet to generate a comparison file.

Perform an alarm test based on the generated comparison file.

Optionally, the test module is set to:

Determine whether the alarm details in the current version of the alarm packet are correct.

If the alarm details in the current version of the alarm packet are correct, the alarm details in the current version of the alarm packet are compared with the alarm details in the historical version of the alarm packet to generate a comparison file.

Perform an alarm test based on the generated comparison file.

Optionally, the testing device further includes an alarm processing module 210, configured to compare the alarm details in the current version with the alarm details in the historical version of the alarm message, and the alarm details in the historical version of the alarm message are incorrect. In case, modify or delete the alarm details of the error.

Optionally, the testing device further includes a comparison processing module 212 configured to set the current alarm message After the alarm details in the version are compared with the alarm details in the historical version of the alarm message,

If there is no alarm detail to be compared with the historical version, it is determined whether there is an alarm message to be tested in the test case database. If there is an alarm message to be tested in the test case database, the test case library is generated. Alarm packet to be tested.

Optionally, the comparison processing module is further configured to:

When it is determined that there is no alarm message to be tested in the test case library, the data of the comparison file is analyzed, and an alarm analysis report is output.

The invention is further described below in conjunction with alternative embodiments.

The embodiment of the present invention improves the efficiency of the system test by comparing and analyzing the existing version with the historical version, and lays a solid foundation for the field test and the network access test. The comparison report based on the historical database visually shows the differences and changes between the versions, and it is very beneficial for the analysis to find hidden faults.

The embodiment can provide a closed loop test system: the system entry can be a test case library, and the test case database is generated to generate an alarm message, and the network management device senses and displays the processing result and the solution after receiving the alarm message. The export is the result of the comparison report and the history database, including the comparison file of the history version and the test version alarm details according to the policy, recording the test version of the alarm details in the library, and modifying or deleting the historical data in the historical version. The correctness of the alarm details can be considered as a test result. After multiple rounds of testing, the test case library can be updated based on the previous test results, such as adding test case alarms in areas where alarms occur frequently, and reducing corresponding test case alarms when the number of alarms shows a convergence trend. The above comparison file includes a comparison between the test version and the historical version of the alarm details. Preferably, a comparison report of the alarm details between the versions can also be output. Preferably, in the system test, the latest result is automatically recorded at the same time of testing, and by continuously adding, modifying, and deleting data operations, the data of the historical database can be enriched step by step, the test automation and the degree of intelligence are improved, and the goal of improving the test efficiency is finally realized. The above policies include but are not limited to time policies and version policies. Time policies include testing at specified times. Version policies include specific versions. The alarm details of the network management alarm are compared and analyzed.

FIG. 3 is a schematic structural diagram of a test apparatus according to an embodiment of the present invention, as shown in FIG. 3. The test packet is generated by the test case database, and the alarm message to be tested is sent to the network management module 32. The execution module 32 parses the packet and processes the alarm according to the internal logic to perceive and display the alarm details of the current version of the alarm packet, which is referred to as the current version of the alarm details. The analysis module 34 judges the execution result, extracts the alarm details, performs data normalization, and summarizes the data; performs data mining of different dimensions according to the strategy set in the test case library, and uses the analysis result to update the test case library, and tests the test case therein. The use case is modified; the analysis module 34 stores the summarized data in the historical database, and after each test, the historical data can be read according to the pre-strategy, the loop comparison is performed, and the comparison report can be output when needed. After the historical data reaches a certain scale, the fault occurrence frequency or convergence trend information in the alarm details recorded in the historical database is queried, and the test case library can be designed as a reference for targeted design; the data changes in the history database are also Can in turn prompt the update of the test case library.

The embodiment of the invention provides a test method applied to network management alarms. Design a test case library, define the planned network element type, version, network element management, protocol (IP) address, network segment and mask, network interface address and mask, interface end-to-end endpoint and Link attributes, Open Shortest Path First (OSPF) / Link State Routing Protocol (ISIS) / Border Gateway Protocol (BGP) routing protocol type and advertising network segment, Layer 2 and Layer 3 Virtual Private Network (VPN) \ Tunnel Service Type and Protection information, connectivity fault management (CFM), Bidirectional Forwarding Detection (BFD), Virtual Router Redundancy Protocol (VRRP), operation management and maintenance (Operation, Administration, Maintenance, OAM) Key configurations such as detection type. Pre-customized strategies generate comparison files and comparison reports for specific alerts.

Start the execution of the alarm test plan. The test case in the test case library is called to generate an alarm and send it to the network management alarm processing module. For the alarms reported, test the alarm details and statistics displayed after the NMS processes. For each alarm detail, you can display the alarm number, NE location, time, level, alarm code, location, type, and status of the NE. All attributes are correct and conform to the specifications. Can be filtered according to different conditions, such as current alarms and historical alarms, alarms and notifications, acknowledged and unacknowledged alarms, etc.

According to the test case, determine whether it is necessary to record the alarm details. In the case where the test version is a temporary version, the alarm details may not be recorded. If the judgment result is yes, the alarm details need to be recorded, and after the alarm details are recorded, it is determined whether the alarm details are correct. Connect the historical database with the alarm ID and version number as the key values. Insert a data in the alarm table, version table, and alarm details table to record the alarm details and execution time of the alarm. The historical data is stored in the historical database. . By recording the alarm details of each alarm in each version, the test data details of each function point in the test process are established to prepare for the next version of the test comparison. If the judgment result is negative, it is not necessary to record the alarm details, and it is directly determined whether the alarm details are correct.

If the alarm processing result is incorrect, if the alarm processing is incorrect, no further comparison is made to determine whether there is a next alarm to be tested. If the alarm processing is correct, enter the history database and query the previous version with the version number and alarm ID as the key value. The data is compared with the location, time, level, alarm code, location, type, and status of the NE in the alarm details table. After the comparison is completed, a comparison file is generated according to the strategy in the test case library.

Determine whether there is a previous historical version. If it exists, enter the historical database again, find the data of the historical version for comparison, and generate a comparison file. If it does not exist, the comparison between the test version and all historical versions has been completed. The comparison of the alarm during the test has been completed.

Determine whether there is a next alarm to be tested. If it exists, the test case is invoked again. After the alarm is generated, the test process is executed. If it does not exist, it indicates that all the alarms have been tested and the process of processing the comparison file is entered.

4 is a flow chart of a test method according to an embodiment of the present invention. As shown in FIG. 4, the method includes the following steps:

Step 402: Design a test scenario, including planning parameters, including an interface address, a routing protocol, a service type, and a protection path.

Address planning

Open Shortest Path First (OSPF) planning:

Label Distribution Protocol (LDP) Planning:

In step 404, a test plan and an alarm test case are written and input into the test case library. According to the test plan, the test case library is called to start testing the alarm. The test version number is version 1, there is history version 2, and history version 3. The comparison strategy is for all comparisons.

Step 406: The alarm message generated by the test case database is invoked, and the alarm message is sent to the network management system. The test is performed by taking the down alarm of the test port as an example.

Step 408: After receiving the alarm message, the network management system performs the gateway alarm processing; the details of the alarm may be displayed in the current alarm; the alarm details may include: an alarm number, an alarm level, a network element location, an alarm occurrence time, an alarm code, Details such as location, alarm type, and acknowledgement status in the NE. The alarm number is 1411008035312, the severity is severity, and the value is red. The type is the communication alarm. The time is the time when the alarm simulation tool is generated. The alarm code is DOWN (2151), the confirmation status is unconfirmed, and the NE IP address is 10.46. 60.93, the network element type is a certain type of router, the positioning frame in the network element is =0, the chassis is =0, the alarm is caused by the unsuccessful negotiation of the port link (50901), and the additional text alarm type: LACP; The interface (index=20) , name=Gei_0/0/0/10) turns into INACTIVE; generated by alarm synchronization; wherein the meaning of the included fields are: Link Aggregation Control Protocol (LACP), port running protocol interface (index= 20, name=Gei_0/0/0/10), port (index 20, interface name Gei_0/0/0/10), port offline: turns into INACTIVE.

Step 410: Determine whether it is necessary to record the alarm details. If the record needs to be recorded, perform the step. Step 412, in the case where recording is not required, jump to step 414;

Step 412: Record alarm details; may include storing the result in a database, inserting a piece of data in an alarm table, a version table, and an alarm detail table in the history database: inserting an alarm ID, a current execution result, and an execution time in the alarm table Insert the alarm ID, the version number, the version execution result, and the execution time in the version table. Insert the alarm ID, version number, version name, root alarm ID, alarm name, alarm level, time of occurrence, and network element in the alarm details table. Internal positioning, alarm code, associated service, alarm type, alarm identifier, processing suggestion, system type, attribute, and alarm cause;

In step 414, it is determined whether the processing result of the alarm module is correct. If the processing is wrong, go to step 420. If the processing is correct, step S416 is performed;

It should be noted that determining whether the processing result is correct is a conventional technical means of those skilled in the art, and details are not described herein.

Step 416 compares with the alarm details in the historical version to generate a comparison file. Open the history database and search for the historical version set with the associated relationship according to version 1 in the test case to obtain the alarm details of the previous history version. Compare the test version with the details of the previous historical version and generate a comparison file based on the policy. For example, the query gets version 2 and version 3. After sorting according to the time, select the historical version closest to version 1, that is, version 2, and query the alarm detail record of the alarm in version 2, and compare it with the alarm details in version 1. The comparison content may include the alarm name, the alarm level, the occurrence time, the intra-network element location, the alarm code, the associated service, the alarm type, the alarm identifier, the processing suggestion, the system type, the attribute, the alarm cause, etc., and the record version 1 is generated after the comparison is completed. Version 2 compares the results of the file.

In step 418, it is determined whether there is an older historical version. If yes, the process returns to step 416 to compare the test version with the older historical version. If not, step 420 is performed. For example, there is also a version 3 that needs to be compared. Connect the history database again and repeat the comparison process in step 416.

Step 420, it is determined whether there is a next alarm message, if there is a next alarm message, the process returns to step 406, if there is no next alarm message, step 422 is performed;

Step 422: Processing the comparison file, after testing all the alarms, acquiring two comparison files, and extracting information such as alarm details, test time, and test personnel in the file. Query the failed device, The board and the port perform data drilling, query the alarm-related service, and perform data drilling. Query the number of alarms under specific conditions according to the alarm code and alarm level to perform data mining. The alarm details and the comparison results of all the comparison files corresponding to the same alarm are stored in the historical database, the data is stored, a comparison report is generated, and the fault change is counted;

In step 424, it is determined whether the historical alarm details need to be updated. If the modification is required, step 426 is performed; if the modification is not required, the test is ended;

In step 426, the historical alarm details are modified or deleted, and the test is ended after the update is completed.

FIG. 5 is a flowchart of a comparison file processing according to an embodiment of the present invention. As shown in FIG. 5, the method includes the following steps:

Step 502: Read all the comparison files, and perform data extraction on the alarm details, the test time, the test personnel, and the like;

Step 504: Perform data reorganization according to the condition of time and version number, and delete unnecessary or erroneous data;

Step 506: According to the corresponding policy, perform statistics on the number of faults, fault levels, fault modules, and the like found in the test, and perform data aggregation; for example, count the total number of faults found within one week or one month;

Step 508, performing data analysis including data drilling based on the aggregated data. Based on the network management alarm information, it is associated with the device, board, port, etc., and is associated with the alarm details and related services. Therefore, data drilling and data drilling can be performed according to the pre-strategy to query different types of faults. After discovering certain rules, such as fault high-issue function and fault convergence tendency, the test case library can be updated.

Step 510: Perform data analysis including data mining based on the aggregated data. Network management alarms Because of the number of associated modules and devices, data mining is required for test results through a combination of different dimensions. For example, query the fault convergence trend of a specific number of versions. It is recommended to update the test case library after getting the data.

Step 512, performing data analysis including data storage according to the summarized data. According to the pre-strategy, the alarm details, data drilling results and data mining results after the rounding and summarization are stored in the historical database to form a historical database with detailed analysis data.

In step 514, a comparison report is generated. After comprehensively processing all the comparison files obtained before, the summary report of the summary is output. The content is a comparison of the failures between historical versions during the test, including the comparison between specific versions and specific test phases according to the pre-strategy.

Step 508 and step 510 may further include step 516:

Step 516, update the test case library

According to actual needs, if you need to modify the historical data in the historical database, connect to the database and update the data in the alarm table, version table, and alarm details table. Then end the process

If you do not need to modify, end the process. complete test.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and scope of the invention are intended to be included within the scope of the invention.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, being executed by a processor and stored in a memory. Programs/instructions to implement their respective functions. The invention is not limited to any particular form of hardware and software Combination of.

The embodiments disclosed in the present application are as described above, but the descriptions are only for the purpose of understanding the present application, and are not intended to limit the present application, such as the specific implementation method in the embodiments of the present invention. Any modifications and changes in the form and details of the embodiments may be made by those skilled in the art without departing from the spirit and scope of the disclosure. The scope defined by the appended claims shall prevail.

Industrial applicability

The foregoing technical solution improves the testing efficiency of the network management alarm.

Claims

A test method is applied to network management alarms, including:

Receiving an alarm message generated by the test case library;

The alarm test is performed by comparing the alarm details in the current version and the historical version of the received alarm message.
The testing method according to claim 1, before the warning test, the testing method further comprises:

Obtaining alarm details in the current version and the historical version of the alarm packet;

The alarm details include: an alarm number, an alarm level, a network element location, an alarm occurrence time, an alarm code, an intra-network element location, an alarm type, and an acknowledgement status;

And storing the obtained alarm details in the current version of the alarm message in a database.
The test method according to claim 2, wherein the storing the alarm details in the current version of the alarm message in the database comprises:

In the case that the current version is the official version, the alarm details of the alarm message are stored in the database.
The testing method according to claim 2, wherein the performing the warning test comprises:

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message to generate a comparison file; performing an alarm test according to the generated comparison file.
The test method of claim 4, wherein comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message comprises:

Determining whether the alarm details in the current version of the alarm message are correct;

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message when the alarm details in the current version of the alarm message are correct. .
The testing method according to claim 4 or 5, after the comparing the alarm details in the current version with the alarm details in the historical version of the alarm message, the testing method Also includes:

If the alarm details in the historical version of the alarm message are in error, modify or delete the alarm details of the error.
The method according to claim 4 or 5, after comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message, the testing method further includes:

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message to be compared, where the alarm details of the historical version are to be compared;

If there is no alarm detail to be compared with the historical version, it is determined whether there is an alarm message to be tested in the test case database, and the test is received if there is an alarm message to be tested in the test case database. The alarm message to be tested generated by the use case library.
The testing method according to claim 7, further comprising:

When it is determined that there is no alarm message to be tested in the test case database, the data of the comparison file is analyzed, and an alarm analysis report is output.
The testing method according to claim 8, wherein said method of analyzing data of said comparison file comprises at least one of the following:

Data drilling, data mining, data storage.
A test device is applied to a network management alarm, including:

a receiving module, configured to receive an alarm message generated by the test case library;

The test module is configured to perform an alarm test by comparing the current version of the received alarm message with the alarm details in the historical version.
The testing device of claim 10, further comprising:

Obtaining a module, configured to obtain the alarm details in the current version and the historical version of the alarm message;

The alarm details include: an alarm number, an alarm level, a network element location, an alarm occurrence time, an alarm code, an intra-network element location, an alarm type, and an acknowledgement status;

The storage module is configured to store the obtained alarm details in the current version of the obtained alarm message in a database.
The testing device of claim 11 wherein said test module is configured to:

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message to generate a comparison file;

Perform an alarm test based on the generated comparison file.
The testing device of claim 12 wherein said test module is configured to:

Determining whether the alarm details in the current version of the alarm message are correct;

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message when the alarm details in the current version of the alarm message are correct. , generating a comparison file;

Perform an alarm test based on the generated comparison file.
The testing device according to claim 12 or 13, the testing device further comprising an alarm processing module configured to compare the alarm details in the current version with the alarm details in the historical version of the alarm message Then, in the case that the alarm details in the historical version of the alarm message are in error, the error alarm details are modified or deleted.
The testing device according to claim 12 or 13, wherein the testing device further comprises a comparison processing module, configured to: in the historical version of the alarm message, the alarm details in the current version of the alarm message After comparing the alarm details,

Comparing the alarm details in the current version of the alarm message with the alarm details in the historical version of the alarm message to be compared, where the alarm details of the historical version are to be compared;

If there is no alarm detail to be compared with the historical version, it is determined whether there is an alarm message to be tested in the test case database, and the test is received if there is an alarm message to be tested in the test case database. The alarm message to be tested generated by the use case library.
The testing device according to claim 15, wherein the comparison processing module is further configured to:

When it is determined that there is no alarm message to be tested in the test case database, the data of the comparison file is analyzed, and an alarm analysis report is output.