CN113722208B - Project progress verification method and device for software test report - Google Patents
Project progress verification method and device for software test report Download PDFInfo
- Publication number
- CN113722208B CN113722208B CN202110624363.2A CN202110624363A CN113722208B CN 113722208 B CN113722208 B CN 113722208B CN 202110624363 A CN202110624363 A CN 202110624363A CN 113722208 B CN113722208 B CN 113722208B
- Authority
- CN
- China
- Prior art keywords
- project
- progress
- test
- data
- progress information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The application is suitable for the technical field of software testing, and particularly discloses a project progress verification method and device for a software test report, wherein in the method, the software test report is acquired; respectively extracting first tab data and second tab data from the software test report; identifying whether project test progress information in the first tab data and the second tab data are consistent; if the project progress verification is consistent, determining that the project progress verification is passed; and if not, executing project progress verification alarm operation. Therefore, the condition that project progress in different tabs of the software test report is inconsistent is automatically identified, and time and cost of manual inspection can be effectively saved.
Description
Technical Field
The application belongs to the technical field of software testing, and particularly relates to a project progress verification method and device for a software testing report.
Background
Software testing is an active process of verifying and validating software products (including staged products) throughout the software development lifecycle, with the objective of finding as early as possible various problems in the software products-where they are inconsistent with user requirements, predefined definitions, for further software optimization.
To ensure test progress, test groups need to aggregate test project progress on a regular basis (e.g., weekly). To facilitate the TPM (Test project manager ) to fill out project progress, recording is done using a software test report that can be synchronized for editing by multiple persons without conflicts, typically there are two tabs (i.e., sheets), with all project progress filled in a first tab (e.g., test project progress week report), including content of progress, time, current week work and next week work schedule, etc., and with the second tab (e.g., project data) requiring that the content in the first tab be manually copied to the second tab.
In the process of filling a software test report, the most error-prone is filling of the test progress, for example, when a user updates the project progress in a first tab and forgets to update the project progress in a second tab, the project progress of the first tab and the project progress of the second tab are inconsistent, and manual checking also needs to be compared one by one, so that a certain labor time cost is consumed.
Disclosure of Invention
In view of this, the embodiment of the application provides a project progress verification method and device for a software test report, which are used for at least solving the problem that progress information on different tabs in the software test report in the prior art is inconsistent.
A first aspect of the embodiment of the application provides a project progress verification method for a software test report, which comprises the following steps: acquiring a software test report; respectively extracting first tab data and second tab data from the software test report; identifying whether project test progress information in the first tab data and the second tab data are consistent; if the project progress verification is consistent, determining that the project progress verification is passed; and if not, executing project progress verification alarm operation.
A second aspect of the embodiment of the present application provides a project progress verification apparatus for a software test report, including: the test report acquisition unit is configured to acquire a software test report; the tab data extraction unit is configured to extract first tab data and second tab data from the software test report respectively; a test progress identifying unit configured to identify whether item test progress information in the first tab data and the second tab data are identical; and a progress coincidence verifying unit configured to determine that the project progress is verified to pass if coincidence, and to perform a project progress verification alarm operation if coincidence.
A third aspect of the embodiments of the present application provides a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the method as described above.
A fourth aspect of the embodiments of the application provides a computer program product for causing an electronic device to carry out the steps of the method as described above when the computer program product is run on the electronic device.
Compared with the prior art, the embodiment of the application has the beneficial effects that:
according to the embodiment of the application, in the project progress verification process of the software test report, the first tab data and the second tab data containing the test progress can be respectively extracted from the software test report, whether the progress information in different tabs is consistent or not is determined through the progress information identification operation, when inconsistent project progress exists, the project progress verification alarm operation is executed, the condition that the project progress is inconsistent in different tabs of the software test report is automatically identified, and the time and the cost of manual inspection can be saved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 illustrates a flowchart of one example of a project progress verification method for a software test report according to an embodiment of the application;
FIG. 2 illustrates a flowchart of one example of identifying project test progress information consistency in accordance with an embodiment of the present application;
FIG. 3 illustrates a flowchart of one example of comparing first project test progress information and second project test progress information in accordance with an embodiment of the present application;
FIG. 4 illustrates a flowchart of an example of a project progress verification method for a software test report according to an embodiment of the application;
FIG. 5 is a block diagram showing an example of a project progress validation apparatus for a software test report according to an embodiment of the application;
fig. 6 is a schematic diagram of an example of an electronic device of an embodiment of the application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to illustrate the technical scheme of the application, the following description is made by specific examples.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In particular implementations, the electronic devices described in embodiments of the application include, but are not limited to, other portable devices such as mobile phones, laptop computers, or tablet computers having touch-sensitive surfaces (e.g., touch screen displays and/or touchpads). It should also be appreciated that in some embodiments, the above-described devices are not portable communication devices, but rather are computers having a touch-sensitive surface (e.g., a touch screen display).
In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device may include one or more other physical user interface devices such as a physical keyboard, mouse, and/or joystick.
Various applications that may be executed on the electronic device may use at least one common physical user interface device such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the terminal may be adjusted and/or changed between applications and/or within the corresponding applications. In this way, the common physical architecture (e.g., touch-sensitive surface) of the terminal may support various applications with user interfaces that are intuitive and transparent to the user.
It should be noted that, the software testing group mainly tests the project of the research and development part, and the testing group needs to summarize the progress of the test project weekly in order to ensure the progress of the test throughout the whole project life cycle. To facilitate the progress of the TPM filling in the project, the shared document (e.g., the enterprise WeChat document) is used for writing, so that the editing of multiple persons can be synchronized, and no conflict is generated. The first sheet page "test project progress weekly report" is to fill out all project progress, including progress, time, week work task, week work plan, etc. In addition, since the formula of the second sheet item data is lost, the first tab content needs to be manually copied in the past in the second sheet item data, the place where errors are often made is the filling of the test progress, and the checking of the test progress also needs a certain manual time.
In view of this, FIG. 1 illustrates a flowchart of one example of a project progress verification method of a software test report according to an embodiment of the application. As for the execution subject of the method of the embodiment of the present application, it may be various types of electronic devices having a processing function, such as various terminal devices of a mobile phone or a computer.
It should be noted that, with the development of the software testing architecture, the shared document has become an important choice for the test group to fill out the test progress, but when different users operate or edit the shared document at the same time, some information mismatch may occur. In filling out test reports, an important process is to fill out and check the test progress, and manual checking results in a lot of labor time cost.
As shown in FIG. 1, in step 110, a software test report is obtained. For example, the user may import a test report to be checked into the terminal device, or the terminal device may automatically detect a corresponding software test report based on a preset path directory.
In step 120, first tab data and second tab data are extracted from the software test report, respectively.
In step 130, it is identified whether the project test progress information in the first tab data and the second tab data are identical.
If the recognition result in step 130 indicates that the progress information is consistent, the process jumps to step 141. If the identification result in step 130 indicates that the progress information is not consistent, the process proceeds to step 143.
In step 141, it is determined that the project progress verification is passed. For example, the terminal device may output a corresponding verification result message to prompt the user for the software test report. Therefore, the result comparison of the same content in different sheet pages in the same document is realized, and the time and error of manual check can be reduced.
In step 143, a project progress verification alarm operation is performed. Illustratively, an audible and visual alarm operation is performed to indicate that project progress information of different tabs in the current software test report is inconsistent.
According to the embodiment of the application, in order to ensure the correctness of the test progress, project test progress information under different tabs in the software test report can be identified, an alarm can be given when the project progress is inconsistent, and the problem of inconsistent test progress is solved by judging through codes, so that a user is reminded of timely paying attention to the abnormal condition of the software test report.
Regarding the implementation details of the above step 110, in some examples of the embodiment of the present application, it may be detected whether there is an editing operation for the original software test report, and when the user editing operation is detected, an edited software test report may be generated according to the original software test report, so as to obtain a software test report to be subjected to project progress verification. Therefore, the terminal equipment can monitor user editing aiming at the software test report, trigger project progress verification operation of the software test report when user editing behaviors exist, and do not respond when no user editing behaviors exist, so that continuous response of the terminal equipment is avoided, and resource consumption of the terminal equipment can be effectively saved.
With respect to the implementation details of step 143 described above, in some examples of embodiments of the present application, item test progress information in the first tab data and the second tab data may be marked. For example, inconsistent project test progress information may be prominently marked, prompting the user for corresponding modifications in a more striking manner.
FIG. 2 illustrates a flowchart of an example of identifying project test progress information consistency in accordance with an embodiment of the present application.
As shown in fig. 2, in step 210, first item test progress information and second item test progress information corresponding to each other are extracted from the first tab data and the second tab data based on a preset test progress tab.
In step 220, it is compared whether the first item test progress information and the second item test progress information are identical.
In the embodiment of the application, the test progress information is extracted from the tab data by the test progress label technology, so that the test progress information can be rapidly and accurately extracted, and the reliability of the progress consistency recognition result is ensured.
In some examples of embodiments of the present application, the project test progress information in the first tab data and the second tab data may be plural (i.e., greater than 1), for example, occupy two columns of data information in the tabs respectively, where the corresponding data information in different columns needs to be compared.
Specifically, the first item test progress information and the second item test progress information respectively include M data information, M > 1. And, each data information in the first item test information corresponds to each data information in the second item test progress information, respectively, for example, each data in a different tab of the same item.
Fig. 3 shows a flowchart of an example of comparing first item test progress information and second item test progress information according to an embodiment of the present application.
As shown in fig. 3, in step 310, the first project test progress information and the second project test progress information are respectively subjected to sequence conversion, so as to obtain a corresponding first data sequence and a corresponding second data sequence.
In step 320, the corresponding data information in the first data sequence and the second data sequence are sequentially matched, so as to identify whether the first project test progress information and the second project test progress information are consistent.
In the embodiment of the application, different test progress data can be verified by sequentially comparing corresponding row data aiming at the test data columns in different tabs, so that the verification efficiency of the test progress aiming at the software test report is improved.
In some application scenarios, the software test report may be a test project week report. It should be noted that, in the test item weekly report, at least ten items are on average weekly, and the test progress in two tabs (i.e., sheets) needs to be checked manually, which is time-consuming, labor-consuming and inefficient. Accordingly, by implementing the technical scheme of the embodiment of the application, whether the test progress filled in the two sheets in the test item weekly report is consistent or not can be automatically checked.
FIG. 4 illustrates a flowchart of an example of a project progress verification method for a software test report according to an embodiment of the application.
As shown in FIG. 4, in step 410, a filled-in test item progress week micro document is exported.
In step 420, the document is stored under the specified project space directory. Illustratively, a Python editing tool may be opened, project created, catalog created, data and src created, and run.py created, with the exported document copied under the data catalog.
In step 430, a preset code is invoked to obtain a path of the document and the document. For example, a package OS may be imported to obtain a document directory and this file.
In step 440, the first sheet "test item progress week" content is read.
In step 450, the test progress is filtered out and saved to the designated DataFrame 1.
Specifically, pandas can be imported, the content of the first sheet 'test item progress week report' can be acquired, a method is called, loc screens out a test progress column, a method is used, apply removes empty columns, acquires a percentage format, and stores the data frame1 after serialization.
In step 460, the second sheet "project data" content is read.
In step 470, the test progress is filtered out and saved to the specified DataFrame 2.
Specifically, the second sheet "item data" content may be obtained, and the method is called.
In step 480, dataFrame1 and DataFrame2 data loops are acquired.
In step 490, the data is compared to see if they are consistent.
If the detection result of step 490 indicates that the data alignment is consistent, then step 4110 is skipped. If the detection result of step 490 indicates that the data alignment is inconsistent, then step 4120 is skipped.
In step 4110, the progress of the corresponding item (e.g., item) is printed out in agreement
In step 4120, the progress of the red font output corresponding item (e.g., the # # item) is not uniform, and the progress is a, B, respectively.
In the embodiment of the application, the progress values in the two dataframes are circularly acquired and compared, so that whether the corresponding project progress information of different test progress columns in the software test report is consistent or not can be effectively identified. Therefore, the problem that the test progress in two sheets is checked manually before is solved, the time is greatly shortened, the program execution only needs a few seconds, the first sheet is modified manually later, the contents of the two sheets are checked again, and the efficiency is improved through automatic checking.
Fig. 5 is a block diagram showing an example of a project progress verification apparatus of a software test report according to an embodiment of the present application.
As shown in fig. 5, the project progress verification apparatus 500 of the software test report includes a test report acquisition unit 510, a tab data extraction unit 520, a test progress recognition unit 530, and a progress coincidence verification unit 540.
The test report acquisition unit 510 is configured to acquire a software test report.
The tab data extraction unit 520 is configured to extract first tab data and second tab data from the software test report, respectively.
The test progress identifying unit 530 is configured to identify whether item test progress information in the first tab data and the second tab data are identical.
The progress coincidence verifying unit 540 is configured to determine that the project progress verification passes if coincidence, and to perform a project progress verification alarm operation if coincidence.
In some examples of embodiments of the present application, the test progress recognition unit 530 includes: a progress extraction module (not shown) configured to extract first item test progress information and second item test progress information corresponding to each other from the first tab data and the second tab data based on a preset test progress label; a progress comparison module (not shown) configured to compare whether the first item test progress information and the second item test progress information are identical.
It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein.
Fig. 6 is a schematic diagram of an example of an electronic device of an embodiment of the application. As shown in fig. 6, the electronic device 600 of this embodiment includes: a processor 610, a memory 620, and a computer program 630 stored in the memory 620 and executable on the processor 610. The processor 610, when executing the computer program 630, implements the steps in the project progress verification method embodiment of the software test report described above, such as steps 110 through 143 shown in fig. 1. Alternatively, the processor 610, when executing the computer program 630, performs the functions of the modules/units of the apparatus embodiments described above, e.g., the functions of the units 510 to 540 shown in fig. 5.
Illustratively, the computer program 630 may be partitioned into one or more modules/units that are stored in the memory 620 and executed by the processor 610 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing the specified functions, which are used to describe the execution of the computer program 630 in the electronic device 600. For example, the computer program 630 may be divided into a test report acquisition program module, a tab data extraction program module, a test progress recognition program module, and a progress consistency verification program module, each of which functions as follows:
the test report acquisition program module is configured to acquire a software test report;
the tab data extraction program module is configured to extract first tab data and second tab data from the software test report respectively;
a test progress recognition program module configured to recognize whether item test progress information in the first tab data and the second tab data are identical;
and the progress consistency verification program module is configured to determine that the project progress verification is passed if consistency is achieved, and execute project progress verification alarm operation if the project progress verification is not achieved.
The electronic device 600 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. The electronic device may include, but is not limited to, a processor 610, a memory 620. It will be appreciated by those skilled in the art that fig. 6 is merely an example of an electronic device 600 and is not intended to limit the electronic device 600, and may include more or fewer components than shown, or may combine certain components, or may be different components, e.g., the electronic device may further include an input-output device, a network access device, a bus, etc.
The processor 610 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 620 may be an internal storage unit of the electronic device 600, such as a hard disk or a memory of the electronic device 600. The memory 620 may also be an external storage device of the electronic device 600, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the electronic device 600. Further, the memory 620 may also include both internal storage units and external storage devices of the electronic device 600. The memory 620 is used to store the computer program and other programs and data required by the electronic device. The memory 620 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. For specific working processes of the units and modules in the system, reference may be made to corresponding processes in the foregoing method embodiments.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/electronic device and method may be implemented in other manners. For example, the apparatus/electronic device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of 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.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The above units may be implemented in hardware or in software.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (6)
1. The project progress verification method for the software test report is characterized by comprising the following steps of:
acquiring a software test report;
respectively extracting first tab data and second tab data from the software test report;
identifying whether project test progress information in the first tab data and the second tab data are consistent;
if the project progress verification is consistent, determining that the project progress verification is passed; and
if the project progress verification alarm operation is inconsistent, executing the project progress verification alarm operation;
wherein the identifying whether the project test progress information in the first tab data and the second tab data is consistent includes:
extracting first project test progress information and second project test progress information which correspond to the first tab data and the second tab data respectively based on a preset test progress label;
comparing whether the first project testing progress information is consistent with the second project testing progress information;
wherein, first project test progress information and second project test progress information contains M data information respectively, M > 1, whether the comparison first project test progress information and second project test progress information are unanimous includes:
performing sequence conversion on the first project testing progress information and the second project testing progress information respectively to obtain a corresponding first data sequence and a corresponding second data sequence;
and sequentially matching corresponding data information in the first data sequence and the second data sequence, so as to identify whether the first project test progress information and the second project test progress information are consistent.
2. The method of claim 1, wherein the performing project progress verification alarm operations comprises:
and marking project testing progress information in the first tab data and the second tab data.
3. The method of claim 1, wherein the obtaining a software test report comprises:
detecting whether editing operation aiming at an original software test report exists or not;
when the user editing operation is detected, an edited software test report is generated according to the original software test report so as to obtain a software test report to be subjected to project progress verification.
4. A project progress verification device for a software test report, comprising:
the test report acquisition unit is configured to acquire a software test report;
the tab data extraction unit is configured to extract first tab data and second tab data from the software test report respectively;
a test progress identifying unit configured to identify whether item test progress information in the first tab data and the second tab data are identical;
a progress coincidence verification unit configured to determine that the project progress verification passes if coincidence, and to perform a project progress verification alarm operation if coincidence;
wherein, the test progress identification unit includes:
the progress extraction module is configured to extract first project test progress information and second project test progress information which correspond to the first tab data and the second tab data respectively based on a preset test progress label;
a progress comparison module configured to compare whether the first item test progress information and the second item test progress information are identical;
wherein the first project test progress information and the second project test progress information respectively include M data information, M > 1, the progress comparison module configured to compare whether the first project test progress information and the second project test progress information are consistent, comprising:
performing sequence conversion on the first project testing progress information and the second project testing progress information respectively to obtain a corresponding first data sequence and a corresponding second data sequence;
and sequentially matching corresponding data information in the first data sequence and the second data sequence, so as to identify whether the first project test progress information and the second project test progress information are consistent.
5. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to any one of claims 1-3 when the computer program is executed.
6. A computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the method according to any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110624363.2A CN113722208B (en) | 2021-06-04 | 2021-06-04 | Project progress verification method and device for software test report |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110624363.2A CN113722208B (en) | 2021-06-04 | 2021-06-04 | Project progress verification method and device for software test report |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113722208A CN113722208A (en) | 2021-11-30 |
| CN113722208B true CN113722208B (en) | 2023-09-05 |
Family
ID=78672881
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110624363.2A Active CN113722208B (en) | 2021-06-04 | 2021-06-04 | Project progress verification method and device for software test report |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113722208B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009082590A1 (en) * | 2007-12-26 | 2009-07-02 | Visa U.S.A. Inc. | System and method for tracking testing of software modification projects |
| CN103530324A (en) * | 2013-09-24 | 2014-01-22 | 金蝶软件（中国）有限公司 | Data updating method and relevant device applied to multiple tabs |
| CN106909604A (en) * | 2015-12-22 | 2017-06-30 | 清华大学 | The automatic check method and system of rule-based EXCEL lists and ACCESS databases |
| CN108984418A (en) * | 2018-08-22 | 2018-12-11 | 中国平安人寿保险股份有限公司 | Software testing management method, device, electronic equipment and storage medium |
| CN110096434A (en) * | 2019-03-28 | 2019-08-06 | 咪咕文化科技有限公司 | A kind of interface test method and device |
| CN111078579A (en) * | 2019-12-31 | 2020-04-28 | 河北省科学院应用数学研究所 | Monkey testing method and device and terminal equipment |
| WO2020233330A1 (en) * | 2019-05-20 | 2020-11-26 | 深圳壹账通智能科技有限公司 | Batch testing method, apparatus, and computer-readable storage medium |
| CN112184493A (en) * | 2020-10-06 | 2021-01-05 | 广州云莫凡信息科技有限公司 | Data processing method, system and storage medium based on big data and assembly type building platform |
| CN112395188A (en) * | 2020-11-06 | 2021-02-23 | 武汉木仓科技股份有限公司 | Test-oriented software project development method and device, electronic equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4218708B2 (en) * | 2006-07-20 | 2009-02-04 | コニカミノルタビジネステクノロジーズ株式会社 | Control program for controlling image forming apparatus |
| US10824644B2 (en) * | 2017-03-07 | 2020-11-03 | Mcafee, Llc | Aggregate, index based, synchronization of node contents |
-
2021
- 2021-06-04 CN CN202110624363.2A patent/CN113722208B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009082590A1 (en) * | 2007-12-26 | 2009-07-02 | Visa U.S.A. Inc. | System and method for tracking testing of software modification projects |
| CN103530324A (en) * | 2013-09-24 | 2014-01-22 | 金蝶软件（中国）有限公司 | Data updating method and relevant device applied to multiple tabs |
| CN106909604A (en) * | 2015-12-22 | 2017-06-30 | 清华大学 | The automatic check method and system of rule-based EXCEL lists and ACCESS databases |
| CN108984418A (en) * | 2018-08-22 | 2018-12-11 | 中国平安人寿保险股份有限公司 | Software testing management method, device, electronic equipment and storage medium |
| CN110096434A (en) * | 2019-03-28 | 2019-08-06 | 咪咕文化科技有限公司 | A kind of interface test method and device |
| WO2020233330A1 (en) * | 2019-05-20 | 2020-11-26 | 深圳壹账通智能科技有限公司 | Batch testing method, apparatus, and computer-readable storage medium |
| CN111078579A (en) * | 2019-12-31 | 2020-04-28 | 河北省科学院应用数学研究所 | Monkey testing method and device and terminal equipment |
| CN112184493A (en) * | 2020-10-06 | 2021-01-05 | 广州云莫凡信息科技有限公司 | Data processing method, system and storage medium based on big data and assembly type building platform |
| CN112395188A (en) * | 2020-11-06 | 2021-02-23 | 武汉木仓科技股份有限公司 | Test-oriented software project development method and device, electronic equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 软件测试过程控制系统的研究和设计;李玲玲;徐娟娟;;软件导刊(第04期);21-23 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113722208A (en) | 2021-11-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11182544B2 (en) | User interface for contextual document recognition | |
| CN107480068A (en) | Code integrity detection method, device, electric terminal and readable storage medium storing program for executing | |
| CN111858698B (en) | Data checking method, data checking device and terminal equipment | |
| CN112529575A (en) | Risk early warning method, equipment, storage medium and device | |
| CN112306495A (en) | Picture verification method and device, computer equipment and computer-readable storage medium | |
| CN113434542B (en) | Data relationship identification method and device, electronic equipment and storage medium | |
| CN111367531A (en) | Code processing method and device | |
| CN114816993A (en) | Full link interface test method, system, medium and electronic equipment | |
| CN109918385A (en) | Tripartite's account checking method, electronic device and readable storage medium storing program for executing | |
| CN112287936A (en) | Optical character recognition test method and device, readable storage medium and terminal equipment | |
| CN113722208B (en) | Project progress verification method and device for software test report | |
| CN108520063B (en) | Event log processing method and device and terminal equipment | |
| CN114816772B (en) | Debugging method, debugging system and computing device for application running based on compatible layer | |
| CN113221888B (en) | License plate number management system test method and device, electronic equipment and storage medium | |
| CN110570207A (en) | commodity tracing method and device | |
| CN110597536B (en) | Software upgrading method, system and terminal equipment | |
| CN110018828B (en) | Source code checking method and device and terminal equipment | |
| CN113407748A (en) | Important blank certificate management method and device | |
| CN112698883A (en) | Configuration data processing method, device, terminal and storage medium | |
| CN112685304A (en) | Front-end information standard checking method, system, device and storage medium | |
| CN113051171A (en) | Interface test method, device, equipment and storage medium | |
| CN112003837A (en) | Intelligent equipment adaptation method and device based on Modbus protocol and storage medium | |
| KR20170011054A (en) | Computing device and computer program stored on conputer-readable medium for comparing spread sheet document | |
| CN108235324B (en) | Short message template testing method and server | |
| CN111026307B (en) | Method and device for quickly associating graphics primitives in graphics configuration tool |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |