CN106294151A - Daily record method of testing and device - Google Patents

Abstract

The invention relates to a log test method and device. The log testing method includes: finding a folder for storing target log files in the log server; and generating the target log file according to the target log use case to be tested when the folder does not include other log files. the target log file; compare the content recorded in the target log file with the preset content of the target log use case, and determine whether the target log use case can run normally according to the comparison result. The log test method in the embodiment of the present invention can improve the test efficiency of log use cases.

Description

Log test method and device

technical field

The invention relates to the field of computers, in particular to a log test method and device.

Background technique

Network equipment, systems and service programs, etc., will generate a log event record during operation. Each line of log records the description of related operations such as date, time, user, and action. Therefore, each log use case may correspond to different execution logic.

At present, for the test of the log use case, the method of manual test is usually adopted. The log use case is triggered by the worker to generate the log, and after the log is generated, the worker goes to the server to check whether the content of the generated log record is correct. However, manual test log use cases are time-consuming, cannot guarantee the coverage of the test, and the regression test time is relatively long.

Contents of the invention

technical problem

In view of this, the technical problem to be solved by the present invention is how to improve the test efficiency of log use cases.

solution

In order to solve the above technical problems, according to an embodiment of the present invention, a log test method is provided, including:

Find the folder used to store the target log file in the log server;

When the folder does not include other log files, generate the target log file according to the target log use case to be tested;

Comparing the content recorded in the target log file with the preset content of the target log use case, and determining whether the target log use case can run normally according to the comparison result.

For the above method, in a possible implementation manner, it also includes:

When the folder includes other log files, all log files included in the folder are deleted.

For the above method, in a possible implementation, the target log file is generated according to the target log use case to be tested, including:

Trigger the request link corresponding to the target log use case to generate the target log file.

For the above method, in a possible implementation, compare the content recorded in the target log file with the preset content of the target log use case, and determine whether the target log use case can run normally according to the comparison result ,include:

Open the target log file, and extract the content recorded in the target log file;

Comparing the content with the preset content, if the content is the same as the preset content, the target log use case can run normally; or, comparing the content with the preset content In comparison, if the content is different from the preset content, the target log use case cannot run normally.

For the above method, in a possible implementation manner, it also includes:

In the case that the code of the system to be tested is found to be updated, at least one target log use case to be tested is obtained from the log use cases included in the system.

In order to solve the above technical problems, according to another embodiment of the present invention, a log test device is provided, including:

A search module, configured to find a folder for storing target log files in the log server;

A generation module, connected to the search module, used to generate the target log file according to the target log use case to be tested when the folder does not include other log files;

A comparison module, connected to the generation module, is used to compare the content recorded in the target log file with the preset content of the target log use case, and determine whether the target log use case can run normally according to the comparison result.

For the above device, in a possible implementation manner, it also includes:

A deletion module, configured to delete all log files included in the folder when the folder includes other log files.

For the above device, in a possible implementation, it is specifically used for

Trigger the request link corresponding to the target log use case to generate the target log file.

For the above device, in a possible implementation, it is specifically used for

Open the target log file, and extract the content recorded in the target log file;

Comparing the content with the preset content, if the content is the same as the preset content, the target log use case can run normally; or, comparing the content with the preset content In comparison, if the content is different from the preset content, the target log use case cannot run normally.

For the above device, in a possible implementation manner, it also includes:

The calling module is used to obtain at least one target log use case to be tested from the log use cases included in the system when the code of the system to be tested is found to be updated.

Beneficial effect

The log test method of the embodiment of the present invention generates a target log file according to the target log use case to be tested, and compares the content recorded in the target log file with the preset content of the target log use case to determine whether the target log use case is normal Running can improve the test efficiency of log use cases.

Furthermore, the log test method of the embodiment of the present invention can be applied to test various types of log use cases, can simulate a large number of log scenarios, increase test coverage, and ensure the quality of log use cases.

Furthermore, when the code of the system is updated, each log use case included in the system can be tested, which can greatly improve the test efficiency, shorten the regression test time, and eliminate the impact of code update on the log use case.

Other features and aspects of the present invention will become apparent from the following detailed description of exemplary embodiments with reference to the accompanying drawings.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the invention and together with the description, serve to explain the principles of the invention.

Fig. 1 shows the flowchart of the log test method according to an embodiment of the present invention;

Fig. 2 shows another flowchart of the log test method according to an embodiment of the present invention;

Fig. 3 shows another flowchart of the log testing method according to an embodiment of the present invention;

Fig. 4 shows another flow chart of the log test method according to an embodiment of the present invention;

Fig. 5 shows another flow chart of the log test method according to an embodiment of the present invention;

Fig. 6 shows another flow chart of the log test method according to an embodiment of the present invention;

Fig. 7 shows a structural block diagram of a log test device according to another embodiment of the present invention;

FIG. 8 shows another structural block diagram of a log test device according to another embodiment of the present invention;

Fig. 9 shows another structural block diagram of a log test device according to another embodiment of the present invention;

Fig. 10 shows a structural block diagram of a log test device according to another embodiment of the present invention.

detailed description

Various exemplary embodiments, features, and aspects of the invention will be described in detail below with reference to the accompanying drawings. The same reference numbers in the figures indicate functionally identical or similar elements. While various aspects of the embodiments are shown in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as superior or better than other embodiments.

In addition, in order to better illustrate the present invention, numerous specific details are given in the specific embodiments below. It will be understood by those skilled in the art that the present invention may be practiced without certain of the specific details. In some instances, methods, means, components and circuits well known to those skilled in the art have not been described in detail in order to highlight the gist of the present invention.

Example 1

Fig. 1 shows a flowchart of a log test method according to an embodiment of the present invention. As shown in Figure 1, the log test method mainly includes:

Step 101, find the folder for storing the target log file in the log server;

Step 102, in the case that the folder does not include other log files, generate the target log file according to the target log use case to be tested;

Step 103: Compare the content recorded in the target log file with the preset content of the target log use case, and determine whether the target log use case can run normally according to the comparison result.

Specifically, network devices, systems, and service programs, etc., will generate log files during operation, such as system logs, security logs, etc., and this embodiment does not limit the specific types of log files. Each log file can record the description of related operations such as date, time, user and action, and these contents play an important role in the operation and maintenance of the system. Specifically, for example, system logs can record information about hardware, software, and system problems in the system, and can also monitor events that occur in the system. The security log can record information every time the machine is turned on and off, the program is run, and the system reports an error.

Taking the Windows operating system as an example, it is designed with various types of logs, for example, it can include application logs, security logs, system logs, Scheduler service logs, FTP (File Transfer Protocol, file transfer protocol) logs, WWW (World Wide Web, World Wide Web) logs, DNS (Domain Name System, Domain Name System) server logs, etc. When the user performs some operations on the system, these log files usually record the relevant content of the operation. For example, if a user performs an IPC (Inter-Process Communication) probe on the system, the system will quickly record the IP address, time, user name, etc. used by the prober in the security log.

The log server in this embodiment of the present invention may include various types of servers capable of storing log files, which is not limited here. Further, the embodiment of the present invention does not limit the number of servers, which may be a single server or a cluster server. Wherein, the types of log files can be classified according to user behavior or system operation. For example, in the process of video broadcasting, when the video ad is first played, the start monitoring log will be recorded, the user clicks on the ad, there will be an ad click log, and the end monitoring log will be recorded after the ad is played.

The log use cases may include various types of test cases capable of generating logs, which are not limited here. In the test case, different parameters are combined into links, and logs can be generated by accessing the links. The content of the logs generated by different links is different. Log files generated by different log cases are stored in different folders in the log server. Log files within a preset time period, for example, within 1 hour, can be obtained in a folder, which is not limited here. The log testing method of this embodiment can test the selected log use cases or all the log use cases included in the system to determine whether each log use case can run normally, which can improve the test efficiency of the log use cases.

In a possible implementation, as shown in Figure 2, the log test method also includes:

Step 102a, when the folder includes other log files, delete all the log files included in the folder.

The log testing method of the embodiment of the present invention needs to generate a target log file according to the target log use case to be tested, and compare the content recorded in the target log file with the preset content of the target log use case. In this process, in order to avoid the failure of the test due to the inability to distinguish other log files that already exist in the folder from the target log file, it is necessary to generate the target log file when the folder does not contain other log files.

In a specific implementation process, the log test method in the embodiment of the present invention may include a judging step. For example, first determine whether the folder includes other log files, and if no other log files are included, directly generate the target log file; if other log files are included, delete all the log files included in the folder, and then regenerate into the target log file. The log test method in the embodiment of the present invention may also not include a judging step. For example, before each target log file is generated, a deletion step is performed to delete all log files included in the folder.

It should be noted that those skilled in the art should understand that before deleting all the log files included in the folder, the storage of the log files can be realized by, for example, copying the log files, exporting the content recorded in the log files to the database, etc. , so as to ensure that the content recorded in the log file will not be lost, and it is convenient to query when needed.

In a possible implementation, as shown in Figure 3, in the case that the folder does not include other log files, according to the target log use case to be tested, generate the target log file (step 102), including:

Step 301 , if the folder does not contain other log files, trigger the request link corresponding to the target log use case to generate the target log file.

Network equipment, systems and service programs, etc. will generate log files during operation. In the log use case, different parameters are combined into links, and logs can be generated by accessing the links. The content of the logs generated by different links is different. Further, by accessing the link corresponding to the target log case to be tested, the target log file can be generated. For example, the target log use case may be an FTP log use case, and an FTP log file (target log file) is generated by triggering a system FTP probe. Wherein, the content recorded in the FTP log file may include, for example, the IP address, time, user name used for detection, and the like.

Some operations can be performed on the generated target log files, such as remote viewing, downloading, deleting, etc., which are not limited here. Take viewing the web management log as an example, click the "Web management log" link to enter the log viewing page, select the log file to be viewed in the log file list box, and then click the "View log" button on the right to browse to the web management log. Verbose content in log records.

In a possible implementation, as shown in FIG. 4 , compare the content recorded in the target log file with the preset content of the target log use case, and determine whether the target log use case can Normal operation (step 103), including:

Step 401, open the target log file, and extract the content recorded in the target log file;

Step 402, comparing the content with the preset content, and if the content is the same as the preset content, the target log use case can run normally; or,

Step 403 , comparing the content with the preset content, and if the content is different from the preset content, the target log use case cannot run normally.

In step 401 to step 403 of the embodiment of the present invention, the process of comparing the content recorded in the target log file with the preset content can be performed directly in the log server, or can be performed in the local hard disk after the target log file is downloaded. It is not limited here. Specifically, the process of downloading the target log file is: select the target log file, then click the "Download Log" button, click the "Save" button in the pop-up "File Download" dialog box and specify the storage path.

It should be noted that the target log use case may be pre-designed, so the content recorded in the generated target log file should generally follow the logic of the target log use case. Further, compare the content recorded in the target log file with the preset content, and if the recorded content is the same as the preset content, it means that the content recorded in the generated target log file follows the logic of the target log use case, and the target log use case can normal operation. If the recorded content is different from the preset content, it means that the content recorded in the generated target log file does not follow the logic of the target log use case, and the target log use case cannot run normally.

As an example, the target logging use case is the FTP logging use case. In a test, the FTP log case is triggered by the system with the IP address 192.168.0.257 and the user name is C904, thereby generating an FTP log file (target log file). Open the FTP log file, specifically, the recorded content includes, for example, Time (time): 14:56, IP address: 192.168.0.254, Name (user name): C901. Through comparison, it is found that the content recorded in the FTP log file is different from the preset content, indicating that the FTP log use case cannot run normally.

In a possible implementation manner, as shown in FIG. 5 , when the code of the system to be tested is found to be updated, at least one target log use case to be tested is obtained from the log use cases included in the system.

Specifically, the log test method in the embodiment of the present invention can be packaged into a test module. Further, the test platform can be written by eg Robot Framework, and the test module can be called to test the target log case to be tested. Among them, Robot Framework is a functional automation testing framework written in Python. It has good scalability, supports keyword drive, can test multiple types of clients or interfaces at the same time, and can perform distributed test execution.

In addition, continuous integration can also be monitored through Jenkins. When the code of the system to be tested is found to be updated, at least one target log use case to be tested is selected and automated testing is performed. In the case of frequent system modification, it can save a lot of testing time. Among them, Jenkins is a continuous integration tool developed based on Java, which is used to monitor continuous and repeated work. Its functions can include continuous software version release/test projects, and monitoring work performed by external calls.

As an example of the present invention, as shown in Figure 6, the specific flow of the log test method is as follows:

S601. Log in to the log server remotely. For example, remotely log in to the log server through terminal devices such as mobile phones and computers. When the login is successful, you can perform operations allowed by the log server, such as deleting other log files, reading the target log file, and downloading the target log file. Wherein, the log server can store the target log files generated by the target log use case.

S602. Determine whether the login to the log server is successful. Specifically, if the login to the log server is successful, continue to perform step S603; if the login to the log server fails, the test fails, and the test ends.

Wherein, the log file is usually stored in the Linux server, and the Linux server can be remotely logged in through SSH (Secure Shell, Secure Shell Protocol). If the login is successful, the login success status code will be returned, and if the login fails, the login failure status code and failure reason will also be returned.

S603. Delete all other log files under the folder. Among them, other log files in the embodiment of the present invention are log files generated by the target log use case before the test, and these files are deleted so that after step S604 is performed, only the generated target log files are included in the folder, which is beneficial to the extraction of the target log files .

S604. Access the request link capable of generating the target log file. After step S604 is executed, the system records relevant content in the log file corresponding to the target log use case, and generates the target log file.

S605. Check whether a target log file is generated. Specifically, if the target log file is generated, continue to execute step S606; if the target log file is not generated, the test fails and the test ends.

S606. Extract the content of the target log file into a dictionary. Specifically, store the log content of each column into the corresponding parameter dictionary. The dictionary in this embodiment of the present invention may be stored in a storage manner, for example, stored in a key-value (Key-Value) manner. Wherein, the Key may be the name of the target log case, and the Value may include the content recorded in the target log file. The corresponding Value can be retrieved through the Key.

S607. Determine whether the content of the target log file matches the preset content. Specifically, compare the content with the preset content, and if the content is the same as the preset content, the target log use case can run normally, the test is successful, and the test ends. If the content is different from the preset content, the target log use case cannot run normally, the test fails, and the test ends.

The log test method of the embodiment of the present invention generates a target log file according to the target log use case to be tested, and compares the content recorded in the target log file with the preset content of the target log use case to determine whether the target log use case is normal Running can improve the test efficiency of log use cases.

Furthermore, the log test method of the embodiment of the present invention can be applied to test various types of log use cases, can simulate a large number of log scenarios, increase test coverage, and ensure the quality of log use cases.

Furthermore, when the code of the system is updated, each log use case included in the system can be tested, which can greatly improve the test efficiency, shorten the regression test time, and eliminate the impact of code update on the log use case.

Example 2

Fig. 7 shows a structural block diagram of a log test device according to another embodiment of the present invention. As shown in FIG. 7 , the log test device mainly includes: a search module 11, configured to find a folder for storing target log files in the log server. The generation module 13 is connected with the search module 11 and is configured to generate the target log file according to the target log use case to be tested when the folder does not include other log files. Comparison module 15, connected with the generation module 13, is used to compare the content recorded in the target log file with the preset content of the target log use case, and determine whether the target log use case is normal according to the comparison result run. For specific principles and examples, refer to Embodiment 1 and related descriptions in FIG. 1 .

In a possible implementation manner, as shown in FIG. 8 , further includes: a deletion module 17 configured to delete all log files included in the folder when the folder includes other log files. For specific principles and examples, reference may be made to Embodiment 1 and related descriptions in FIG. 2 .

In a possible implementation manner, the generating module 13 is specifically configured to trigger a request link corresponding to the target log use case to generate the target log file. For specific principles and examples, reference may be made to Embodiment 1 and related descriptions in FIG. 3 .

In a possible implementation manner, the comparison module 15 is specifically configured to open the target log file, and extract the content recorded in the target log file; compare the content with the preset content, If the content is the same as the preset content, the target log use case can run normally; or, compare the content with the preset content, and if the content is different from the preset content In the same situation, the target log use case cannot run normally. For specific principles and examples, reference may be made to Embodiment 1 and related descriptions in FIG. 4 .

In a possible implementation, as shown in FIG. 9 , it also includes: a calling module 10, configured to obtain from each log case included in the system when it is found that the code of the system to be tested is updated. At least one target log case to be tested. For specific principles and examples, reference may be made to Embodiment 1 and related descriptions in FIG. 5 .

The log test device of the embodiment of the present invention generates a target log file according to the target log use case to be tested, and compares the content recorded in the target log file with the preset content of the target log use case to determine whether the target log use case is normal Running can improve the test efficiency of log use cases.

Furthermore, the log test device in the embodiment of the present invention can be applied to test various types of log use cases, can simulate a large number of log scenarios, increase test coverage, and ensure the quality of log use cases.

Furthermore, when the code of the system is updated, each log use case included in the system can be tested, which can greatly improve the test efficiency, shorten the regression test time, and eliminate the impact of code update on the log use case.

Example 3

Fig. 10 shows a structural block diagram of a log test device according to another embodiment of the present invention. The log test device 1100 may be a host server with computing capabilities, a personal computer PC, or a portable portable computer or terminal. The specific embodiments of the present invention do not limit the specific implementation of the computing nodes.

The log testing device 1100 includes a processor (processor) 1110 , a communication interface (Communications Interface) 1120 , a memory (memory) 1130 and a bus 1140 . Wherein, the processor 1110 , the communication interface 1120 , and the memory 1130 communicate with each other through the bus 1140 .

The communication interface 1120 is used for communicating with network devices, where the network devices include, for example, a virtual machine management center, shared storage, and the like.

The processor 1110 is used to execute programs. The processor 1110 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.

The storage 1130 is used for storing files. The memory 1130 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. Memory 1130 may also be a memory array. The storage 1130 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

In a possible implementation manner, the above program may be a program code including computer operation instructions. This program can be specifically used to: realize each step in embodiment 1.

Those skilled in the art can appreciate that each exemplary unit and algorithm steps in the embodiments described herein can be realized by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in the form of hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may choose different methods to implement the described functions for specific applications, but this implementation should not be regarded as exceeding the scope of the present invention.

If the functions are implemented in the form of computer software and sold or used as an independent product, it can be considered that all or part of the technical solution of the present invention (such as the part that contributes to the prior art) is In the form of computer software products. The computer software product is usually stored in a computer-readable non-volatile storage medium, and includes several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all the methods of the various embodiments of the present invention. or partial steps. The aforementioned storage medium includes various media capable of storing program codes such as U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (10)

1. A log test method, characterized in that, comprising: Find the folder used to store the target log file in the log server; When the folder does not include other log files, generate the target log file according to the target log use case to be tested; Comparing the content recorded in the target log file with the preset content of the target log use case, and determining whether the target log use case can run normally according to the comparison result. 2. The method according to claim 1, further comprising: When the folder includes other log files, all log files included in the folder are deleted. 3. The method according to claim 1, wherein, according to the target log use case to be tested, generating the target log file includes: Trigger the request link corresponding to the target log use case to generate the target log file. 4. The method according to claim 1, characterized in that, comparing the content recorded in the target log file with the preset content of the target log use case, and determining whether the target log use case can normal operation, including: Open the target log file, and extract the content recorded in the target log file; Comparing the content with the preset content, if the content is the same as the preset content, the target log use case can run normally; or, comparing the content with the preset content In comparison, if the content is different from the preset content, the target log use case cannot run normally. 5. The method according to any one of claims 1 to 4, further comprising: In the case that the code of the system to be tested is found to be updated, at least one target log use case to be tested is obtained from the log use cases included in the system. 6. A log test device, characterized in that, comprising: A search module, configured to find a folder for storing target log files in the log server; A generation module, connected to the search module, used to generate the target log file according to the target log use case to be tested when the folder does not include other log files; A comparison module, connected to the generation module, is used to compare the content recorded in the target log file with the preset content of the target log use case, and determine whether the target log use case can run normally according to the comparison result. 7. The device according to claim 6, further comprising: A deletion module, configured to delete all log files included in the folder when the folder includes other log files. 8. The device according to claim 6, wherein the generating module is specifically configured to trigger a request link corresponding to the target log use case to generate the target log file. 9. The device according to claim 6, wherein the comparison module is specifically configured to open the target log file, and extract the recorded content of the target log file; Comparing the content with the preset content, if the content is the same as the preset content, the target log use case can run normally; or, comparing the content with the preset content In comparison, if the content is different from the preset content, the target log use case cannot run normally. 10. The device according to any one of claims 6 to 9, further comprising: The calling module is used to obtain at least one target log use case to be tested from the log use cases included in the system when the code of the system to be tested is found to be updated.