CN111309579A - Test method and related device for system event log quantity acquisition function - Google Patents
Test method and related device for system event log quantity acquisition function Download PDFInfo
- Publication number
- CN111309579A CN111309579A CN202010108487.0A CN202010108487A CN111309579A CN 111309579 A CN111309579 A CN 111309579A CN 202010108487 A CN202010108487 A CN 202010108487A CN 111309579 A CN111309579 A CN 111309579A
- Authority
- CN
- China
- Prior art keywords
- system event
- event log
- command
- list
- log
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000010998 test method Methods 0.000 title claims description 7
- 238000012360 testing method Methods 0.000 claims abstract description 146
- 238000000034 method Methods 0.000 claims abstract description 25
- 230000002159 abnormal effect Effects 0.000 claims abstract description 19
- 230000006870 function Effects 0.000 claims description 64
- 238000004590 computer program Methods 0.000 claims description 10
- 108010028984 3-isopropylmalate dehydratase Proteins 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 241000282326 Felis catus Species 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
Abstract
The application discloses a method and a related device for testing a system event log quantity acquisition function, which comprise the following steps: sending a selinfo command and a selelist command to a target test machine through ipmitool, receiving summary information of a system event log returned by the target test machine after the selinfo command is executed, and obtaining the number of the system event log based on the summary information of the system event log; receiving system event log list information returned by a target tester executing a selelist command, and obtaining the line number of the system event log list based on the system event log list information; judging whether the number of the system event logs is equal to the number of lines of the system event log list or not; if not, determining that the system event log quantity acquisition function is abnormal; otherwise, it is normal. The testing method not only can greatly save the manpower input of testing personnel, but also can effectively improve the testing accuracy.
Description
Technical Field
The application relates to the technical field of servers, in particular to a method for testing a system event log quantity acquisition function; also relates to a testing device, equipment and a computer readable storage medium for the system event log quantity acquisition function.
Background
In order to maintain the running state of the server resources, the system event log of the server records the date and time stamp information of the system related to daily events or misoperation alarms. Usage records and abnormal alarms generated in the running process of the equipment are recorded in the system event log. Therefore, the system event log is very important for the server maintenance personnel, and the function of acquiring the information and the quantity of the system event log through the IPMI command is particularly important. Therefore, how to accurately and efficiently test the acquisition function of the number of the system event logs becomes a technical problem to be solved by those skilled in the art.
Disclosure of Invention
The purpose of the application is to provide a method for testing the system event log quantity acquisition function, which can accurately and efficiently test the system event log quantity acquisition function. Another object of the present application is to provide a testing apparatus, a device and a computer-readable storage medium for a system event log quantity obtaining function, all of which have the above technical effects.
In order to solve the above technical problem, the present application provides a method for testing a system event log quantity obtaining function, including:
sending a selinfo command to a target test machine through ipmitool, receiving summary information of a system event log returned by the target test machine after the selinfo command is executed, and obtaining the number of the system event log based on the summary information of the system event log;
sending a selelist command to the target test machine through the ipmitool, receiving system event log list information returned by the selelist command executed by the target test machine, and obtaining the line number of the system event log list based on the system event log list information;
judging whether the number of the system event logs is equal to the number of lines of the system event log list or not;
if the number of the system event logs is not equal to the number of rows of the system event log list, determining that the system event log number acquisition function is abnormal;
and if the number of the system event logs is equal to the number of the lines of the system event log list, determining that the system event log number acquisition function test is normal.
Optionally, the receiving system event log list information returned by the target test machine executing the selelist command, and obtaining the number of lines in the system event log list based on the system event log list information includes:
receiving list information of the system event log returned by the target tester after the target tester executes the selelist command, and outputting the list information to a test log;
and executing a test log query command to acquire the line number of the system event log list from the test log.
Optionally, the obtaining the number of the system event logs based on the summary information of the system event logs includes:
and obtaining the number of the system event logs based on the Entries field in the summary information of the system event logs.
Optionally, if the number of the system event logs is not equal to the number of rows in the system event log list, determining that the system event log number acquisition function is abnormal includes:
and if the number of times that the number of the system event logs is not equal to the number of lines of the system event log list reaches a preset value, determining that the system event log number acquisition function is abnormal.
Optionally, the method further includes:
and displaying the test result.
In order to solve the above technical problem, the present application further provides a testing apparatus for system event log quantity obtaining function, including:
the log quantity query module is used for sending a selinfo command to a target test machine through the ipmitool, receiving summary information of the system event logs returned by the target test machine after the selinfo command is executed, and obtaining the quantity of the system event logs based on the summary information of the system event logs;
the list line number query module is used for sending a selelist command to the target test machine through the ipmitool, receiving system event log list information returned by the target test machine after the selelist command is executed by the target test machine, and obtaining the line number of the system event log list based on the system event log list information;
the judging module is used for judging whether the number of the system event logs is equal to the number of lines of the system event log list or not;
the determining module is used for determining that the system event log quantity acquisition function is abnormal if the quantity of the system event logs is not equal to the line number of the system event log list; and if the number of the system event logs is equal to the number of the lines of the system event log list, determining that the system event log number acquisition function is normal.
Optionally, the list line number query module includes:
the list information output unit is used for receiving the list information of the system event log returned by the target testing machine after the selelist command is executed, and outputting the list information to a test log;
and the test log query unit is used for executing a test log query command to acquire the line number of the system event log list from the test log.
Optionally, the log quantity query module is specifically configured to obtain the quantity of the system event logs based on an Entries field in summary information of the system event logs.
In order to solve the above technical problem, the present application further provides a testing apparatus with a system event log quantity obtaining function, including:
a memory for storing a computer program;
and the processor is used for realizing the steps of the test method of the system event log quantity acquisition function when the computer program is executed.
In order to solve the above technical problem, the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the steps of the method for testing the system event log quantity obtaining function are implemented as described above.
The method for testing the system event log quantity acquisition function comprises the following steps: sending a selinfo command to a target test machine through ipmitool, receiving summary information of a system event log returned by the target test machine after the selinfo command is executed, and obtaining the number of the system event log based on the summary information of the system event log; sending a selelist command to the target test machine through the ipmitool, receiving system event log list information returned by the selelist command executed by the target test machine, and obtaining the line number of the system event log list based on the system event log list information; judging whether the number of the system event logs is equal to the number of lines of the system event log list or not; if the number of the system event logs is not equal to the number of rows of the system event log list, determining that the system event log number acquisition function is abnormal; and if the number of the system event logs is equal to the number of the lines of the system event log list, determining that the system event log number acquisition function test is normal.
Therefore, according to the method for testing the system event log quantity obtaining function, the selinfo command and the selelist command are sent to the target test machine through the ipmitool, the selinfo command and the selelist command are executed based on the target test machine, the summary information of the system event log returned by the selinfo command and the selelist command and the system event log list information are obtained, the system event log quantity and the line number of the system event log list are obtained, and the test result is obtained by judging whether the system event log quantity is equal to the line number of the system event log list or not. The test method realizes the automatic test of the system event log quantity acquisition function, not only can greatly save the manpower input of testers, but also can effectively improve the test accuracy.
The test device, the equipment and the computer readable storage medium with the system event log quantity acquiring function have the technical effects.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the prior art and the embodiments are briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for testing a system event log quantity obtaining function according to an embodiment of the present application;
fig. 2 is a schematic diagram of a testing apparatus for a system event log quantity obtaining function according to an embodiment of the present disclosure;
fig. 3 is a schematic diagram of a testing device with a system event log quantity obtaining function according to an embodiment of the present application.
Detailed Description
The core of the application is to provide a method for testing the function of acquiring the number of the system event logs, which can accurately and efficiently test the function of acquiring the number of the system event logs. At the other core of the present application, a testing apparatus, a device and a computer-readable storage medium for a system event log quantity obtaining function are provided, which all have the above technical effects.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a schematic flow chart of a testing method for a system event log quantity obtaining function according to an embodiment of the present application, and referring to fig. 1, the testing method mainly includes the following steps:
s101: sending a selinfo command to a target test machine through ipmitool, receiving summary information of a system event log returned by the target test machine after the selinfo command is executed, and obtaining the number of the system event log based on the summary information of the system event log;
specifically, the present step aims to obtain the number of current system event logs by querying the summary information of the system event logs, i.e. the SEL. Specifically, the execution machine sends a selinfo command to the target tester using ipmitool. The target test machine executes the selinfo command to obtain the summary information of the system event log and returns the obtained summary information of the system event log to the execution machine. Further, the execution machine obtains the number of the system event logs based on the summary information of the system event logs returned by the target test machine.
Wherein, sending the selinfo command to the target tester through the ipmitool may be as follows:
ipmitool–I lanplus–H<ip>–U<username>–P<password>selinfo
in addition, in a specific embodiment, the obtaining the number of the system event logs based on the summary information of the system event logs may include: and obtaining the number of the system event logs based on the Entries field in the summary information of the system event logs. That is, in this embodiment, the Entries field in the summary information of the system event logs is used to indicate the number of the system event logs, and the number of the system event logs is obtained by querying the Entries field.
For example, send a selinfo command to the target tester over ipmitool:
ipmitool-I lanplus-H 100.3.8.5-U admin-P admin selinfo
the target test machine executes the command and returns the following information:
Version：1.5(v1.5，v2 compliant)
Entries：7
Free Space：65376bytes
Percent Used：0％
LastAdd Time：03/30/201923:55:41
Last Del Time：NotAvailable
Overflow：false
Supported Cmds：'Delete”Partial Add”Reserve”Get Alloc Info'
#ofAlloc Units：3639
Alloc Unit Size：18
#Free Units：3632
Largest Free Blk：3632
Max Record Size：1
the summary information returned by the target test machine comprises an Entries field, Free Space and the like, wherein the Entries field is mainly concerned, and the value of the entry field is 7, which indicates that the current number of the system event logs is 7.
S102: sending a selelist command to a target test machine through ipmitool, receiving system event log list information returned by the target test machine after the selelist command is executed, and obtaining the number of lines of a system event log list based on the system event log list information;
specifically, the step aims to query the system event log list information to obtain the number of rows of the system event log list, and then verify the accuracy of the function of obtaining the number of the system event logs through the IPMI command according to the number of rows of the system event log list. Specifically, the execution machine sends a selelist command to the target test machine through ipmitool. The target test machine executes the selelist command to obtain system event log list information and returns the obtained system event log list information to the execution machine. Further, the execution machine obtains the line number of the system event log list based on the system event log list information returned by the target test machine.
Wherein, sending selelist command to the target tester through ipmitool may be as follows:
ipmitool–I lanplus–H<ip>–U<username>–P<password>selelist
in addition, in a specific embodiment, the receiving system event log list information returned by the target test machine executing the selelist command, and obtaining the number of rows of the system event log list based on the system event log list information may include: receiving list information of a system event log returned by a target test machine executing a selelist command, and outputting the list information to a test log; and executing the test log query command to acquire the line number of the system event log list from the test log. That is, in this embodiment, after receiving list information of the system event log returned by the target test machine, the execution machine first outputs the list information to the test log, and then executes the test log query command to obtain the line number of the system event log list from the test log.
For example: sending a selelist command to the target tester through ipmitool:
ipmitool-I lanplus-H 100.3.8.5-U admin-P admin selelist
the target tester executes the command and returns the following information:
1|Pre-Init|0000028813|Microcontroller/Coprocessor BMC_Boot_up|DeviceEnabled|Asserted
2|03/30/2019|23:53:38|System ACPI Power State ACPI_State|Legacy ONstate|Asserted
3|03/30/2019|23:54:03|PowerSupply PSU0_Status|Power Supply AC lost|Asserted
4|03/30/2019|23:54:03|Drive Slot DISK4_Status|Drive Present|Asserted
5|03/30/2019|23:54:03|Drive Slot DISK6_Status|Drive Present|Asserted
6|03/30/2019|23:54:03|Drive Slot DISK7_Status|Drive Present|Asserted
7|03/30/2019|23:55:41|OS Boot OS_Boot|boot completed-device notspecified|Asserted
log, i.e., a test log, outputs the above information. Furthermore, a test log query command, such as cat test.
S103: judging whether the number of the system event logs is equal to the number of lines of the system event log list or not;
s104: if the number of the system event logs is not equal to the number of rows of the system event log list, determining that the system event log number acquisition function is abnormal;
s105: and if the number of the system event logs is equal to the number of lines of the system event log list, determining that the system event log number acquisition function is normal.
Specifically, after the number of the system event logs and the number of rows of the system event log list are obtained, the number of the system event logs and the number of rows of the system event log list are further compared, whether the number of the system event logs is equal to the number of rows of the system event log list or not is judged, if the number of the system event logs is equal to the number of rows of the system event log list, the number of the obtained system event logs is accurate, the function of obtaining the number of the system event logs through the IPMI instruction is normal, and the test is passed. On the contrary, if the two are not equal, the number of the obtained system event logs is not accurate, the function of obtaining the number of the system event logs through the IPMI instruction is abnormal, and the test is not passed.
To further ensure the accuracy and reliability of the test, as a preferred implementation manner on the basis of the above embodiment, if the number of the system event logs is not equal to the number of rows in the system event log list, determining that the number of the system event logs obtains a functional test abnormality includes: and if the number of times that the number of the system event logs is not equal to the number of lines of the system event log list reaches a preset value, determining that the function test of obtaining the number of the system event logs is abnormal.
Specifically, the steps S101 and S102 may be repeatedly executed for multiple times, the number of the system event logs obtained each time is compared with the number of rows in the system event log list, and if the number of times that the number of the system event logs is not equal to the number of rows in the system event log list reaches a preset value, it is determined that the system event log number obtaining function is abnormal.
The specific numerical value of the preset value is not limited uniquely, and the difference setting can be performed according to the actual application requirement.
In addition, it is understood that, regarding the execution sequence of steps S101 and S102, the present application is not limited thereto, and step S101 may be executed first, or step S102 may be executed first.
In addition, on the basis of obtaining the test result, the test result of the system event log quantity obtaining function can be further displayed, so that related personnel can know the situation in time.
In summary, in the test method for the system event log quantity obtaining function provided by the present application, the ipmitool is used to send the selinfo command and the selelist command to the target test machine, and further, the summary information of the system event log and the system event log list information returned after the selinfo command and the selelist command are executed by the target test machine are used to obtain the system event log quantity and the line number of the system event log list, and a test result is obtained by judging whether the system event log quantity is equal to the line number of the system event log list. The test method realizes the automatic test of the system event log quantity acquisition function, not only can greatly save the manpower input of testers, but also can effectively improve the test accuracy.
The application also provides a testing device with a system event log quantity obtaining function, and the testing device described below can be referred to with the testing method described above correspondingly. Referring to fig. 2, fig. 2 is a schematic diagram of a testing apparatus for a system event log quantity obtaining function according to an embodiment of the present application, and with reference to fig. 2, the testing apparatus includes:
the log quantity query module 10 is configured to send a selinfo command to a target test machine through ipmitool, receive summary information of a system event log returned by the target test machine after the selinfo command is executed, and obtain the quantity of the system event log based on the summary information of the system event log;
the list line number query module 20 is configured to send a selelist command to the target test machine through the ipmitool, receive system event log list information returned by the target test machine after the selelist command is executed by the target test machine, and obtain the line number of the system event log list based on the system event log list information;
a judging module 30, configured to judge whether the number of the system event logs is equal to the number of rows in the system event log list;
a determining module 40, configured to determine that the number of the system event logs is abnormal in acquiring function if the number of the system event logs is not equal to the number of rows in the system event log list; and if the number of the system event logs is equal to the number of the lines of the system event log list, determining that the system event log number acquisition function is normal.
On the basis of the above embodiment, optionally, the list line number query module 20 includes:
the list information output unit is used for receiving the list information of the system event log returned by the target testing machine after the selelist command is executed, and outputting the list information to a test log;
and the test log query unit is used for executing a test log query command to acquire the line number of the system event log list from the test log.
On the basis of the above embodiment, optionally, the log quantity query module 10 is configured to obtain the quantity of the system event logs based on an Entries field in the summary information of the system event logs.
On the basis of the foregoing embodiment, optionally, the determining module is specifically configured to determine that the system event log number obtaining function is abnormal if the number of times that the number of the system event logs is not equal to the number of lines in the system event log list reaches a preset value.
On the basis of the above embodiment, optionally, the method further includes:
and the display module is used for displaying the test result.
The present application also provides a testing device with system event log quantity obtaining function, which is shown in fig. 3 and includes a memory 1 and a processor 2. Wherein, the memory 1 is used for storing computer programs; a processor 2 for executing a computer program to implement the steps of:
sending a selinfo command to a target test machine through ipmitool, receiving summary information of a system event log returned by the target test machine after the selinfo command is executed, and obtaining the number of the system event log based on the summary information of the system event log; sending a selelist command to the target test machine through the ipmitool, receiving system event log list information returned by the selelist command executed by the target test machine, and obtaining the line number of the system event log list based on the system event log list information; judging whether the number of the system event logs is equal to the number of lines of the system event log list or not; if the number of the system event logs is not equal to the number of rows of the system event log list, determining that the system event log number acquisition function is abnormal; and if the number of the system event logs is equal to the number of the lines of the system event log list, determining that the system event log number acquisition function test is normal.
For the introduction of the test equipment provided in the present application, please refer to the above method embodiments, which are not described herein again.
The present application further provides a computer-readable storage medium having a computer program stored thereon, which when executed by a processor, performs the steps of:
sending a selinfo command to a target test machine through ipmitool, receiving summary information of a system event log returned by the target test machine after the selinfo command is executed, and obtaining the number of the system event log based on the summary information of the system event log; sending a selelist command to the target test machine through the ipmitool, receiving system event log list information returned by the selelist command executed by the target test machine, and obtaining the line number of the system event log list based on the system event log list information; judging whether the number of the system event logs is equal to the number of lines of the system event log list or not; if the number of the system event logs is not equal to the number of rows of the system event log list, determining that the system event log number acquisition function is abnormal; and if the number of the system event logs is equal to the number of the lines of the system event log list, determining that the system event log number acquisition function test is normal.
The computer-readable storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
For the introduction of the computer-readable storage medium provided in the present application, please refer to the above method embodiments, which are not described herein again.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device, the apparatus and the computer-readable storage medium disclosed by the embodiments correspond to the method disclosed by the embodiments, so that the description is simple, and the relevant points can be referred to the description of the method.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The method, the apparatus, the device and the computer readable storage medium for testing the system event log quantity obtaining function provided by the present application are described in detail above. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. A method for testing a system event log quantity acquisition function is characterized by comprising the following steps:
sending a selinfo command to a target test machine through ipmitool, receiving summary information of a system event log returned by the target test machine after the selinfo command is executed, and obtaining the number of the system event log based on the summary information of the system event log;
sending a selelist command to the target test machine through the ipmitool, receiving system event log list information returned by the selelist command executed by the target test machine, and obtaining the line number of the system event log list based on the system event log list information;
judging whether the number of the system event logs is equal to the number of lines of the system event log list or not;
if the number of the system event logs is not equal to the number of rows of the system event log list, determining that the system event log number acquisition function is abnormal;
and if the number of the system event logs is equal to the number of the lines of the system event log list, determining that the system event log number acquisition function test is normal.
2. The method according to claim 1, wherein the receiving system event log list information returned by the target tester executing the selelist command, and deriving a number of rows of a system event log list based on the system event log list information comprises:
receiving list information of the system event log returned by the target tester after the target tester executes the selelist command, and outputting the list information to a test log;
and executing a test log query command to acquire the line number of the system event log list from the test log.
3. The method according to claim 2, wherein the obtaining the number of system event logs based on the summary information of the system event logs comprises:
and obtaining the number of the system event logs based on the Entries field in the summary information of the system event logs.
4. The method according to claim 3, wherein if the number of the system event logs is not equal to the number of rows in the system event log list, determining that the system event log number acquisition function is abnormal comprises:
and if the number of times that the number of the system event logs is not equal to the number of lines of the system event log list reaches a preset value, determining that the system event log number acquisition function is abnormal.
5. The test method of claim 4, further comprising:
and displaying the test result.
6. A test device for system event log quantity acquisition function is characterized by comprising:
the log quantity query module is used for sending a selinfo command to a target test machine through the ipmitool, receiving summary information of the system event logs returned by the target test machine after the selinfo command is executed, and obtaining the quantity of the system event logs based on the summary information of the system event logs;
the list line number query module is used for sending a selelist command to the target test machine through the ipmitool, receiving system event log list information returned by the target test machine after the selelist command is executed by the target test machine, and obtaining the line number of the system event log list based on the system event log list information;
the judging module is used for judging whether the number of the system event logs is equal to the number of lines of the system event log list or not;
the determining module is used for determining that the system event log quantity acquisition function is abnormal if the quantity of the system event logs is not equal to the line number of the system event log list; and if the number of the system event logs is equal to the number of the lines of the system event log list, determining that the system event log number acquisition function is normal.
7. The testing apparatus of claim 6, wherein the list line number query module comprises:
the list information output unit is used for receiving the list information of the system event log returned by the target testing machine after the selelist command is executed, and outputting the list information to a test log;
and the test log query unit is used for executing a test log query command to acquire the line number of the system event log list from the test log.
8. The testing device of claim 7, wherein the log quantity query module is specifically configured to obtain the quantity of the system event logs based on an Entries field in summary information of the system event logs.
9. A test device for system event log quantity acquisition function, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the method for testing the system event log quantity acquisition function according to any one of claims 1 to 5 when executing said computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored thereon, which, when being executed by a processor, implements the steps of the method for testing the system event log quantity acquisition function according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010108487.0A CN111309579B (en) | 2020-02-21 | 2020-02-21 | Test method and related device for system event log quantity acquisition function |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010108487.0A CN111309579B (en) | 2020-02-21 | 2020-02-21 | Test method and related device for system event log quantity acquisition function |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111309579A true CN111309579A (en) | 2020-06-19 |
| CN111309579B CN111309579B (en) | 2022-06-10 |
Family
ID=71151247
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010108487.0A Active CN111309579B (en) | 2020-02-21 | 2020-02-21 | Test method and related device for system event log quantity acquisition function |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309579B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112463818A (en) * | 2020-11-24 | 2021-03-09 | 苏州浪潮智能科技有限公司 | Method, medium, equipment and system for inquiring information of storage bottom layer |
| CN113377719A (en) * | 2021-06-02 | 2021-09-10 | 北京鼎普科技股份有限公司 | Method and system for acquiring abnormal shutdown time of system |
| CN114238018A (en) * | 2021-12-17 | 2022-03-25 | 天翼爱音乐文化科技有限公司 | Method, system and device for detecting integrity of log collection file and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109684166A (en) * | 2018-12-03 | 2019-04-26 | 郑州云海信息技术有限公司 | Method, apparatus, terminal and the storage medium of automatic test Sensor log normalization |
| CN109726130A (en) * | 2019-01-02 | 2019-05-07 | 浪潮商用机器有限公司 | Test macro, method, equipment and the storage medium of BMC event log strategy |
| CN110188013A (en) * | 2019-05-30 | 2019-08-30 | 苏州浪潮智能科技有限公司 | A kind of log read-write capability test method, device and electronic equipment and storage medium |
-
2020
- 2020-02-21 CN CN202010108487.0A patent/CN111309579B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109684166A (en) * | 2018-12-03 | 2019-04-26 | 郑州云海信息技术有限公司 | Method, apparatus, terminal and the storage medium of automatic test Sensor log normalization |
| CN109726130A (en) * | 2019-01-02 | 2019-05-07 | 浪潮商用机器有限公司 | Test macro, method, equipment and the storage medium of BMC event log strategy |
| CN110188013A (en) * | 2019-05-30 | 2019-08-30 | 苏州浪潮智能科技有限公司 | A kind of log read-write capability test method, device and electronic equipment and storage medium |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112463818A (en) * | 2020-11-24 | 2021-03-09 | 苏州浪潮智能科技有限公司 | Method, medium, equipment and system for inquiring information of storage bottom layer |
| CN112463818B (en) * | 2020-11-24 | 2022-07-12 | 苏州浪潮智能科技有限公司 | Method, medium, equipment and system for inquiring information of storage bottom layer |
| CN113377719A (en) * | 2021-06-02 | 2021-09-10 | 北京鼎普科技股份有限公司 | Method and system for acquiring abnormal shutdown time of system |
| CN113377719B (en) * | 2021-06-02 | 2023-12-19 | 北京鼎普科技股份有限公司 | System abnormal shutdown time acquisition method and system |
| CN114238018A (en) * | 2021-12-17 | 2022-03-25 | 天翼爱音乐文化科技有限公司 | Method, system and device for detecting integrity of log collection file and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111309579B (en) | 2022-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111309579B (en) | Test method and related device for system event log quantity acquisition function | |
| CN110727556A (en) | BMC health state monitoring method, system, terminal and storage medium | |
| US9542304B1 (en) | Automated operating system installation | |
| CA3127343A1 (en) | Test data acquisition method and device, computer equipment and storage medium | |
| CN110580220B (en) | Method for measuring code segment execution time and terminal equipment | |
| CN113721144A (en) | Motor aging test method and device, storage medium and electronic equipment | |
| CN112817869A (en) | Test method, test device, test medium, and electronic apparatus | |
| CN112084108A (en) | Test script generation method and device and related components | |
| US20220345360A1 (en) | Fault Locating Method, Apparatus And System Based On I2C Communication | |
| CN110543394A (en) | server sensor information consistency testing method, system, terminal and storage medium | |
| CN111858198A (en) | Multi-scheme memory plugging test method, system, terminal and storage medium | |
| CN108845932B (en) | Unit testing method and device of network library, storage medium and terminal | |
| CN109039770B (en) | Server CMC refreshing method and device and related equipment | |
| CN111240990A (en) | ISMCLI command line testing method, system, terminal and storage medium | |
| CN111008150A (en) | Test report generation method, device and equipment | |
| CN112181744A (en) | Fault detection method, system, terminal and storage medium of converter interface | |
| CN114003442A (en) | Pressure testing method, device, equipment and medium for ARM server | |
| CN116820946B (en) | Method and device for automatically testing compatibility of target software | |
| CN117493127B (en) | Application program detection method, device, equipment and medium | |
| CN113868048B (en) | Method, device and equipment for determining equipment information | |
| CN112242858B (en) | Method and device for testing carrier communication module of electric energy meter | |
| CN112463500A (en) | Hard disk partition testing method, device, equipment and storage medium | |
| CN115687109A (en) | Interface test method and device, electronic equipment and storage medium | |
| CN117491784A (en) | Module aging test method, device, equipment and storage medium | |
| CN116755949A (en) | Method and device for positioning abnormal equipment in multi-equipment testing system and related products |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |