A method, device, equipment and storage medium for sending inspection reminders

Abstract

The present invention relates to the field of data processing technology, and specifically to a method, device, equipment, and storage medium for checking and reminding when sending reports, including: obtaining and saving the login status information of the user when logging into a preset platform; using the login status information to call the preset platform interface to obtain all product line information that the user is responsible for, and then deriving the report information that needs to be sent for the versions within the preset time range of each product line; then obtaining the email records that have been sent for each version; based on the report information and email records, cyclically determining whether the report of each version has been sent; if there is unsent report information, the report information is stored in a designated queue and the latest email sending time is noted; and finally reminding the user. The technical solution shown in the present invention can automatically determine whether the verification report email has been sent and remind the unsent report information, which can reduce the workload of staff and reduce the error rate.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method, device, equipment and storage medium for sending an inspection reminder. Background Art

[0002] As the company's projects continue to develop, the number of its projects is also increasing. In order for each project to achieve the expected results, the test plan and test report for each version of each project need to be sent on the scheduled date. Currently, the entry, exit, and release dates of the corresponding versions of each project are manually checked. After the check is completed, the corresponding test plan and test report emails will be sent out by the user.

[0003] Currently, when and whether the test plan and test report of each version are sent are all manually checked and confirmed. For example, the following steps are required: open the one-stop platform page, which will display multiple responsible product lines; click on one of the product lines and go to the "Version" tab to view the "All Versions" of the product line; click on each version in turn to view the time points for admission, exit, and release, and record these time points; decide which plans and report emails to send based on the test cycle; record the time points for sending the test plan and test report based on the time points for admission, exit, and release; manually record the information obtained in the above steps in Excel or Notepad; staff members occasionally open the Excel or Notepad that records the above information to check whether the email has been sent and mark it to avoid missing emails.

[0004] In summary, manually checking the delivery status of each project is labor-intensive when there are many projects and versions, and it is easy to miss an email when work is busy. Therefore, the current manual verification of project delivery is labor-intensive and has a high error rate. Summary of the Invention

[0005] In view of this, the purpose of the present invention is to provide a method, device, equipment and storage medium for inspection reminder of report sending, so as to solve the problem that the manual verification and sending of projects in the prior art is currently carried out with a large workload and a high error rate.

[0006] According to a first aspect of an embodiment of the present invention, a method for sending a report and reminding an inspection is provided, comprising:

[0007] Step S11: Acquire and save the login status information of the user when logging into the preset platform;

[0008] Step S12: Using the login information, the preset platform interface is called to obtain information about all product lines that the user is responsible for;

[0009] Step S13: Using the login status information, calling the preset platform interface according to the product line traversal, and obtaining the report information that needs to be sent for the version within the preset time range of each product line;

[0010] Step S14: Using the login information, traverse and call the preset platform interface to obtain the email records sent for each version;

[0011] Step S15: Based on the report information and email records, cyclically determine whether each version of the report has been sent;

[0012] Step S16: If there is any unsent report information, the report information is stored in a designated queue and the latest sending time of the email is noted;

[0013] Step S17: After the cyclic judgment is completed, if there is report information in the designated queue, the user is reminded in a preset reminder manner.

[0014] Preferably, the step of obtaining the report information that needs to be sent for each product version within a preset time range includes:

[0015] Using the login information, call the preset platform interface according to the product line traversal to obtain the version within the preset time range of each product line;

[0016] Using the login status information, obtain the access, exit and release time of the version, and calculate the test period using preset rules based on the access, exit and release time;

[0017] The report information that needs to be sent for each version is obtained according to the test cycle and the production and research process rules. The report information includes the test plan and the test report type.

[0018] Preferably, obtaining the entry, exit, and release time of the version includes:

[0019] According to the preset production and research process rules, remove the versions that do not require relevant reports from all versions;

[0020] By using the login status information, the versions that meet the production and research process rules are traversed and called the preset platform interface to obtain the entry, exit and release time of the versions.

[0021] Preferably, the obtaining and saving of login status information of the user when logging into the preset platform includes:

[0022] After the user successfully logs in to the preset platform, the designated request of the preset platform is monitored, and when the designated request is monitored, the login state information of the preset platform is saved.

[0023] Preferably, the method further comprises:

[0024] After the loop judgment is completed, save the timestamp of 0:00 the next day;

[0025] When it is detected that the user enters the preset platform page again, the current time is obtained;

[0026] The current time is compared with the timestamp. If the current time is later than the timestamp, steps S11 to S17 are repeated.

[0027] According to a second aspect of an embodiment of the present invention, there is provided a device for sending a report and reminding an inspection, comprising:

[0028] Login status acquisition module, used to obtain and save the login status information of the user when logging into the preset platform;

[0029] A product line information acquisition module, configured to use the login status information to call the preset platform interface and acquire information on all product lines that the user is responsible for;

[0030] A report information acquisition module is used to use the login status information to call a preset platform interface according to the product line traversal to obtain the report information that needs to be sent for each version within a preset time range of each product line;

[0031] A record acquisition module is used to use the login status information to traverse and call the preset platform interface to obtain the email records sent for each version;

[0032] A judgment module is used to cyclically judge whether each version of the report has been sent based on the report information and email records; if there is unsent report information, the report information is stored in a designated queue and the latest email sending time is noted;

[0033] The reminder module is used to remind the user in a preset reminder manner if there is report information in the designated queue after the cyclic judgment is completed.

[0034] According to a third aspect of an embodiment of the present invention, there is provided a device for sending a report and reminding an inspection, including:

[0035] A main controller, and a memory connected to the main controller;

[0036] a memory in which program instructions are stored;

[0037] The main controller is used to execute program instructions stored in the memory and perform any of the above methods.

[0038] According to a fourth aspect of an embodiment of the present invention, a computer-readable storage medium is provided, storing a computer program, wherein when the computer program is executed by a processor, the computer program implements any of the above methods.

[0039] The technical solutions provided by the embodiments of the present invention may have the following beneficial effects:

[0040] It can be understood that the present invention obtains and saves the login status information of the user when logging into the preset platform; uses the login status information to call the preset platform interface to obtain all product line information that the user is responsible for, and then obtains the report information that needs to be sent for the versions within the preset time range under each product line; then obtains the email records that have been sent for each version; based on the report information and email records, cyclically determines whether the report of each version has been sent; if there is any unsent report information, the report information is stored in a designated queue and the latest email sending time is noted; and finally, the user is reminded. The technical solution shown in the present invention can automatically determine whether the verification report email has been sent and remind the user of the unsent report information, which can reduce the workload of staff and reduce the error rate.

[0041] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0043] Figure 1 This is a schematic diagram showing the steps of a method for sending an inspection reminder report according to an exemplary embodiment;

[0044] Figure 2 The present invention is a schematic block diagram of a device for sending a report and reminding an inspection according to an exemplary embodiment. DETAILED DESCRIPTION

[0045] Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent like or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present invention, as detailed in the appended claims.

[0046] Example 1

[0047] Figure 1This is a schematic diagram of a method for sending a report and reminding an inspection according to an exemplary embodiment. Figure 1 , providing a method for checking reminder of report sending, including:

[0048] Step S11: Acquire and save the login status information of the user when logging into the preset platform;

[0049] It should be noted that the acquisition and storage of the user's login status information when logging into the preset platform includes:

[0050] After the user successfully logs in to the preset platform, the designated request of the preset platform is monitored, and when the designated request is monitored, the login state information of the preset platform is saved.

[0051] In specific practice, the preset platform can be a one-stop platform. When the user opens the one-stop platform and completes the login, the webRequest.onBeforeSendHeaders.addListener method provided by Chrome is used to listen to the request specified by the one-stop platform. After listening to the specified request, the login status in the header is saved to Chrome's storage to save the login status information.

[0052] Step S12: Using the login information, the preset platform interface is called to obtain information about all product lines that the user is responsible for;

[0053] Preferably, before performing step S12, it is also possible to determine whether the user has already performed automatic detection on the same day. If not, step S12 is performed to perform automatic detection.

[0054] In specific practice, when performing step S12, the pre-saved login information can be retrieved from the storage of Chrome, and the one-stop platform interface is called with the login information to obtain all product lines that the user is responsible for.

[0055] Step S13: Using the login status information, calling the preset platform interface according to the product line traversal, and obtaining the report information that needs to be sent for the version within the preset time range of each product line;

[0056] In specific practice, the step S13 of obtaining the report information that needs to be sent for the version of each product line within the preset time range includes:

[0057] Step S131: Using the login information, call the preset platform interface according to the product line traversal to obtain the version within the preset time range of each product line;

[0058] Step S132: Using the login status information, obtain the entry, exit, and release time of the version, and calculate the test period using preset rules based on the entry, exit, and release time;

[0059] It should be noted that, in step S132, obtaining the entry, exit, and release time of the version includes:

[0060] According to the preset production and research process rules, versions that do not require sending relevant reports are eliminated from all versions; using the login status information, the versions that meet the production and research process rules are traversed and called the preset platform interface to obtain the entry, exit and release time of the version.

[0061] It is understandable that by eliminating versions of relevant reports that do not need to be sent through preset production and research process rules, the method can be made more flexible and convenient for users to use.

[0062] Step S133: Determine the report information that needs to be sent for each version according to the test cycle and the production and research process rules. The report information includes the test plan and the test report type.

[0063] Step S14: Using the login information, traverse and call the preset platform interface to obtain the email records sent for each version;

[0064] Step S15: Based on the report information and email records, cyclically determine whether each version of the report has been sent;

[0065] Step S16: If there is any unsent report information, the report information is stored in a designated queue and the latest sending time of the email is noted;

[0066] Step S17: After the cyclic judgment is completed, if there is report information in the designated queue, the user is reminded in a preset reminder manner.

[0067] In practice, if there is no report information in the specified queue, it means that the user has sent all emails and there is no need to remind the user. The way to remind the user is to use the chrome.notifications.create method provided by Chrome to send a browser notification reminder, and at the same time call the Message Center Treasure Box Work Notification API to give the user a Treasure Box Work Notification reminder.

[0068] It can be understood that this embodiment obtains and saves the login status information of the user when logging into the preset platform; uses the login status information to call the preset platform interface to obtain all product line information that the user is responsible for, and then obtains the report information that needs to be sent for the versions within the preset time range under each product line; then obtains the email records that have been sent for each version; based on the report information and email records, it cyclically determines whether the report of each version has been sent; if there is any unsent report information, the report information is stored in a designated queue and the latest email sending time is noted; and finally, the user is reminded. The technical solution shown in this embodiment can automatically determine whether the verification report email has been sent and remind the unsent report information, which can reduce the workload of staff and reduce the error rate.

[0069] It should be noted that the method further includes:

[0070] After the loop judgment is completed, save the timestamp of 0:00 the next day;

[0071] When it is detected that the user enters the preset platform page again, the current time is obtained;

[0072] The current time is compared with the timestamp. If the current time is later than the timestamp, steps S11 to S17 are repeated.

[0073] In specific practice, the timestamp of 0:00 on the next day can be stored in the storage of Chrome. When the user enters the page again, the current timestamp is compared with the timestamp of 0:00 on the next day stored in the storage. If the current time is greater than 0:00 on the next day, it means that the user entered the page on the next day, and steps S11 to S17 are re-executed. If the current time is less than 0:00 on the next day, it means that the user entered the platform page again on the same day, and it has been detected today, so there is no need to detect it again, and no repeated check is required.

[0074] Preferably, a plug-in can be set up on the platform page. Users can click the plug-in icon on the browser page to open the plug-in panel, which can display the versions of unsent test plans and test reports and the latest time when the report of each version needs to be sent. The plug-in panel also provides users with buttons for manually clearing data and rechecking.

[0075] It can be understood that the technical solution provided by the present invention does not require human intervention to check the sending time of each version report and whether the email has been sent. If there are many versions, the workload of checking is large, and when the work is busy, it is easy to miss sending emails; it can be checked completely automatically without the user noticing, and has double insurance of browser notification reminders and treasure box work notification reminders, which minimizes the user's error rate.

[0076] Example 2

[0077] Figure 2 This is a schematic block diagram of a device for sending a report and reminding an inspection according to an exemplary embodiment. Figure 2 , providing a report sending inspection reminder device, comprising:

[0078] The login status acquisition module 101 is used to acquire and save the login status information of the user when logging into the preset platform;

[0079] The product line information acquisition module 102 is configured to use the login information to call the preset platform interface to obtain information on all product lines that the user is responsible for;

[0080] The report information acquisition module 103 is configured to utilize the login status information to call a preset platform interface according to the product line traversal to obtain the report information that needs to be sent for each version within a preset time range of each product line;

[0081] The record acquisition module 104 is used to use the login status information to traverse and call the preset platform interface to obtain the email records sent for each version;

[0082] The judgment module 105 is used to cyclically determine whether each version of the report has been sent based on the report information and the email record; if there is any unsent report information, the report information is stored in a designated queue and the latest email sending time is noted;

[0083] The reminder module 106 is configured to remind the user in a preset reminder manner if there is report information in the designated queue after the cyclic judgment is completed.

[0084] It can be understood that the present invention uses the login status acquisition module 101 to acquire and save the login status information of the user when logging into the preset platform; the product line information acquisition module 102 uses the login status information to call the preset platform interface to obtain information on all product lines that the user is responsible for, and then uses the report information acquisition module 103 to obtain the report information that needs to be sent for the versions within the preset time range under each product line; the record acquisition module 104 obtains the email records that have been sent for each version; the judgment module 105 uses the report information and email records to cyclically determine whether the report of each version has been sent. If there is any unsent report information, the report information is stored in a designated queue and the latest email sending time is noted; and finally, the reminder module 106 reminds the user. The technical solution shown in the present invention can automatically determine whether the verification report email has been sent and remind users of unsent report information, which can reduce the workload of staff and reduce the error rate.

[0085] Example 3

[0086] Provided is a report-sending inspection reminder device, comprising:

[0087] A main controller, and a memory connected to the main controller;

[0088] a memory in which program instructions are stored;

[0089] The main controller is used to execute program instructions stored in the memory and perform any of the above methods.

[0090] Example 4

[0091] A computer-readable storage medium is provided, storing a computer program, wherein when the computer program is executed by a processor, the computer program implements any of the above methods.

[0092] It can be understood that the same or similar parts of the above embodiments can be referenced to each other, and the contents not described in detail in some embodiments can refer to the same or similar contents in other embodiments.

[0093] It should be noted that, in the description of the present invention, the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, the meaning of "plurality" is at least two.

[0094] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention pertain.

[0095] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0096] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0097] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing module, or each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

[0098] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0099] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in conjunction with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0100] Although the embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and are not to be construed as limitations on the present invention. A person skilled in the art may change, modify, replace and modify the above embodiments within the scope of the present invention.

Claims

1. A method for inspection reminder of report sending, characterized in that: include: Step S11: Acquire and save the login status information of the user when logging into the preset platform; Step S12: Using the login information, the preset platform interface is called to obtain information about all product lines that the user is responsible for; Step S13: using the login state information, calling a preset platform interface according to the product line traversal, and obtaining report information that needs to be sent for each version within the preset time range of each product line, including: using the login state information, calling a preset platform interface according to the product line traversal, and obtaining each version within the preset time range of each product line; using the login state information to obtain the entry, exit, and release time of the version, and calculating the test cycle according to the entry, exit, and release time using preset rules; according to the test cycle and the production and research process rules, obtaining the report information that needs to be sent for each version, the report information including the test plan and the test report type; Step S14: Using the login information, traverse and call the preset platform interface to obtain the email records sent for each version; Step S15: Based on the report information and email records, cyclically determine whether each version of the report has been sent; Step S16: If there is any unsent report information, the report information is stored in a designated queue and the latest sending time of the email is noted; Step S17: After the cyclic judgment is completed, if there is report information in the designated queue, the user is reminded in a preset reminder manner.

2. The method according to claim 1, characterized in that The obtaining of the access, exit and release time of the version includes: According to the preset production and research process rules, remove the versions that do not require relevant reports from all versions; By using the login status information, the versions that meet the production and research process rules are traversed and called the preset platform interface to obtain the entry, exit and release time of the versions.

3. The method according to claim 1, characterized in that The obtaining and saving of login status information of the user when logging into the preset platform includes: After the user successfully logs in to the preset platform, the designated request of the preset platform is monitored, and when the designated request is monitored, the login state information of the preset platform is saved.

4. The method according to claim 1, wherein Also includes: After the loop judgment is completed, save the timestamp of 0:00 the next day; When it is detected that the user enters the preset platform page again, the current time is obtained; The current time is compared with the timestamp. If the current time is later than the timestamp, steps S11 to S17 are repeated.

5. A report-sending inspection reminder device, characterized in that: include: Login status acquisition module, used to obtain and save the login status information of the user when logging into the preset platform; A product line information acquisition module, configured to use the login status information to call the preset platform interface and acquire information on all product lines that the user is responsible for; A report information acquisition module is used to use the login state information to call the preset platform interface according to the product line traversal to obtain the report information that needs to be sent for the version within the preset time range of each product line, including: using the login state information to call the preset platform interface according to the product line traversal to obtain the version within the preset time range of each product line; using the login state information to obtain the entry, exit and release time of the version, and using preset rules to calculate the test cycle based on the entry, exit and release time; according to the test cycle and the production and research process rules, obtain the report information that needs to be sent for each version, and the report information includes the test plan and the test report type; A record acquisition module is used to use the login status information to traverse and call the preset platform interface to obtain the email records sent for each version; A judgment module is used to cyclically judge whether each version of the report has been sent based on the report information and email records; if there is unsent report information, the report information is stored in a designated queue and the latest email sending time is noted; The reminder module is used to remind the user in a preset reminder manner if there is report information in the designated queue after the cyclic judgment is completed.

6. A report-sending inspection reminder device, characterized in that: include: A main controller, and a memory connected to the main controller; a memory in which program instructions are stored; The main controller is used to execute program instructions stored in the memory and perform the method according to any one of claims 1 to 4.

7. 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 4 is implemented.

Images