Test daily report generation method and device, terminal equipment and storage medium

Abstract

The invention is suitable for the technical field of computers, and provides a test daily report generation method and device, terminal equipment and a storage medium, and the method comprises the steps: firstly generating a test daily report template according to historical test data; responding to a data editing instruction sent by a user through the visual editing panel, and obtaining target test data carried in the data editing instruction; and finally, in combination with the test daily report template and the target test data, generating a test daily report. Therefore, the test daily report template is automatically generated in advance according to the historical test data, and the final test daily report can be generated only by editing the test data by the user on the basis of the test daily report template, so that the efficiency of generating the test daily report is improved.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and in particular, relates to a test daily report generation method, apparatus, terminal equipment and storage medium. Background Art

[0002] Testing is a crucial part of software development. At the end of each testing cycle, testers usually need to manually write a daily test report and send it to relevant personnel to report the test results. However, this method is time-consuming, labor-intensive and inefficient. Summary of the invention

[0003] The embodiments of the present application provide a test daily report generation method, apparatus, terminal device and storage medium, which can solve the problem of low efficiency in manually writing test daily reports.

[0004] A first aspect of an embodiment of the present application provides a test daily report generation method, comprising:

[0005] Generate a test daily report template based on historical test data; in response to a data editing instruction sent by a user through a visual editing panel, obtain the target test data carried in the data editing instruction; and generate a test daily report by combining the test daily report template and the target test data.

[0006] In a possible implementation of the first aspect, generating a test daily report template according to historical test data includes:

[0007] Calling a pre-built data mining model to analyze historical test data to obtain mining results, wherein the mining results include target test information and / or target test indicators;

[0008] Generate a test daily report template based on target test information and / or target test indicators.

[0009] Optionally, in another possible implementation of the first aspect, calling a pre-built data mining model to analyze historical test data to obtain mining results includes:

[0010] Based on the historical test data, at least one data warehouse is established, wherein each data warehouse has different dimensions;

[0011] The data mining model is called to analyze the data contained in each data warehouse respectively to obtain the mining results corresponding to each data warehouse.

[0012] Optionally, in yet another possible implementation of the first aspect, before generating a test daily report by combining the test daily report template and the target test data, the method further includes:

[0013] In response to a template editing instruction of the test daily report template issued by the user, the test daily report template is updated, wherein the template editing instruction includes at least one of an adding instruction, a modifying instruction, a deleting instruction and a moving instruction.

[0014] Optionally, in another possible implementation of the first aspect, the users include at least two, and the step of responding to the data editing instruction sent by the user through the visual editing panel, obtaining the target test data carried in the data editing instruction, includes:

[0015] In response to the data editing instruction sent by each user through the visual editing panel, obtaining the initial test data carried in each data editing instruction;

[0016] In response to the save editing instruction sent by each user through the visual editing panel in turn, the initial test data corresponding to each user is stored in the database;

[0017] After all user operations are completed, target test data is obtained from the database, wherein the target test data includes initial test data corresponding to each user.

[0018] Optionally, in another possible implementation of the first aspect, the test daily report is displayed on a visual editing panel, the test daily report includes a plurality of daily report modules, and the test daily report generating method further includes:

[0019] Generate a parent scroll bar corresponding to the test daily report, and generate child scroll bars corresponding to each daily report module;

[0020] In response to the user's scrolling operation on the parent scroll bar, the display content of the test daily report on the visual editing panel is changed, or,

[0021] In response to the user's scrolling operation on each sub-scroll bar, the display content of the corresponding daily report module on the visual editing panel is changed.

[0022] Optionally, in yet another possible implementation of the first aspect, after the test daily report template and the target test data are combined to generate the test daily report, the method further includes:

[0023] Get the pre-configured daily report delivery time and recipient email address;

[0024] Send the test daily report to the recipient's mailbox at the daily report sending time.

[0025] A second aspect of an embodiment of the present application provides a test daily report generating device, including:

[0026] Template acquisition module, used to generate test daily report template based on historical test data;

[0027] A data acquisition module, used to respond to a data editing instruction sent by a user through a visual editing panel and acquire target test data carried in the data editing instruction;

[0028] The daily report generation module is used to generate a test daily report by combining the test daily report template and target test data.

[0029] A third aspect of an embodiment of the present application provides a terminal device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the test daily report generation method of the first aspect when executing the computer program.

[0030] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the test daily report generation method of the first aspect is implemented.

[0031] A fifth aspect of an embodiment of the present application provides a computer program product. When the computer program product runs on a terminal device, the terminal device executes the test daily report generating method of the first aspect.

[0032] Compared with the prior art, the embodiments of the present application have the following beneficial effects: the embodiments of the present application provide a test daily report generation method, apparatus, terminal device and storage medium, wherein the method first generates a test daily report template based on historical test data; then, in response to a data editing instruction sent by a user through a visual editing panel, obtains the target test data carried in the data editing instruction; and finally, generates a test daily report by combining the test daily report template and the target test data. Thus, by automatically generating a test daily report template based on historical test data in advance, and then on the basis of the test daily report template, the user only needs to edit the test data to generate the final test daily report, thereby improving the efficiency of test daily report generation. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0034] Figure 1 This is a flow chart of a test daily report generation method provided in Example 1 of the present application;

[0035] Figure 2 This is a flow chart of a test daily report generation method provided in Example 2 of the present application;

[0036] Figure 3 This is a flow chart of a method for generating a test daily report provided in Example 3 of the present application;

[0037] Figure 4 It is a structural schematic diagram of a test daily report generating device provided in Embodiment 4 of the present application;

[0038] Figure 5 This is a structural diagram of a terminal device provided in Example 5 of the present application. DETAILED DESCRIPTION

[0039] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0040] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0041] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0042] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.

[0043] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0044] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0045] It should be understood that the size of the serial numbers of each step in this embodiment does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of this application.

[0046] In the related art, at the end of each test cycle, testers usually need to manually write a test daily report and send it to relevant personnel to report the test results. However, this method is time-consuming and labor-intensive, and has low efficiency.

[0047] In view of this, the embodiments of the present application provide a test daily report generation method, apparatus, terminal device and storage medium, which automatically generates a test daily report template based on historical test data in advance, and then based on the test daily report template, the user only needs to edit the test data to generate the final test daily report, thereby improving the efficiency of test daily report generation.

[0048] In order to illustrate the technical solution of the present application, specific embodiments are provided below.

[0049] Reference Figure 1 , shows a flow chart of a test daily report generation method provided in Example 1 of the present application. Figure 1 As shown, the test daily report generation method may include the following steps:

[0050] Step 101, generating a test daily report template based on historical test data.

[0051] In the embodiment of the present application, historical test data can be various data related to software testing, including but not limited to test case execution results, defect reports, performance indicators, etc. The sources of historical test data can include test management tools, version control systems, defect tracking systems, test logs, test reports, databases, historical records, archives, etc. Among them, the test management tool provides storage and tracking functions for test data, and historical test data, such as executed test cases, defect reports, test coverage and other indicators, can be extracted from the test management tool; the version control system can store test code and test data, and previous test data can be obtained by viewing historical submission records and change history. This includes modification, addition and deletion of test cases, as well as change records of test code; the defect tracking system usually records the problems and defects found during the test process, and can obtain historical defect reports, problem solving status and corresponding test results by querying the defect tracking system; in addition, test logs, databases, historical records, etc. are also important sources of historical test data. These documents contain information such as test case execution results, error logs, performance indicators, etc., and can also be used as the basis for generating test daily templates.

[0052] It should be noted that the test information and test indicators that the test daily report template needs to include can be obtained through historical test data. The test information may include test plan, test progress, defect statistics, etc., and the test indicators may include test coverage, defect density, etc. Based on the above test information and test indicators, the structure and layout of the test daily report template can be further designed. For example, the above test information and test indicators can be presented in the form of tables, charts, etc., so as to generate a test daily report template.

[0053] Step 102 : in response to a data editing instruction sent by a user through a visual editing panel, obtaining target test data carried in the data editing instruction.

[0054] In an embodiment of the present application, in order to facilitate users to fill in and edit target test data, a test daily report template can be displayed on a visual editing panel, and the content in the visual editing panel can be updated by responding to the user's editing operation instructions.

[0055] As a possible implementation, the visual editing panel can be created using the wx container in wxPython, which is an excellent GUI (Graphical User Interface) graphics library for Python that allows users to easily create complete, fully-functional GUI user interfaces. The panel is a container in a GUI application that can be used to organize and layout other controls, draw graphics, display data, etc.

[0056] Specifically, you first need to import the wxPython library, create a wx.Frame window, and add a wx.Panel panel, which is a visual editing panel. wx.Frame is a class in wxPython used to create and manage windows. wx.Frame is the top-level window of a GUI application. It provides common window elements such as title bar, menu bar, toolbar, etc. It can also contain other controls and panels. According to actual needs, you can flexibly set window properties, add controls and panels, respond to events, etc. to achieve a user-friendly interface and interactive experience; wx.Panel is a class in wxPython used to create and manage panels.

[0057] In an embodiment of the present application, the test information and test indicators generated by historical test data can be used as initialization loading data for panel drawing, and an initialization template can be drawn during initialization. Furthermore, in order to meet the personalized needs of different users for the test daily report template, the function of customizing and changing the test daily report template can also be enabled. Therefore, as a possible implementation method of the present application, the test daily report template can also be updated in response to the user's template editing instructions for the test daily report template, wherein the template editing instructions include at least one of an add instruction, a modify instruction, a delete instruction, and a move instruction.

[0058] Specifically, you can customize the graphics drawn on the wx.Panel panel, such as tables, charts, etc. Among them, in order to avoid the problem of incomplete drawing, you can use the SetBackgroundColour method of the wx.Panel panel to set the background color of the panel to the desired color. By setting the background color, you can ensure that the entire area of ​​the panel is filled, so that you can get the expected results when performing drawing operations.

[0059] In addition, when drawing a panel, you can first define the basic styles used by the elements in the entire panel, including column styles, CSS (Cascading Style Sheets) styles and values, etc. Among them, CSS is the style used to render tags on the page. In this way, when these elements are needed, they can be inherited from the predefined templates and modified according to personalized needs.

[0060] In actual application, when users want to customize and update the test daily template, they can run the packaged EXE (executable) file to use it for visual editing. Next, parse the BoxSizer layout and initialize the UI (User Interface). BoxSizer is one of the layout managers in wxPython, which is used to manage the layout of controls. BoxSizer can arrange controls horizontally or vertically and automatically adjust their size and position. Specifically, when opening the EXE file, use the Add method of the wxSizer class to add subcontrols to the BoxSizer, and control the layout of the subcontrols in the BoxSizer by setting the scale and alignment of the subcontrols. Use the constructor of the wxBoxSizer class or the parameters of the Add method to set the scale and alignment of the subcontrols, and then add the subcontrols to the BoxSizer, and draw the entire BoxSizer layer by layer according to the currently set template. For example, BoxSizer can be composed of 5 layers of templates. The first layer is the bottom frame setting, the second layer is the scroll bar panel and scroll bar components, the third layer is the module component, the fourth layer is the table component, and the fifth layer is bound to the components of the same module (binding the third and fourth layers), and then load the default CSS style to display the style of the default template. Among them, the CSS style mainly includes background color, font, table, etc. Users can select the style template by themselves. After the end, the user clicks Save. The next time the user enters the page, the last saved latest style can be loaded.

[0061] Further, in order to improve the visualization effect of the test daily report, the test daily report usually includes multiple daily report modules, and each daily report module displays test information and test indicators of different dimensions. In order to facilitate users to update the initial test daily report, a parent scroll bar and a child scroll bar can be set, wherein the parent scroll bar is used to control the sliding of the entire page, that is, to change the display content of the test daily report on the visual editing panel; the child scroll bar is used to control the sliding of the corresponding daily report module, that is, to change the display content of the corresponding daily report module on the visual editing panel. Through this setting, a large amount of content can be displayed without taking up too much space, and a convenient, flexible and easy-to-use development environment can be provided to users to improve user experience. That is, in a possible implementation method of the embodiment of the present application, it can also include: generating a parent scroll bar corresponding to the test daily report, and generating child scroll bars corresponding to each daily report module; in response to the user's scrolling operation on the parent scroll bar, changing the display content of the test daily report on the visual editing panel, or, in response to the user's scrolling operation on each child scroll bar, changing the display content of the corresponding daily report module on the visual editing panel.

[0062] Specifically, you can use the scrolledpanel component in wxPython to draw the sliding panel. When drawing the panel, you can customize the increase and decrease of the number of rows in the list, and you can also automatically determine whether the daily module needs to load a sub-scrollbar based on whether the current daily module is displayed.

[0063] In a possible implementation of the present application, after each update of the test data by the user, the corresponding update data needs to be saved, and the corresponding update data is stored in a cache (cache), so that the user can load the latest data when opening the visual editing panel next time, and it is convenient for subsequent troubleshooting. It should be understood that the present application does not limit the data format and server type of the test data, for example, JSON (JavaScript Object Notation, JS object notation) format and Linux server can be used to save the test data, for example, in Python, the built-in lru_cache decorator can be used to implement the cache function, and the decorator can cache the result of the function, and when the function is called again, if the parameters are the same, the cached result is directly returned. The standard library or third-party library of Python can be used to implement the cache function. Redis (REmote DIctionary Server, remote data service), memcached and other memory databases can be used to store temporary data. The shelve module of Python can be used to cache data in the local file system. It is also important to note that when using cache to store temporary data, you need to pay attention to the life cycle of the cached data to avoid taking up too much memory or disk space. You can set the expiration time of the cache or use the LRU (Least Recently Used) algorithm to automatically clean up expired cached data.

[0064] Step 103, generating a test daily report by combining the test daily report template and the target test data.

[0065] After the user edits the target test data based on the test daily report template, a final test daily report is generated.

[0066] In an embodiment of the present application, after generating a test daily report, the user can manually send the test daily report to the designated user's mailbox to ensure that relevant personnel receive the test results and reports in a timely manner, understand the progress of the test, and take necessary measures in a timely manner.

[0067] Furthermore, in order to ensure that the test results are communicated in a timely manner and reduce the workload of manual operations, the test daily report can be set to be sent on a scheduled basis. That is, as a possible implementation method of the present application, after the above step 103, it also includes: obtaining the pre-configured daily report sending time and recipient email address; and sending the test daily report to the recipient email address at the daily report sending time.

[0068] As a possible implementation method, after generating the test daily report, you can use Python's mail library (such as smtplib) to send the test daily report to the designated user's mailbox at a fixed time. First, you need to pre-set the sender's mailbox, password, recipient's mailbox, email subject and other information. Then organize the test daily report into the email body, which can be in HTML (Hyper Text Markup Language) format or plain text format. Further, you can use the SMTP class in the smtplib library to send the email, and send the email body and email header information to the SMTP server. After the sending is successful, you can confirm it through the information returned by the SMTP server.

[0069] The test daily report generation method disclosed in the above embodiment of the present application first generates a test daily report template based on historical test data; then, in response to a data editing instruction sent by a user through a visual editing panel, the target test data carried in the data editing instruction is obtained; finally, a test daily report is generated by combining the test daily report template and the target test data. Thus, by automatically generating a test daily report template based on historical test data in advance, and then on the basis of the test daily report template, the user only needs to edit the test data to generate the final test daily report, thereby improving the efficiency of test daily report generation.

[0070] In a possible implementation of the present application, since the historical test data is relatively broad, in order to extract the required test information and test indicators from the historical test data, big data technology can be used to analyze and process the collected historical test data, thereby effectively discovering potential problems, anomalies and improvement points.

[0071] See also Figure 2 , shows a flow chart of a test daily report generation method provided in Example 2 of the present application. Figure 2 As shown, the test daily report generation method may include the following steps:

[0072] Step 201 , calling a pre-built data mining model to analyze historical test data to obtain mining results, wherein the mining results include target test information and / or target test indicators.

[0073] It should be noted that the data mining model can be a machine learning model such as a decision tree and a random forest model. By calling the machine learning model to perform data mining analysis on historical test data, the trends and correlations in the historical test data can be obtained. By mining this information, potential problems, anomalies and improvement points can be discovered. Among them, the target test information can include test plans, test progress, defect statistics, etc., and the target test indicators can include test coverage, defect density, etc.

[0074] As a possible implementation method, before data mining the historical test data, data cleaning and data aggregation can be performed on the historical test data. Data cleaning can clean the test data, remove duplicate, invalid or erroneous data, and ensure the accuracy and completeness of the data; data aggregation can integrate test data from different sources and formats to form a unified data set.

[0075] Furthermore, in order to improve the traceability, efficiency and quality of the test, a data warehouse can be established and corresponding analysis can be performed based on each data warehouse. That is, as a possible implementation method of the embodiment of the present application, the above step 201 can include: establishing at least one data warehouse based on historical test data, wherein each data warehouse has different dimensions; calling a data mining model to analyze the data contained in each data warehouse respectively, and obtaining mining results corresponding to each data warehouse.

[0076] For example, you can establish a data warehouse with three dimensions, namely the Pre-test data warehouse, the Testing data warehouse, and the Report data warehouse. The following is a detailed description of the data warehouse of each dimension.

[0077] Among them, the Pre-test data warehouse is used to store pre-test preparation data, mainly including test plans, requirement documents, test cases, and other related documents. These data are essential for the test team to prepare before starting the test. The main purpose of the Pre-test data warehouse is to provide a centralized storage space so that the test team can easily access and share various documents required for the test preparation phase. In the Pre-test data warehouse, the test plan specifies the scope, objectives, and strategies of the test, and clarifies the test resources and schedule. The requirement document contains the functional and performance requirements of the software product, and the test cases are written based on the requirement document to verify the correctness and completeness of the software. Other related documents may include configuration information, test environment settings, and test data. By centrally storing this data in the Pre-test data warehouse, the test team can better control and manage the testing process.

[0078] The Testing data warehouse is used to store data generated during the testing process, including test execution results, error logs, performance indicators, and other test-related data. This data can help testers track and analyze test progress and issues, and provide insights into software quality and stability. In the Testing data warehouse, the test execution results record the execution status and results of each test case, including pass, fail, or skip. The error log contains error and exception information captured during testing to help developers locate and fix problems. Performance indicators are used to evaluate the performance of the system, including response time, throughput, and resource utilization. The Testing data warehouse can also include other test-related data, such as test coverage, code complexity, and static analysis results. By storing and analyzing this data, the testing team can evaluate the effectiveness of the test and discover potential problems and improvement opportunities in the testing process.

[0079] The Report data warehouse is used to store test reports and summary data, including test daily reports, defect reports, test indicators, and other documents related to test results. These data are essential for relevant personnel to understand test results and project progress. In the Report data warehouse, the test daily records the test activities and results of each test cycle, including test case execution, defect discovery and resolution, etc. The defect report contains detailed information about the problems and defects found during the test process, such as description, priority, and impact. Test indicators include test coverage, defect density, pass rate, etc., which are used to evaluate the quality and effectiveness of the test. In addition to test reports and indicators, the Report data warehouse can also include other documents related to test results, such as user feedback, user experience reports, and test summaries. These data can help relevant personnel understand the stability of the software, user satisfaction, and improvement directions. By establishing a Report data warehouse, the test team can easily store and retrieve test reports and related data, making it convenient to share test results with relevant personnel. This helps to communicate test progress in a timely manner, promote decision-making and improvement, and provide valuable reference and experience for subsequent test cycles.

[0080] In the embodiment of the present application, by establishing a data warehouse and performing data mining processing based on the data warehouse of a specific dimension, the test data can be comprehensively and effectively organized and managed, and the traceability and analysis capabilities of the test can be improved.

[0081] Step 202: Generate a test daily report template according to target test information and / or target test indicators.

[0082] It should be noted that the target test information and target test indicators obtained in step 201 are integrated and displayed in the form of tables and charts, etc., and finally a test daily report template is generated.

[0083] Step 203 , in response to a data editing instruction sent by the user through the visual editing panel, obtaining target test data carried in the data editing instruction.

[0084] Step 204: Generate a test daily report by combining the test daily report template and the target test data.

[0085] The specific implementation process and principle of the above steps 203-204 can refer to the detailed description of the above embodiment, which will not be repeated here.

[0086] The test daily report generation method disclosed in the above embodiment of the present application first calls a pre-built data mining model to analyze the historical test data to obtain mining results, wherein the mining results include target test information and / or target test indicators, and then generates a test daily report template based on the target test information and / or target test indicators, and finally responds to the data editing instruction sent by the user through the visual editing panel, obtains the target test data carried in the data editing instruction, and generates a test daily report in combination with the test daily report template and the target test data. Thus, by using the data mining model to analyze and process the collected historical test data, potential problems, anomalies and improvement points can be effectively discovered.

[0087] In a possible implementation of the present application, since the test data may be edited by multiple people at the same time, concurrent editing by multiple people may cause concurrency problems. For example, when multiple users request to save the test data at the same time after updating it, data processing exceptions may easily occur. Therefore, the save operation request of each user can be processed in chronological order. After processing the current request, the updated data is saved in the database in time, and then the next request is processed, so as to solve the concurrency problem of multiple people editing.

[0088] See also Figure 3 , shows a flow chart of a test daily report generation method provided in Example 3 of the present application. Figure 3 As shown, the test daily report generation method may include the following steps:

[0089] Step 301, generating a test daily report template based on historical test data.

[0090] Step 302 , in response to the data editing instruction sent by each user through the visual editing panel, the initial test data carried in each data editing instruction is obtained.

[0091] There are at least two users, and the initial test data is the test data generated by each user each time when editing.

[0092] The specific implementation process and principle of the above steps 301-302 can refer to the detailed description of the above embodiment, which will not be repeated here.

[0093] Step 303: In response to the save editing instruction sent by each user through the visual editing panel, the initial test data corresponding to each user is stored in the database.

[0094] In one possible implementation, when a user opens an EXE file and wants to edit the test daily report, other users can also edit it at the same time. After a user saves the edit, the new test daily report is stored in the database, and a copy of the data can be backed up to the Linux server, and the corresponding cache data in the Linux server is updated, and the editing history of the test daily report is updated. At the same time, locking processing is also performed. For the same test daily report, only one request can be processed at present, and the remaining requests are in a waiting state. After the current request is processed, the next request will be processed to solve the concurrency problem. In addition, when other users open the EXE file again for editing, the data in the cache will be read to display the latest test daily report.

[0095] Step 304: After all user operations are completed, target test data is obtained from the database.

[0096] The target test data includes initial test data corresponding to each user.

[0097] It should be noted that the database stores the initial test data updated by each user and the editing history. After all user operations are completed, the latest test daily report can be obtained from the database.

[0098] Step 305: Generate a test daily report by combining the test daily report template and the target test data.

[0099] The specific implementation process and principle of the above step 305 can refer to the detailed description of the above embodiment, which will not be repeated here.

[0100] The test daily report generation method disclosed in the above embodiment of the present application first generates a test daily report template based on historical test data, then responds to the data editing instructions sent by each user through the visual editing panel, obtains the initial test data carried in each data editing instruction, and then responds to the save editing instructions sent by each user through the visual editing panel in turn, stores the initial test data corresponding to each user in the database, and further obtains the target test data in the database after all user operations are completed, and finally generates a test daily report by combining the test daily report template and the target test data. Thus, by processing each user's save operation request in chronological order, after processing the current request, the test data is saved in the database in time, and then the next request is processed, thereby solving the concurrency problem of multiple people editing.

[0101] See also Figure 4, shows a structural schematic diagram of a test daily report generating device provided in Example 4 of the present application. For the sake of convenience of explanation, only the parts related to the example of the present application are shown.

[0102] The test daily report generating device may specifically include the following modules:

[0103] The template acquisition module 401 is used to generate a test daily report template based on historical test data.

[0104] The data acquisition module 402 is used to respond to the data editing instruction sent by the user through the visual editing panel and acquire the target test data carried in the data editing instruction.

[0105] The daily report generation module 403 is used to generate a test daily report by combining the test daily report template and the target test data.

[0106] The test daily report generation device disclosed in the above embodiment of the present application first generates a test daily report template based on historical test data. Then, in response to a data editing instruction sent by a user through a visual editing panel, the target test data carried in the data editing instruction is obtained. Finally, a test daily report is generated by combining the test daily report template and the target test data. Thus, by automatically generating a test daily report template based on historical test data in advance, and then on the basis of the test daily report template, the user only needs to edit the test data to generate the final test daily report, thereby improving the efficiency of test daily report generation.

[0107] In a possible implementation of the fourth embodiment of the present application, the template acquisition module 401 may specifically include the following submodules:

[0108] The data mining submodule is used to call a pre-built data mining model to analyze historical test data to obtain mining results, wherein the mining results include target test information and / or target test indicators.

[0109] The first generating submodule is used to generate a test daily report template according to target test information and / or target test indicators.

[0110] Furthermore, in another possible implementation of the fourth embodiment of the present application, the data mining submodule may specifically include the following units:

[0111] The data warehouse establishment unit is used to establish at least one data warehouse based on historical test data, wherein the dimensions of each data warehouse are different.

[0112] The data mining unit is used to call the data mining model, analyze the data contained in each data warehouse respectively, and obtain the mining results corresponding to each data warehouse.

[0113] Furthermore, in another possible implementation of the fourth embodiment of the present application, the test daily report generating device may further include the following modules:

[0114] The template updating module is used to update the test daily report template in response to the template editing instruction of the user, wherein the template editing instruction includes at least one of an adding instruction, a modifying instruction, a deleting instruction and a moving instruction.

[0115] Furthermore, in another possible implementation of the fourth embodiment of the present application, the above-mentioned users include at least two, and the above-mentioned data acquisition module 402 may specifically include the following sub-modules:

[0116] The first acquisition submodule is used to respond to the data editing instruction sent by each user through the visual editing panel and acquire the initial test data carried in each data editing instruction.

[0117] The first storage submodule is used to respond in turn to the save editing instruction sent by each user through the visual editing panel, and store the initial test data corresponding to each user in the database.

[0118] The second acquisition submodule is used to acquire target test data from the database after all user operations are completed, wherein the target test data includes initial test data corresponding to each user.

[0119] Further, in another possible implementation of the fourth embodiment of the present application, the test daily report is displayed on a visual editing panel, the test daily report includes multiple daily report modules, and the test daily report generating device may further include the following modules:

[0120] The scroll bar generation module is used to generate a parent scroll bar corresponding to the test daily report, and to generate a child scroll bar corresponding to each daily report module.

[0121] The display change module is used to change the display content of the test daily report on the visual editing panel in response to the user's scrolling operation on the parent scroll bar, or to change the display content of the corresponding daily report module on the visual editing panel in response to the user's scrolling operation on each child scroll bar.

[0122] Furthermore, in another possible implementation of the fourth embodiment of the present application, the test daily report generating device may further include the following modules:

[0123] The information acquisition module is used to obtain the pre-configured daily report sending time and recipient email address.

[0124] The email sending module is used to send the test daily report to the recipient's mailbox at the daily report sending time.

[0125] The test daily report generating device disclosed in the above embodiment of the present application analyzes and processes the collected historical test data by using a data mining model, thereby effectively discovering potential problems, anomalies and improvement points. It also processes each user's save operation request in chronological order, saves the test data in the database in time after processing the current request, and then processes the next request, thereby solving the concurrent problem of multiple people editing.

[0126] The test daily report generating device provided in the embodiment of the present application can be applied in the aforementioned method embodiment. For details, please refer to the description of the aforementioned method embodiment, which will not be repeated here.

[0127] Figure 5 Schematic diagram of the structure of the terminal device provided in Embodiment 5 of the present application. Figure 5 As shown, the terminal device 500 of this embodiment includes: at least one processor 510 ( Figure 5 Only one is shown in the figure) a processor, a memory 520, and a computer program 521 stored in the memory 520 and executable on the at least one processor 510, and when the processor 510 executes the computer program 521, the steps in the above-mentioned test daily report generation method embodiment are implemented.

[0128] The terminal device 500 may be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The terminal device may include, but is not limited to, a processor 510 and a memory 520. Those skilled in the art will appreciate that Figure 5 It is only an example of the terminal device 500 and does not constitute a limitation on the terminal device 500. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components, for example, it may also include input and output devices, network access devices, etc.

[0129] The processor 510 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0130] In some embodiments, the memory 520 may be an internal storage unit of the terminal device 500, such as a hard disk or memory of the terminal device 500. In other embodiments, the memory 520 may also be an external storage device of the terminal device 500, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the terminal device 500. Further, the memory 520 may also include both an internal storage unit of the terminal device 500 and an external storage device. The memory 520 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as the program code of the computer program, etc. The memory 520 may also be used to temporarily store data that has been output or is to be output.

[0131] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0132] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0133] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0134] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0135] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0136] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0137] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0138] The present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed through a computer program product. When the computer program product runs on a terminal device, the terminal device can implement the steps in the above-mentioned method embodiments when executing.

[0139] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application is described in detail with reference to the above-mentioned embodiments, a person skilled in the art should understand that the technical solutions described in the above-mentioned embodiments can still be modified, or some of the technical features can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application.

Claims

1. A test daily report generation method, characterized in that: include: Generate a test daily report template based on historical test data; In response to a data editing instruction sent by a user through a visual editing panel, obtaining target test data carried in the data editing instruction; A test daily report is generated by combining the test daily report template and the target test data.

2. The test daily report generation method according to claim 1, characterized in that: The test daily report template is generated based on the historical test data, including: Calling a pre-built data mining model to analyze the historical test data to obtain mining results, wherein the mining results include target test information and / or target test indicators; The test daily report template is generated according to the target test information and / or the target test indicator.

3. The test daily report generation method according to claim 2, characterized in that: The calling of the pre-built data mining model to analyze the historical test data to obtain the mining results includes: Based on the historical test data, establishing at least one data warehouse, wherein each of the data warehouses has a different dimension; The data mining model is called to analyze the data contained in each data warehouse respectively to obtain the mining results corresponding to each data warehouse.

4. The test daily report generation method according to claim 1, characterized in that: Before generating a test daily report by combining the test daily report template and the target test data, the method further includes: In response to a template editing instruction of the test daily report template issued by a user, the test daily report template is updated, wherein the template editing instruction includes at least one of an adding instruction, a modifying instruction, a deleting instruction and a moving instruction.

5. The test daily report generation method according to claim 1, characterized in that: The users include at least two, and the step of responding to a data editing instruction sent by the user through a visual editing panel, obtaining target test data carried in the data editing instruction includes: In response to the data editing instruction sent by each user through the visual editing panel, obtaining the initial test data carried in each data editing instruction; In response to the save editing instruction sent by each user through the visual editing panel in turn, storing the initial test data corresponding to each user in a database; After all the user operations are completed, the target test data is obtained from the database, wherein the target test data includes initial test data corresponding to each of the users.

6. The test daily report generation method according to claim 1, characterized in that: The test daily report is displayed on the visual editing panel. The test daily report includes a plurality of daily report modules. The test daily report generation method further includes: Generate a parent scroll bar corresponding to the test daily report, and generate a child scroll bar corresponding to each of the daily report modules; In response to the user's scrolling operation on the parent scroll bar, changing the display content of the test daily report on the visual editing panel, or, In response to the user's scrolling operation on each of the sub-scroll bars, the display content of the corresponding daily report module on the visual editing panel is changed.

7. The test daily report generation method according to any one of claims 1 to 6, characterized in that: After the test daily report template and the target test data are combined to generate the test daily report, the method further includes: Get the pre-configured daily report delivery time and recipient email address; Send the test daily report to the recipient's mailbox at the daily report sending time.

8. A test daily report generating device, characterized in that: include: Template acquisition module, used to generate test daily report template based on historical test data; A data acquisition module, configured to respond to a data editing instruction sent by a user through a visual editing panel and acquire target test data carried in the data editing instruction; The daily report generation module is used to generate a test daily report by combining the test daily report template and the target test data.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images