Project test methods, apparatus, computer-readable media and electronic equipment

Abstract

This application provides a project testing method, apparatus, computer-readable medium, and electronic device. The method includes: acquiring test data for a target project during a testing period, analyzing the test data to obtain a true test curve for the target project within the testing period; determining a standard test curve corresponding to the target project; comparing the true test curve with the standard test curve to determine the test differences within the testing period; determining the current testing period based on current time information, and generating a test reference corresponding to the current testing period based on the current time information and the test differences, so as to test the target project based on the test reference. The technical solution of this application allows for rapid and intuitive statistical analysis of test data, and simultaneously adjusts the test situation within the current testing period based on the true test data to obtain a more reasonable test plan.

Description

Technical Field

[0001] This application relates to the field of data analysis and visualization technology, and more specifically, to a project testing method, apparatus, computer-readable medium, and electronic device. Background Technology

[0002] Gradual testing refers to the process in software development where developers submit test tasks to testers in a tiered manner after completing the code for project requirements. This avoids uneven distribution of test tasks throughout the testing cycle or a backlog of test tasks concentrated in a certain period, which can affect project testing quality and delivery schedule. However, in actual software project development and management, although developers and testers are aware of the importance of gradual testing, some problems still exist.

[0003] For example, due to the lack of intuitive data metrics, different developers and testers have inconsistent understandings of gradient testing. This leads to situations where, although the gradient testing principle is followed during software project development, the gradient testing slope is often too high or too low, making it difficult to achieve scientific gradient testing. Furthermore, during project debriefing, a large amount of testing task data needs to be manually compiled and analyzed to review whether the project followed gradient testing. However, manually compiled data is often fragmented and incomplete, and may even mislead the project debriefing. Summary of the Invention

[0004] The embodiments of this application provide a project testing method and related equipment, which improves the efficiency and quality of testing.

[0005] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0006] According to one aspect of the embodiments of this application, a project testing method is provided, comprising:

[0007] Obtain the test data of the target project during the testing period, analyze the test data, and obtain the actual test curve of the target project during the testing period;

[0008] Determine the standard test curve corresponding to the target project;

[0009] The actual test curve is compared with the standard test curve to determine the test differences within the test cycle;

[0010] The current test cycle is determined based on the current time information, and a test reference corresponding to the current test cycle is generated based on the current time information and test differences, so as to test the target project based on the test reference.

[0011] According to one aspect of the embodiments of this application, a project testing apparatus is provided, comprising:

[0012] The first analysis module is used to obtain the test data of the target project during the test period, and analyze the test data to obtain the actual test curve of the target project during the test period.

[0013] The second analysis module is used to determine the standard test curve corresponding to the target project.

[0014] The difference comparison module is used to compare the actual test curve with the standard test curve to determine the test differences within the test cycle.

[0015] The adjustment test module is used to determine the current test cycle based on the current time information, and generate a test reference corresponding to the current test cycle based on the current time information and test differences, so as to test the target project based on the test reference.

[0016] According to one aspect of the embodiments of this application, a computer-readable medium is provided having a computer program stored thereon, which, when executed by a processor, implements the project testing method as described in the above embodiments.

[0017] According to one aspect of the embodiments of this application, an electronic device is provided, including: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement the project testing method as described in the above embodiments.

[0018] In some embodiments of this application, the technical solutions provide that, during the project testing process, establish corresponding standard testing curves. During testing, firstly, acquire real testing data, analyze and process it to obtain the corresponding real testing curves, then compare and analyze the real testing curves and standard testing curves to obtain corresponding adjustment methods. Based on these adjustment methods, obtain testing references for the current testing cycle, and finally, implement the target project testing within the current testing cycle based on these references. This achieves rapid and intuitive statistical analysis of testing data, and allows for adjustments to the testing situation within the current testing cycle based on real testing data, resulting in a more reasonable testing plan.

[0019] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0021] Figure 1 A schematic diagram of an exemplary system architecture to which the technical solutions of the embodiments of this application can be applied is shown;

[0022] Figure 2 A flowchart illustrating a project testing method according to an embodiment of this application is shown;

[0023] Figure 3 A flowchart illustrating the steps for obtaining a true test curve according to an embodiment of this application is shown.

[0024] Figure 4 A schematic diagram of the test curve according to an embodiment of this application is shown;

[0025] Figure 5 A schematic diagram of the test curve of another embodiment of this application is shown;

[0026] Figure 6 A block diagram of a project testing apparatus according to an embodiment of this application is shown;

[0027] Figure 7 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0028] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art.

[0029] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0030] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0031] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0032] Figure 1 A schematic diagram of an exemplary system architecture to which the technical solutions of the embodiments of this application can be applied is shown.

[0033] like Figure 1 As shown, the system architecture may include terminal devices (such as...) Figure 1 The device shown includes one or more of a smartphone 101, tablet 102, and portable computer 103 (which could also be a desktop computer, etc.), a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the terminal device and the server 105. The network 104 can include various connection types, such as wired communication links, wireless communication links, etc.

[0034] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, there can be any number of terminal devices, networks, and servers. For example, server 105 could be a server cluster composed of multiple servers.

[0035] Users can use terminal devices to interact with server 105 via network 104 to receive or send messages, etc. Server 105 can be a server that provides various services. For example, users can use terminal device 103 (or terminal device 101 or 102) to upload data viewing and display commands to server 105. When server 105 needs to view and display data, it can retrieve the data to be displayed from the relevant database, analyze and process it to obtain the corresponding display result, and finally display the obtained display result on terminal device 103.

[0036] It should be noted that the project testing method provided in this application embodiment is generally executed by server 105, and correspondingly, the project testing device is generally set in server 105. However, in other embodiments of this application, the terminal device may also have similar functions to the server, thereby executing the project testing scheme provided in this application embodiment.

[0037] The implementation details of the technical solutions in the embodiments of this application are described in detail below:

[0038] Figure 2 This illustration shows a flowchart of a project testing method according to an embodiment of the present application. This project testing method can be executed by a server, which can be... Figure 1 The server shown. (Refer to...) Figure 2 As shown, the test method for this project includes steps S201 to S204.

[0039] Step S201: Obtain the test data of the target project during the test period, and analyze the test data to obtain the actual test curve of the target project during the test period.

[0040] During project development, after completing the required code, corresponding testing is necessary to determine if the project can be executed correctly. Therefore, testing is conducted based on the actual completion status during project development to address any anomalies promptly. Specifically, during the actual testing of the target project, appropriate test submissions are performed based on the actual situation. The time required to complete all tests for a project constitutes a test cycle. By acquiring and analyzing the test data within this test cycle, the true test curve of the target project within that test cycle is obtained.

[0041] For example, when analyzing and processing the test submission information within a test cycle, the test submission status for the entire test cycle can be obtained by statistically analyzing the number of tasks submitted on each test submission date within the test cycle.

[0042] For the target project, after the corresponding code is written, version updates may occur due to project updates. After the version update, it is necessary to ensure that the target project can still run normally, so corresponding testing operations are required. During the testing of the target project, test data can be acquired for any test cycle. Here, based on the current time, the test data of the target project in the previous test cycle is acquired, and then analyzed to obtain the corresponding actual test curve for that test cycle.

[0043] During the testing process of a target project, a start date and a latest submission date for testing are typically set. The testing period can be defined as the time span encompassed by the start date and the latest submission date. Generally, the latest submission date is determined based on the start date and the set testing period. For example, if the start date is August 1, 2022, and the testing period is 5 days, then the latest submission date is August 5, 2022.

[0044] After obtaining the test data for the target project within a testing cycle, it will be analyzed and processed to obtain the corresponding actual test curve. (Refer to...) Figure 3 , Figure 3 A flowchart illustrating the steps for obtaining a true test curve according to an embodiment of this application is shown. These steps include steps S301 to S302.

[0045] Step S301: Filter the test data to obtain the filtered test data;

[0046] Step S302: Perform curve planning on the screened test data to obtain the actual test curve of the target project within the test period.

[0047] Due to the diversity of the obtained test data, appropriate filtering and screening processes are required. Specifically, the test data is filtered to obtain the filtered test data, and then curve planning is performed on the filtered test data to obtain the corresponding real test curve.

[0048] For example, the test submission data includes relevant information each time a test task is submitted, such as test task information, test time, number of tasks, and testers. However, some information may be invalid during analysis, such as the test task identifier. In addition, diverse test submission data is not conducive to analysis and processing. Therefore, when the test submission data is obtained, it is first filtered, and then the filtered test submission data is analyzed to obtain the corresponding real test submission curve.

[0049] When filtering, different processing methods can be applied based on the actual analysis needs. For example, if the analysis requires measuring the number of test tasks on each submission date, then the number of test tasks on each submission date needs to be statistically analyzed. Or, if the analysis requires analyzing the daily distribution of testers, then the testers and corresponding test tasks on each submission date need to be correlated and statistically analyzed. Examples are not listed here.

[0050] Specifically, the filtering process includes: obtaining the time identifier corresponding to each data point in the test data and determining the time category corresponding to the time identifier, wherein the time category includes work category and non-work category; selecting the test data whose time identifier corresponds to the work category from the test data to obtain the filtered test data.

[0051] After obtaining the test data, the time identifier corresponding to each data point in the test data is identified and obtained during the filtering process. Then, the test data is filtered according to the obtained time identifier, specifically according to the time category corresponding to the time identifier, which includes work category and non-work category.

[0052] When acquiring and analyzing test data throughout the entire testing cycle, it is necessary to consider non-working days, as there may be no testing tasks on non-working days. This makes the test curve less intuitive to view. Therefore, before analysis, dates without testing are removed, specifically non-working days. Then, the test data from working days is statistically analyzed to obtain the corresponding curve.

[0053] For example, the filtered test submission data could be the number of test tasks on each testing date, or the percentage of test tasks on each submission date. The actual test submission curve can be obtained by processing the actual data.

[0054] In one embodiment, in addition to considering only the number or proportion of test tasks submitted on each test submission date, other factors, such as the test phase or testers, can also be considered. In actual testing, the task requirements at different phases may differ, resulting in varying test task volumes. Furthermore, different testers may be responsible for different test tasks. Therefore, during analysis and processing, different analysis and processing methods can be performed according to actual needs to obtain the true test submission curves under different conditions.

[0055] Step S202: Determine the standard test curve corresponding to the target project.

[0056] Before obtaining the actual test curve, the standard test curve corresponding to the target project needs to be set according to the preset test strategy. Specifically, the standard test curve for the target project within the testing cycle is determined, and the standard test curve is obtained through appropriate processing.

[0057] For example, a standard test curve is used as a criterion for judging whether the extracted curve is reasonable; therefore, it is essential to obtain a reasonable standard test curve. Specifically, obtaining a standard test curve includes: determining the test dates included in the test cycle and sorting the test dates according to time sequence; generating a standard test curve corresponding to the target project according to preset curve generation rules and the sorted test dates.

[0058] By acquiring the testing time included in the testing cycle, the included testing dates are determined. Within each testing cycle, the testing dates can be designated as Date 1, Date 2, ..., Date n, where n is the length of the testing cycle. By acquiring and sorting the testing dates, and according to pre-set curve generation rules, the corresponding standard extraction curve is obtained. The obtained standard testing curve can be as follows: Figure 4 As shown by curve X in the figure, the value corresponding to each testing date is the sum of the testing rates including the current testing date. The actual testing curve obtained above can be represented as follows: Figure 4 The curve Y is shown in the figure.

[0059] Furthermore, the obtained standard extraction curve and the actual measured curve will differ if the information represented by the horizontal and vertical axes in the coordinate system is different. For example... Figure 5 As shown, Figure 5 Curve A is the standard test curve, and curve B is the actual test curve, with the vertical axis representing the daily test rate.

[0060] It should be noted that when the standard extraction curve is a fixed curve, the standard extraction curve corresponding to each test cycle is the same. However, when the standard extraction curve changes with the actual test cycle, the standard extraction curve corresponding to each test cycle is different. Besides obtaining the standard extraction curve in the way described above, it can also be obtained by analyzing the extraction data and feedback results from all previous test cycles. For example, by statistically analyzing the body measurement rate for each extraction date in all test cycles, and then adjusting the data including the extraction feedback results, the corresponding standard extraction curve can be obtained.

[0061] Step S203: Compare the actual test curve with the standard test curve to determine the test differences within the test cycle.

[0062] After obtaining the actual test curve, it is compared with the standard test curve to determine the test differences of the target item in that test cycle. Specifically, when comparing the actual test curve and the standard test curve, the data corresponding to each test date is compared and analyzed to determine whether corresponding test adjustments are needed in the next test cycle, such as whether the test can be based on the test data of the previous cycle.

[0063] In one embodiment, determining the test difference by comparison includes: comparing the actual test curve with the standard test curve based on the test submission time within the test period to determine the test difference value corresponding to each test submission time; comparing the test difference value with a preset difference value to determine the judgment result for each test submission time within the test period; and determining the test difference within the test period based on the judgment result.

[0064] When making comparisons, the actual test curve and the standard test curve are compared according to the test time to determine the test difference value corresponding to each test time. Then, the obtained test difference value is compared with the preset difference value to determine the judgment result of each test time in the test cycle, so as to obtain the corresponding test difference based on the obtained judgment result.

[0065] by Figure 4 Taking the generation of real and standard test curves as an example, within a test cycle, each test moment corresponds to a data point, namely the test rate. The real and standard test curves are compared and matched based on the test moment. By calculating the difference in test rates, the test difference value corresponding to each test moment can be obtained, which is the test rate difference value. Then, it is compared with a preset threshold to obtain the comparison result corresponding to each test moment. Finally, the test difference is obtained based on the comparison judgment results corresponding to all test moments.

[0066] Since the total test submission rate is recorded at this time, when the test difference value increases, it is determined that the number of test tasks at the current test submission time decreases, and when the test difference value decreases, it is determined that the number of test tasks at the current test submission time increases.

[0067] When comparing the test difference value with the preset difference value, if the test difference value is less than or equal to the preset difference value, it is determined that the test status at that test submission time is normal. If the test difference value is greater than the preset difference value, it indicates that the test workload at that test submission time has decreased, and there is a test submission anomaly. In this case, it may be necessary to adjust the test workload at that test submission time.

[0068] For example, if the standard test curve is a straight line and a test cycle contains 5 working days, then within a test cycle, the value corresponding to date 1 is 0.2, date 2 is 0.4, date 3 is 0.6, date 4 is 0.8, and date 5 is 1.0. However, the values ​​corresponding to the 5 dates in the actual test curve are 0.2, 0.3, 0.35, 0.6, and 1.0, respectively. At this time, the test difference value corresponding to each date is 0, 0.1, 0.25, 0.2, and 0. If the preset difference value is 0.05, then there are test anomalies on dates 2, 3, and 4. That is, when testing is performed on these three dates, the number of test tasks is too small. By comparison, date 5 in the actual test curve needs to test 40% of the test tasks, which will increase the workload on date 5 to some extent, which is not conducive to reasonable testing. Therefore, adjustments are needed.

[0069] Step S204: Determine the current test cycle based on the current time information, and generate a test reference corresponding to the current test cycle based on the current time information and test differences, so as to test the target project based on the test reference.

[0070] After obtaining the test discrepancies, the testing situation in the next testing cycle can be adjusted based on these discrepancies, specifically the submission rate for each submission date within the testing cycle. Specifically, upon obtaining the test discrepancies, the current testing cycle is determined based on the current time information. Then, a submission reference for the current testing cycle is generated based on the current time information and the obtained test discrepancies. Finally, the target project is tested within the current testing cycle based on this submission reference.

[0071] Specifically, this includes: obtaining current time information and determining the current test period based on the current time information and the length of time included in the test period; adjusting the test submission data according to test differences to obtain the test submission reference corresponding to the current test period, and testing the target project based on the test submission reference.

[0072] When determining the current test cycle, the current time information is obtained to determine the test start date. Then, the test submission dates included in the current test cycle are determined according to the test cycle. Finally, the test submission data in the previous cycle is adjusted according to the test differences to obtain the test submission reference corresponding to the current cycle. Then, the target project is tested within the current test cycle according to the obtained test submission reference.

[0073] Specifically, when making adjustments, since the preset difference value is 0.05, and adjustments need to be made for dates 2, 3, and 4, the adjusted results can be 0.2, 0.35 (0.3 + 0.05), 0.55 (0.25 - 0.05 + 0.35), 0.7 (0.2 - 0.05 + 0.55), and 1.0. For the 0.35 corresponding to date 2, it can be directly added to the actual 0.3 by 0.05 (the preset difference value). For the 0.55 corresponding to date 3, it can be added to the obtained 0.35 by the allowable deviation of 0.25 - 0.05 = 0.2. For the 0.7 corresponding to date 4, it can be added to the 0.55 by the allowable deviation of 0.15 (0.2 - 0.05). Of course, the specific adjustment method is not limited.

[0074] Furthermore, adjustments can be made based on actual test feedback. For example, if a particular test submission date experiences frequent reports of busy submissions during the testing cycle, the number of test tasks submitted on that date should be reduced, and the actual test submission curve can also be optimized.

[0075] In the project testing method described above, a corresponding standard testing curve is established during the project testing process. During testing, real testing data is first acquired and analyzed to obtain the corresponding real testing curve. Then, by comparing the real and standard testing curves, appropriate adjustment methods are derived. These methods are then used to adjust the data and obtain a testing reference for the current testing cycle. Finally, the target project is tested within the current testing cycle based on this reference. This method enables rapid and intuitive statistical analysis of testing data, and allows for adjustments to the testing situation within the current testing cycle based on real testing data, resulting in a more reasonable testing plan and improving the quality and efficiency of testing.

[0076] The following describes an embodiment of the apparatus described in this application, which can be used to execute the project testing method described above in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the project testing method described above in this application.

[0077] Figure 6 A block diagram of a project testing apparatus according to an embodiment of this application is shown.

[0078] Reference Figure 6 As shown, a project testing apparatus 600 according to one embodiment of this application includes:

[0079] The first analysis module 601 is used to acquire the test data of the target project during the test period, and analyze the test data to obtain the actual test curve of the target project during the test period.

[0080] The second analysis module 602 is used to determine the standard test curve corresponding to the target project;

[0081] The difference comparison module 603 is used to compare the actual test curve with the standard test curve to determine the test difference within the test cycle.

[0082] The adjustment test module 604 is used to determine the current test cycle based on the current time information, and generate a test reference corresponding to the current test cycle based on the current time information and test differences, so as to test the target project based on the test reference.

[0083] Figure 7 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown.

[0084] It should be noted that, Figure 7 The computer system of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0085] like Figure 7 As shown, the computer system includes a Central Processing Unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 702 or loaded from storage portion 708 into Random Access Memory (RAM) 703, such as performing the methods described in the above embodiments. The RAM 703 also stores various programs and data required for system operation. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An Input / Output (I / O) interface 705 is also connected to the bus 704.

[0086] The following components are connected to I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 710 as needed so that computer programs read from it can be installed into storage section 708 as needed.

[0087] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs various functions defined in the system of this application.

[0088] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0089] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0090] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0091] In another aspect, this application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods described in the above embodiments.

[0092] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0093] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, touch terminal, or network device, etc.) to execute the method according to the embodiments of this application.

[0094] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.

[0095] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method of testing an item, characterized by, The method comprises the following steps: obtaining test data of a target project in a test period, and analyzing the test data to obtain a real test curve of the target project in the test period; determining a standard test curve corresponding to the target project; comparing the real test curve with the standard test curve to determine a test difference in the test period; the test difference is used to represent a difference in test rate; determining a current test period according to current time information, and generating a test reference corresponding to the current test period based on the current time information and the test difference, so as to test the target project based on the test reference; the method of determining a current test period according to current time information, and generating a test reference corresponding to the current test period based on the current time information and the test difference, so as to test the target project based on the test reference, comprises the following steps: obtaining current time information, and determining a current test period according to the current time information and a length of time contained in the test period; adjusting the test data according to the test difference to obtain a test reference corresponding to the current test period, so as to test the target project based on the test reference.

2. The method of claim 1, wherein, the method of analyzing the test data to obtain a real test curve of the target project in the test period, comprises the following steps: screening the test data to obtain screened test data; planning a curve based on the screened test data to obtain a real test curve of the target project in the test period.

3. The method of claim 2, wherein, the method of screening the test data to obtain screened test data, comprises the following steps: obtaining a time identifier corresponding to each data in the test data, and determining a time category corresponding to the time identifier, wherein the time category comprises a work category and a non-work category; selecting test data corresponding to the time identifier of the work category from the test data to obtain screened test data.

4. The method of claim 1, wherein, the method of determining a standard test curve corresponding to the target project, comprises the following steps: determining test dates contained in the test period, and sorting the test dates based on time sequence; generating a standard test curve corresponding to the target project according to a preset curve generation rule and the sorted test dates.

5. The method of claim 1, wherein, the method of comparing the real test curve with the standard test curve to determine a test difference in the test period, comprises the following steps: comparing the real test curve with the standard test curve based on test time in the test period to determine a test difference value corresponding to each test time; comparing the test difference value with a preset difference value to determine a judgment result of each test time in the test period; determining a test difference in the test period according to the judgment result.

6. The method of claim 5, wherein, the method of comparing the test difference value with a preset difference value to determine a judgment result of each test time in the test period, comprises the following steps: if the test difference value is less than or equal to the preset difference value, it is determined that the test time corresponding to the test difference value is normal; If the test difference value is greater than the preset difference value, it is determined that the test at the test time corresponding to the test difference value is abnormal.

7. An item testing apparatus characterized by comprising: The item testing device comprises: A first analysis module is configured to acquire test data of a target item at a test period and analyze the test data to obtain a real test curve of the target item at the test period. A second analysis module is configured to determine a standard test curve corresponding to the target item. A difference comparison module is configured to compare the real test curve with the standard test curve to determine a test difference at the test period, wherein the test difference is used to represent a difference in test rate. An adjustment testing module is configured to determine a current test period according to current time information and generate a test reference corresponding to the current test period based on the current time information and the test difference, so as to test the target item based on the test reference. The adjustment testing module is configured to determine a current test period according to current time information and generate a test reference corresponding to the current test period based on the current time information and the test difference, so as to test the target item based on the test reference, comprising: Obtaining current time information and determining a current test period according to the current time information and a length of time contained in the test period. Adjusting the test data according to the test difference to obtain a test reference corresponding to the current test period, so as to test the target item based on the test reference.

8. A computer readable medium having stored thereon a computer program, characterized in that, The computer program, when executed by a processor, implements the item testing method of any one of claims 1 to 6.

9. An electronic device, comprising: Comprise: One or more processors; A storage device is configured to store one or more programs, when the one or more programs are executed by the one or more processors, make the one or more processors realize the item testing method of any one of claims 1 to 6.

10. A computer program product, characterised in that, Comprise computer instructions, when the computer instructions are executed, realize the item testing method of any one of claims 1 to 6.

Images