CN112000587B - Test man-hour automatic statistical method based on associated object operation statistics - Google Patents
Test man-hour automatic statistical method based on associated object operation statistics Download PDFInfo
- Publication number
- CN112000587B CN112000587B CN202011180987.1A CN202011180987A CN112000587B CN 112000587 B CN112000587 B CN 112000587B CN 202011180987 A CN202011180987 A CN 202011180987A CN 112000587 B CN112000587 B CN 112000587B
- Authority
- CN
- China
- Prior art keywords
- test
- hour
- data
- page
- tester
- 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
Images
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
-
- 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/3692—Test management for test results analysis
Abstract
A test man-hour automatic statistical method based on associated object operation statistics comprises the following steps: A. establishing an entity element hierarchical tree; B. establishing a test working hour data table; C. adding buried points to operations such as creating use cases, editing use cases, executing use cases, creating defects, updating defect states and the like; D. adding buried points on a graphical user interface, a program method and a program function of software; E. establishing a background management system and establishing a page for testing working hour statistics and analysis; F. and establishing an analysis page for testing time estimation accuracy. The invention tests all three types of work in the working process: writing and executing test cases, testing software, submitting and verifying defects can be converted into operation actions on software entity elements, and the operation duration can be automatically counted by using a data acquisition tool. The method realizes completely objective statistic testing working hours, has real and effective data and high accuracy and reliability.
Description
Technical Field
The invention relates to the technical field of software testing, in particular to a test working hour automatic statistical method based on associated object operation statistics.
Background
With the continuous development of the internet era, software is an indispensable tool for people to process work files daily, and general software has software tester cases to perform functional tests on each module before being put into use formally. In the field of software testing, statistics and analysis of testing man-hour of a project have important significance on efficiency measurement and project quality measurement of testers and testing teams.
At present, the following schemes are mostly adopted for counting the test working hours: before a certain task is started to be executed, the tester fills the estimated testing man-hour of the task in the project management system, and after the task is completed, the tester fills the actual testing man-hour of the task in the project management system. These two items of data are combined at the time of estimating the test man-hour and the actual test man-hour in advance.
The method can measure the complexity of project tasks, the working efficiency of testers and the accuracy of test working hour evaluation to a certain extent. However, the method completely depends on subjective evaluation of testers, has great randomness, is influenced by factors such as experience of the testers, professional ethics level and the like, and is difficult to ensure accuracy and credibility.
Disclosure of Invention
In order to solve the problems, the invention provides an automatic test time counting method based on associated object operation counting, which can completely objectively count test time, and has real and effective data and high accuracy and reliability.
The invention provides a test working hour automatic statistical method based on associated object operation statistics, which comprises the following steps:
A. extracting entity elements of the software, storing the extracted entity elements in an entity element table of a database, establishing a new entity element hierarchical tree or updating an existing entity element hierarchical tree according to the affiliated relationship of the entity elements, and storing the newly established entity element hierarchical tree or the updated entity element hierarchical tree in the entity element hierarchical tree table of the database;
B. establishing a test working hour data table in a database, and collecting the time consumption of operation of a tester on the software entity elements;
C. adding buried points to operations of creating cases, editing cases, executing cases, creating defects and updating defect states on pages of a test case management system and a defect management system, collecting the stay time of a tester for operating the entity elements, and after the operation is completed, transmitting the operation types and the operation stay time data of the entity elements to a background program and storing the data in a test working hour data table of a database;
D. adding buried points on a graphical user interface, a program method and a program function of the software, and collecting the stay time of a tester operating the functional module, the functional component, the program interface, the program method and the entity element of the program function of the software; after the operation is finished, transmitting the operation type of the entity element and the data of the operation stay time to a background program and storing the data into a test working hour data table of a database;
E. establishing a background management system and establishing a page for testing working hour statistics and analysis; the page shows that each tester counts the total time of the testing man-hour of all the entity elements in the working day;
F. establishing an analysis page of the test estimation accuracy in a background management system, displaying the estimated test working hours and the actual test working hours of the software functional module on the page, and calculating and displaying the estimated accuracy; the estimated testing man-hour data is from the existing data in the project management tool, and the actual testing man-hour is from the testing man-hour data table.
The invention tests all three types of work in the working process: writing and executing test cases, testing software, submitting and verifying defects can be converted into operation actions on software entity elements, and the operation duration can be automatically counted by using a data acquisition tool. The method realizes completely objective statistic testing working hours, has real and effective data and high accuracy and reliability.
Further, step a comprises: extracting functional modules, functional components, code modules and entity elements contained in code lines of the software; after the entity elements are extracted, establishing an entity element hierarchical tree according to the actual semantic dependency relationship and storing the entity element hierarchical tree in an entity element hierarchical tree table; the physical element hierarchy tree is updated if it already exists in the physical element hierarchy tree table.
And the step A extracts all entity elements of the software and is used for calculating and counting all testing man-hours for operating the entity elements. The purpose of constructing all entity elements into an entity element hierarchical tree is to query all entity elements belonging to a functional module according to the functional module, so as to calculate and count the whole testing man-hour of the functional module.
Further, step B includes: establishing a test man-hour data table in a database, wherein the test man-hour data table comprises the following fields: primary key ID, entity element ID, tester ID, operation type, operation duration, and operation date of the table;
the test working hour data table is established for storing the operation working hour data of each entity element by the tester.
And the step B is used for recording the operation time of the tester on each software entity element. Because the essence of the testing man-hour is that the operation time of the tester on the software is consumed, the sum of each operation time is the testing man-hour.
Further, step C includes: adding buried points to page operation controls for creating a use case, editing the use case and executing the use case on a page of the test case management system; adding a buried point to a page operation control for creating the defect and updating the defect state on a page of the defect management system;
after a tester makes a case creating operation, a case editing operation or a case executing operation on a test case, the embedded point program sends a corresponding operation event to the background program; or after the tester performs operation of creating the defect or updating the defect state on the defect, the embedded point program sends the corresponding operation event to the background program;
after the background program receives the operation event, the data in the event is analyzed, and test working hour data is generated and stored in a test working hour data table of the database.
And step C, collecting the operation time of each software entity element by a tester in the test case compiling and updating process and the defect compiling and updating process for calculating and counting the test working hours.
Further, step D includes: adding a buried point on a graphical user interface, a program method and a program function of the software, and after a tester operates on the graphical user interface, the program method or the program function of the software, sending a corresponding operation event to a background program by a buried point program;
after the background program receives the operation event, the data in the event is analyzed, and test man-hour data is generated and stored in a test man-hour data table of the database.
And D, collecting the operation time of the tester on each software entity element in the components such as a software interface, a program interface and the like for calculating and counting the test working hours.
Further, step E includes: establishing a background management system, and establishing a test working hour statistics and analysis page; the page is provided with two statistical conditions of ID of a tester and operation date;
when the condition of the operation date is selected for data statistics, the background program screens all test working hour data in the corresponding operation date in the test working hour data table according to the operation date condition, calculates the total test working hour duration for the grouping condition according to the ID of the tester, sends the total test working hour duration for all the testers in the date to a page for display, and can rank in an ascending order or a descending order according to the length of the test working hours;
when two conditions of the tester ID and the operation date are selected simultaneously for data statistics, the background program screens all the test working hour data of the tester in the operation date in the test working hour data table according to the two conditions of the tester ID and the operation date, calculates the total test working hour duration, and sends the total test working hour duration of the tester in the date to a page for display.
And E, summarizing, calculating and counting the collected data to obtain the testing man-hour of the tester for the software entity elements, and outputting the testing man-hour to a page.
Further, step F includes: establishing an analysis page of test estimation accuracy in a background management system, wherein the page is provided with two statistical conditions of a software functional module and a project cycle time period, the data of the software functional module is from an entity element hierarchical tree table of a database, the data of the project cycle time period is from a project management tool, and the page acquires estimated test man-hour data of a tester to the software functional module in each project cycle time period from the project management tool and displays the estimated test man-hour data on the page;
when a certain software function module and a project cycle time period of the function module are selected, a background program inquires an entity element hierarchical tree which takes the name of the software function module as a root node in an entity element hierarchical tree table according to the name of the software function module, acquires all child nodes in the tree, traverses each child node, inquires entity element data corresponding to each child node in the entity element table, screens out corresponding entity element ID and all test man-hour data of a creation date in the project cycle time period in a test man-hour data table according to the two data of the entity element ID and the project cycle time period, finally sums up and calculates the total test man-hour time period, and returns a result to a page;
and displaying the estimated testing man-hour and the actual testing man-hour of the software functional module on a page, and calculating and displaying the estimated man-hour accuracy according to the estimated man-hour accuracy rate = (actual testing man-hour/estimated testing man-hour) × 100%.
And F, comparing the statistical result of the testing man-hour with the estimated man-hour, calculating and displaying the estimated accuracy, and outputting the estimated accuracy to a page.
The invention componentizes the elements of the software functions, software modules, program interfaces, program methods, program functions and the like contained in the test cases and defects which are written into the components, defines the elements as 'entity elements' of the software, and each test case and defect can be converted into the operation action on a certain entity element or certain entity elements. In the software module, the test case management system and the defect management system, a buried point technology is used for adding buried points for entity elements of software and collecting operation actions and operation duration of software entity elements by testers. All three types of work in the test work process: writing and executing test cases, testing software, submitting and verifying defects can be converted into operation actions on software entity elements, and the operation duration can be automatically counted by using a data acquisition tool. We define that only the software entity elements are operated in the test work process, and the effective test work is only performed. And then, the working efficiency of the tester and the accuracy of the tester for evaluating the testing man-hour can be truly and effectively evaluated by combining the pre-estimated testing man-hour of the tester. The method has the advantages of completely objective statistics and test man-hour, real and effective data, and high accuracy and reliability.
Drawings
FIG. 1 is a flow chart of an automatic test hour statistical method based on associated object operation statistics according to the present invention.
Detailed Description
The present invention will be described in further detail with reference to the following examples. This should not be understood as limiting the scope of the above-described subject matter of the present invention to the following examples. Various substitutions and alterations according to the general knowledge and conventional practice in the art are intended to be included within the scope of the present invention without departing from the technical spirit of the present invention as described above.
As shown in fig. 1, the present invention provides a test man-hour automatic statistical method based on associated object operation statistics, which includes:
A. and establishing an entity element hierarchical tree.
A1. And extracting entity elements contained in the functional modules, the functional components, the code modules and the code lines of the software. Assuming that A, B, C, D, E five entity elements are included in the software, the five entity elements are extracted and stored in the entity element table of the database.
A2. And for A, B, C, D, E five entity elements, establishing an entity element hierarchical tree according to actual semantic affiliation. For example A, B, C, D, E have dependencies from left to right, i.e. E belongs to D, D belongs to C, and so on. Then a is taken as the root node and a 5-level tree from a to E is built.
A3. The entity element hierarchical tree established in step a2 is stored in the entity element hierarchical tree table of the database. If an entity element hierarchical tree taking A as a root node or a child node already exists in the database, and A, B, C, D, E five nodes all exist in the tree and have node dependencies consistent with the tree in the step A2, abandoning the storage and skipping; if there is no entity element hierarchy tree with a as the root node or a child node or there is no entity element hierarchy tree containing the complete A, B, C, D, E five nodes and consistent node dependencies in the database, the newly created tree in step a2 is saved in the table.
B. And establishing a test working hour data table.
And establishing a test working hour data table in the database, wherein the test working hour data table is used for storing the operation working hour data of each entity element by the tester.
The test man-hour data table includes the following fields: primary key ID of the table, entity element ID, tester ID, operation type, operation duration, and operation date.
C. And adding buried points to operations such as creating use cases, editing use cases, executing use cases, creating defects, updating defect states and the like.
C1. On the page of the test case management system, a buried point is added to the page operation control such as a created case, an edited case, an executed case and the like, and a self-study buried point tool such as a JS script and the like or a commercialized buried point tool such as a GrowingIO and the like can be used.
C2. After a tester performs operations such as creating a use case, editing a use case, executing a use case and the like on a test case containing A, B, C, D, E five entity elements, the buried point program sends corresponding operation events to the background program. For example, the tester has performed a create case operation on entity element a for a duration of 5 minutes. After the operation is finished, the embedded point program sends an operation event with an event type of 'create case' to the background program, wherein the operation event comprises data such as entity element ID, tester ID, operation type, operation duration, operation date and the like. After the background program receives the operation event, the data in the event is analyzed, and test man-hour data is generated and stored in a test man-hour data table of the database.
C3. On the page of the defect management system, a buried point is added to page operation controls for creating defects, updating defect states and the like.
C4. After the tester performs operations such as creating defects and updating the defect state on the defects containing A, B, C, D, E five entity elements, the buried point program sends corresponding operation events to the background program. For example, the tester performs a create defect operation on the entity element B for 5 minutes. After the operation is finished, the embedded point program sends an operation event with an event type of 'create defect' to the background program, wherein the operation event comprises data such as entity element ID, tester ID, operation type, operation duration, operation date and the like. After the background program receives the operation event, the data in the event is analyzed, and test man-hour data is generated and stored in a test man-hour data table of the database.
D. And adding buried points on a graphical user interface, a program method and a program function of the software.
D1. The embedded point is added on a graphical user interface of the software, and a self-ground embedded point tool such as a JS script or a commercialized embedded point tool such as GrowingIO can be used.
D2. When a tester clicks a button on a software graphical user interface containing A, B, C, D, E five entity elements, inputs data in an input box and the like, the point burying program sends corresponding operation events to the background program. For example, the tester performs data input operation in the input box on the entity element C, and the duration is 10 seconds. After the operation is finished, the embedded point program sends an operation event with an event type of page function test to the background program, wherein the operation event comprises data such as entity element ID, tester ID, operation type, operation duration, operation date and the like. After the background program receives the operation event, the data in the event is analyzed, and test man-hour data is generated and stored in a test man-hour data table of the database.
D3. The embedded points are added to the program interface, the program method and the program function, and the data of operations such as interface calling, method calling, function calling and the like can be collected by using a self-embedding point tool.
D4. When a tester makes operations such as interface calling, method calling, function calling and the like on code modules such as program interfaces, program methods, program functions and the like which contain A, B, C, D, E five entity elements, the embedded point program sends corresponding operation events to the background program. For example, the tester performs a call interface operation on the entity element D for 1 second. After the operation is finished, the embedded point program sends an operation event with an event type of interface test to the background program, wherein the operation event comprises data such as entity element ID, tester ID, operation type, operation duration, operation date and the like. After the background program receives the operation event, the data in the event is analyzed, and test man-hour data is generated and stored in a test man-hour data table of the database.
E. And establishing a background management system and establishing a page for testing working hour statistics and analysis.
E1. And establishing a background management system and establishing a test working hour statistic and analysis page. The page is provided with two statistical conditions of ID and date of the tester, and the combined statistics can be carried out according to the two statistical conditions.
E2. When the condition of the operation date is selected for data statistics, the background program screens all test working hour data in the corresponding operation date in the test working hour data sheet according to the operation date condition, calculates the total test working hour duration for the grouping condition according to the ID of the tester, returns the result to the page to show the total test working hour duration of all the testers in the date, and can rank in an ascending order or a descending order according to the test working hour duration;
E3. when two conditions of the tester ID and the operation date are selected simultaneously for data statistics, the background program screens all test working hour data of the tester in the operation date in the test working hour data table according to the two conditions of the tester ID and the operation date, calculates the total test working hour duration, and returns a result to the page to display the total test working hour duration of the tester in the date.
F. And establishing an analysis page for testing time estimation accuracy.
F1. Establishing an analysis page of test estimation accuracy in a background management system, wherein the page is provided with two statistical conditions of a software functional module and a project cycle time period, the data of the software functional module is from an entity element hierarchical tree table of a database, the data of the project cycle time period is from a project management tool, and the page acquires estimated test man-hour data of a tester to the software functional module in each project cycle time period from the project management tool and displays the estimated test man-hour data on the page;
F2. when a certain software function module and a project cycle time period of the function module are selected, a background program inquires an entity element hierarchical tree which takes the name of the software function module as a root node in an entity element hierarchical tree table according to the name of the software function module, acquires all child nodes in the tree, traverses each child node, inquires entity element data corresponding to each child node in the entity element table, screens out corresponding entity element ID and all test man-hour data of a creation date in the project cycle time period in a test man-hour data table according to the two data of the entity element ID and the project cycle time period, finally sums up and calculates the total test man-hour time period, and returns a result to a page;
F3. and displaying the pre-estimated testing working hours and the actual testing working hours of the software functional module on a page, and calculating and displaying the pre-estimated accuracy according to the percentage of the actual working hours in the pre-estimated working hours.
Example 1.
Assume that there is now a website that includes functional modules such as "X: home page", "Y: registration page", "Z: shopping cart page", etc. The function module of "registration page Y" needs to be developed with new functions, and includes six entity elements of "a: user name", "B: set password", "C: confirmation password", "D: registration button", "E: userregistterservice", "F: doRegister ()". In the project management tool, the project cycle time period of a function module of 'Y: registration page' is 2020-07-01 to 2020-07-05, and the estimated test working hour of a tester to the 'registration page' is 20 hours.
Firstly, extracting entity elements of software, and generating entity element data and entity element hierarchical tree data.
The software functional module of 'Y: registration page' comprises four functional components of 'A: user name', 'B: setting password', 'C: confirmation password', 'D: registration button', and two program interfaces and program methods of 'E: UserRegisterService', 'F: DoRegister ()'.
b. According to the names of the six functional components, the program interfaces and the program methods, inquiring whether the same entity elements exist in an entity element table of the database, if not, creating new entity elements, storing data in the entity element table, and acquiring the ID of the entity elements; if so, directly acquiring the ID of the entity element. In this example, Y, A, B, C, D, E, F are IDs of seven entity elements such as "Y: registration page", "A: user name", "B: set password", "C: confirmation password", "D: registration button", "E: UserRegisterService", "F: doRegister ()", respectively.
c. And establishing an entity element hierarchical tree for all entity elements according to the actual semantic dependency relationship. In this example, a hierarchy tree of entity elements is established with six entity elements of "Y: registration page" as root node, "A: user name", "B: setting password", "C: confirmation password", "D: registration button", "E: UserRegisterService", "F: dorRegister ()" as child nodes.
d. And c, storing the entity element hierarchical tree established in the step c in an entity element hierarchical tree table of the database. If an entity element hierarchy tree with Y as a root node or a child node already exists in the database, and Y, A, B, C, D, E, F seven nodes exist in the tree and have node dependencies consistent with the tree in the step c, abandoning the storage and skipping; and c, if the entity element hierarchy tree taking Y as a root node or a child node does not exist in the database, or the entity element hierarchy tree containing the complete Y, A, B, C, D, E, F seven nodes and consistent node dependencies does not exist, storing the newly-built tree in the step c in a table.
And secondly, newly building a test man-hour data table in the database, wherein the test man-hour data table is used for storing the operation man-hour data of each entity element by the tester.
a. And establishing a test working hour data table in the database, wherein the test working hour data table is used for storing the operation working hour data of each entity element by the tester.
b. The test man-hour data table includes the following fields: ID. Entity element ID, tester ID, operation type, operation duration and operation date.
And thirdly, adding buried points to operations such as case creation, case editing, case execution, defect creation, defect state updating and the like on pages of the test case management system and the defect management system, and collecting the stay time of the operation of the tester on the entity elements. And after the operation is finished, transmitting the data of the operation type, the operation stay time and the like of the entity element to a background program, and storing the data into a test working hour data table of the database.
a. On the page of the test case management system, a buried point is added to the page operation control such as a created case, an edited case, an executed case and the like, and a self-study buried point tool such as a JS script and the like or a commercialized buried point tool such as a GrowingIO and the like can be used.
b. After a tester (ID is TestUserID1) performs operations such as creating a use case, editing a use case, executing a use case and the like on a test case containing seven entity elements such as Y, A, B, C, D, E, F and the like, the buried point program sends a corresponding operation event to the background program. For example, the tester performs a "create case" operation for a test case containing "A: user name" for a duration of 5 minutes. After the operation is completed, the embedded point program of the test case management system on the case creation page generates an event with an operation type of case creation according to the operation of a tester, and the event comprises data with an entity element ID of A, a tester ID of TestUserID1, an operation type of case creation, an operation duration of 5 minutes, an operation date of the current date and the like. After receiving the operation event, the background program analyzes the data in the event, generates a piece of test man-hour data, and stores the test man-hour data into a test man-hour data table of the database, wherein the data of the test man-hour data table is as shown in table 1:
table 1:
| ID | entity element ID | Tester ID | Type of operation | Duration of operation | Date of operation |
| 1 | A | TestUserID1 | Creating use cases | 300s | 2020-7-2 |
c. Similarly, on the page of the defect management system, a buried point is added to the page operation control for creating a defect, updating a defect state, and the like, and a self-research buried point tool such as a JS script or a commercialized buried point tool such as a growth io can be used.
d. After a tester (ID is TestUserID1) performs operations such as creating a defect and updating a defect state on a defect including seven entity elements such as Y, A, B, C, D, E, F, the buried point program sends a corresponding operation event to the background program. For example, the tester performs a "create defect" operation on "B: set password" for a duration of 5 minutes. After the operation is completed, the defect management system sends an event with an operation type of "create defect" to the background program by the buried point program on the "create defect" page, which includes data with an entity element ID of B, a tester ID of TestUserID1, an operation type of "create defect", an operation duration of 5 minutes, an operation date of the current date, and the like. After receiving the operation event, the background program analyzes the data in the event, generates a piece of test man-hour data, and stores the test man-hour data into a test man-hour data table of the database, wherein the data of the test man-hour data table is as shown in table 2:
table 2:
| ID | entity element ID | Tester ID | Type of operation | Duration of operation | Date of operation |
| 1 | A | TestUserID1 | Creating use cases | 300s | 2020-7-2 |
| 2 | B | TestUserID1 | Creating defects | 300s | 2020-7-2 |
And fourthly, adding buried points on a graphical user interface, a program method and a program function of the software, and collecting the stay time of the testers operating the entity elements such as the functional module, the functional component, the program interface, the program method and the program function of the software. And after the operation is finished, transmitting the data of the operation type, the operation stay time and the like of the entity element to a background program, and storing the data into a test working hour data table of the database.
a. On the 'registration page' of the website, a buried point is added to operation controls such as a 'user name' input box, a 'set password' input box, a 'confirmation password' input box, and a 'registration' button, and a self-buried point tool such as a JS script or a commercialized buried point tool such as a growth io can be used. In this case, the user name input box, the password setting input box, the password confirmation input box, the registration button and the embedded point are added to the page operation controls "user name" input box, "password setting" input box, "password confirmation" input box and "registration" button which correspond to the four entity elements "A: user name", "B: setting password", "C: confirmation password" and "D: registration button", respectively.
b. When a tester (ID is TestUserID2) performs function test on a user name input box, a password setting input box, a password confirmation input box and a registration button on a registration page, the embedded point program sends a corresponding operation event to the background program. For example, the tester performs a function test operation such as text input on a "user name" input box, and the duration is 5 minutes. After the operation is completed, the point burying program on the 'registration page' generates an event with an operation type of 'functional test' according to the operation of the tester, wherein the event comprises data of an entity element ID of A, a tester ID of TestUserID1, an operation type of 'functional test', an operation duration of 5 minutes, an operation date of the current date and the like. After receiving the operation event, the background program analyzes the data in the event, generates a piece of test man-hour data, and stores the test man-hour data into a test man-hour data table of the database, wherein the data of the test man-hour data table is as shown in table 3:
table 3:
| ID | entity element ID | Tester ID | Type of operation | Duration of operation | Date of operation |
| 1 | A | TestUserID1 | Creating use cases | 300s | 2020-7-2 |
| 2 | B | TestUserID1 | Creating defects | 300s | 2020-7-2 |
| 3 | A | TestUserID2 | Functional testing | 300s | 2020-7-2 |
c. The embedded points are added to the program interface, the program method and the program function, and the data of operations such as interface calling, method calling, function calling and the like can be collected by using a self-embedding point tool. In this case, a buried point is added to the program interface userregistervice and the program method doRegister () corresponding to the two entity elements "E: userregistervice" and "F: doRegister ()".
d. The tester (ID is TestUserID2) makes an interface calling operation on the UserRegisterService interface, and the duration is 1 second. After the operation is finished, the embedded point program sends an operation event with an event type of 'interface test' to the background program, and the operation event comprises data of an entity element ID of E, a tester ID of TestUserID1, an operation type of 'interface test', an operation duration of 1 second, an operation date of the current date and the like. After receiving the operation event, the background program analyzes the data in the event, generates a piece of test man-hour data, and stores the test man-hour data into a test man-hour data table of the database, wherein the data of the test man-hour data table is as shown in table 4:
table 4:
| ID | entity element ID | Tester ID | Type of operation | Duration of operation | Date of operation |
| 1 | A | TestUserID1 | Creating use cases | 300s | 2020-7-2 |
| 2 | B | TestUserID1 | Creating defects | 300s | 2020-7-2 |
| 3 | A | TestUserID2 | Functional testing | 300s | 2020-7-2 |
| 4 | E | TestUserID2 | Interface testing | 1s | 2020-7-2 |
And fifthly, establishing a background management system and establishing a test working hour statistic and analysis page. The page shows that each tester counts the total time of the testing working hours of all the entity elements in the working day, and can be ranked in an ascending order or a descending order according to the working hours.
a. And (5) establishing a background management system and establishing a test working hour counting and analyzing page. And counting and analyzing the test working hours, reading data of a test working hour data sheet in the database by the page, and displaying the result on the page after corresponding operation is carried out. The page is provided with two statistical conditions of ID and date of the tester, and the combined statistics can be carried out according to the two statistical conditions.
b. When only a single condition of the date is selected for data statistics, the background program screens all the test working hour data with the operation date equal to the date in the test working hour data table according to the date condition, calculates the total test working hour duration by taking the tester ID as a grouping condition, returns the result to the page, shows the total test working hour duration of all the testers on the date, and can perform ascending or descending ranking according to the test working hour duration. For example, selecting the date "2020-07-02" as a statistical condition, counting, the background program counts all the man-hour data with the operation date "2020-07-02" according to the grouping condition of the tester ID, counting the total time of the testing man-hour, and returning the result to the page for displaying. According to the data of the test man-hour data table obtained in the above steps, the page display result at this time is as shown in table 5:
table 5:
| tester ID | Measuring total duration of working hours | Counting date |
| TestUserID1 | 600s | 2020-7-2 |
| TestUserID2 | 301s | 2020-7-2 |
c. When two conditions of a tester and a date are selected simultaneously to carry out data statistics, the background program screens all the test man-hour data with the tester ID as the selected tester ID and the operation date equal to the date from the test man-hour data table according to the two conditions of the tester and the date, calculates the total test man-hour duration, returns a result to the page, and displays the total test man-hour duration of the tester on the date on the page. For example, when the tester ID is "TestUserID 1" and the date is "2020-07-02" are selected as statistical conditions for statistics, the background program queries all the man-hour data with the tester ID equal to "TestUserID 1" and the operation date equal to "2020-07-02" to calculate the total time length of the test man-hours, and the result is returned to the page for display. According to the data of the test man-hour data table obtained in the above steps, the page display result at this time is as shown in table 6:
table 6:
| tester ID | Measuring total duration of working hours | Counting date |
| TestUserID1 | 600s | 2020-7-2 |
And sixthly, establishing a test time estimation accuracy analysis page in the background management system. And (4) displaying the pre-estimated test working hours and the actual test working hours of the software functional module on the page, and calculating and displaying the pre-estimated accuracy. The estimated testing man-hour data is from the existing data in the project management tool, and the actual testing man-hour is from the testing man-hour data table.
a. And establishing a test time estimation accuracy analysis page in a background management system. The page is provided with two statistical conditions of a software function module and a project period time period, and combined statistics can be carried out according to the two statistical conditions. The data of the software functional module comes from an entity element hierarchical tree table of the database, and is generally a root node of the entity element hierarchical tree data. Project cycle time period data comes from the project management tool. In addition, the page also acquires the data of the estimated testing man-hour of the software functional module by the tester in each project cycle time period from the project management tool, and displays the data on the page. For example, in this case, the software function module is "registration page", and its entity element is "Y: registration page", and an entity element hierarchy tree with Y as a root node can be queried in the entity element hierarchy tree by the entity element ID being Y, and the tree includes A, B, C, D, E, F and other child nodes. All entity elements like Y can be used as query conditions of the functional module of the time estimation accuracy analysis page. The test time estimation accuracy analysis page reads the project cycle time segment data of each functional module from the project management tool as a query condition of the project cycle time segment, for example, for the 'registration page', the number of the project where the page is located is 1, and the project cycle is from '2020 + 0701' to '2020-07-05'. In addition, the test time estimation accuracy analysis page also reads the estimated test time of the functional module from the project management tool to be used as result calculation. In this case, the estimated test man-hour of the "registration page" is 20 hours. The above data are all existing data.
b. After the functional module is used as a registration page and the project cycle time period is from 2020-07-01 to 2020-07-05 is submitted as statistical conditions, the background program queries an entity element hierarchical tree table according to the name of the software functional module, wherein the entity element hierarchical tree table is used for querying the entity element hierarchical tree which takes the registration page as the entity element name and is used as a root node, and all child nodes in the tree are obtained: "A: user name", "B: set password", "C: confirmation password", "D: registration button", "E: UserRegisterService", "F: dorRegister ()". And then traversing each child node, screening all the test working hour data with the entity element ID of A, B, C, D, E, F and the operation date of 2020-07-01 to 2020-07-05 in the test working hour data table according to the two data of each entity element ID and the project period time section, and finally adding to calculate the total time length of the test working hour. The results are returned to the page. The calculation result data at this time are shown in table 7:
table 7:
| functional module | Measuring total duration of working hours |
| Registration page | 901s |
c. The page calculates the ratio of actual test working hours to estimated test working hours according to the calculation result data, converts the ratio into percentage, finally obtains estimated accuracy, and displays the estimated accuracy on the page, wherein the page display result is shown in the table 8:
table 8:
| functional module | Project cycle time period | Pre-estimating test working hour | Actual test man-hour | Prediction accuracy | Counting date |
| Registration page | 2020-07-01--2020-07-05 | 20h | 901s | 1.25% | 2020-07-01 |
Claims (7)
1. A test man-hour automatic statistical method based on associated object operation statistics is characterized by comprising the following steps:
A. extracting entity elements contained in a function module, a function component, a code module and a code line of the software, storing the extracted entity elements in an entity element table of a database, establishing a new entity element hierarchical tree or updating the existing entity element hierarchical tree according to the affiliated relationship of the entity elements, and storing the newly established entity element hierarchical tree or the updated entity element hierarchical tree in the entity element hierarchical tree table of the database;
B. establishing a test working hour data table in a database, and collecting the time consumption of operation of a tester on the software entity elements;
C. adding buried points to operations of creating cases, editing cases, executing cases, creating defects and updating defect states on pages of a test case management system and a defect management system, collecting the stay time of a tester for operating the entity elements, and after the operation is completed, transmitting the operation types and the operation stay time data of the entity elements to a background program and storing the data in a test working hour data table of a database;
D. adding buried points on a graphical user interface, a program method and a program function of the software, and collecting the stay time of a tester operating the functional module, the functional component, the program interface, the program method and the entity element of the program function of the software; after the operation is finished, transmitting the operation type of the entity element and the data of the operation stay time to a background program and storing the data into a test working hour data table of a database;
E. establishing a background management system and establishing a page for testing working hour statistics and analysis; the page shows that each tester counts the total time of the testing man-hour of all the entity elements in the working day;
F. establishing an analysis page of the test estimation accuracy in a background management system, displaying the estimated test working hours and the actual test working hours of the software functional module on the page, and calculating and displaying the estimated accuracy; the estimated testing man-hour data is from the existing data in the project management tool, and the actual testing man-hour is from the testing man-hour data table.
2. The method for automatically counting the test man-hour based on the operation statistics of the associated objects as claimed in claim 1, wherein the step a comprises:
after the entity elements are extracted, establishing an entity element hierarchical tree and storing the entity element hierarchical tree in an entity element hierarchical tree table; the physical element hierarchy tree is updated if it already exists in the physical element hierarchy tree table.
3. The method for automatically counting the test man-hour based on the operation statistics of the associated objects as claimed in claim 1, wherein the step B comprises:
establishing a test man-hour data table in a database, wherein the test man-hour data table comprises the following fields: primary key ID of the table, entity element ID, tester ID, operation type, operation duration, and operation date.
4. The method for automatically counting the test man-hour based on the operation statistics of the associated objects as claimed in claim 1, wherein the step C comprises:
adding buried points to page operation controls for creating a use case, editing the use case and executing the use case on a page of the test case management system; adding a buried point to a page operation control for creating the defect and updating the defect state on a page of the defect management system;
after a tester makes a case creating operation, a case editing operation or a case executing operation on a test case, the embedded point program sends a corresponding operation event to the background program; or after the tester performs operation of creating the defect or updating the defect state on the defect, the embedded point program sends the corresponding operation event to the background program;
after the background program receives the operation event, the data in the event is analyzed, and test working hour data is generated and stored in a test working hour data table of the database.
5. The method for automatically counting the test man-hour based on the operation statistics of the associated objects as claimed in claim 1, wherein the step D comprises:
adding a buried point on a graphical user interface, a program method and a program function of the software, and after a tester operates on the graphical user interface, the program method or the program function of the software, sending a corresponding operation event to a background program by a buried point program;
after the background program receives the operation event, the data in the event is analyzed, and test man-hour data is generated and stored in a test man-hour data table of the database.
6. The method for automatically counting the test man-hour based on the operation statistics of the associated objects as claimed in claim 1, wherein the step E comprises:
establishing a background management system, and establishing a test working hour statistics and analysis page; the page is provided with two statistical conditions of ID of a tester and operation date;
when the condition of the operation date is selected for data statistics, the background program screens all test working hour data in the corresponding operation date in the test working hour data sheet according to the operation date condition, calculates the total test working hour duration for the grouping condition according to the ID of the tester, returns the result to the page to show the total test working hour duration of all testers in the date, and ranks the test working hours in an ascending order or a descending order according to the length of the test working hours;
when two conditions of the tester ID and the operation date are selected simultaneously for data statistics, the background program screens all test working hour data of the tester in the operation date in the test working hour data table according to the two conditions of the tester ID and the operation date, calculates the total test working hour duration, and returns a result to the page to display the total test working hour duration of the tester in the date.
7. The method for automatically counting the test man-hour based on the operation statistics of the associated objects as claimed in claim 1, wherein the step F comprises:
establishing an analysis page of test estimation accuracy in a background management system, wherein the page is provided with two statistical conditions of a software functional module and a project cycle time period, the data of the software functional module is from an entity element hierarchical tree table of a database, the data of the project cycle time period is from a project management tool, and the page acquires estimated test man-hour data of a tester to the software functional module in each project cycle time period from the project management tool and displays the estimated test man-hour data on the page;
when a certain software function module and a project cycle time period of the function module are selected, a background program inquires an entity element hierarchical tree which takes the name of the software function module as a root node in an entity element hierarchical tree table according to the name of the software function module, acquires all child nodes in the tree, traverses each child node, inquires entity element data corresponding to each child node in the entity element table, screens out corresponding entity element ID and all test man-hour data of a creation date in the project cycle time period in a test man-hour data table according to the two data of the entity element ID and the project cycle time period, finally sums up and calculates the total test man-hour time period, and returns a result to a page;
and displaying the pre-estimated testing working hours and the actual testing working hours of the software functional module on a page, and calculating and displaying the pre-estimated accuracy according to the percentage of the actual working hours in the pre-estimated working hours.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011180987.1A CN112000587B (en) | 2020-10-29 | 2020-10-29 | Test man-hour automatic statistical method based on associated object operation statistics |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011180987.1A CN112000587B (en) | 2020-10-29 | 2020-10-29 | Test man-hour automatic statistical method based on associated object operation statistics |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112000587A CN112000587A (en) | 2020-11-27 |
| CN112000587B true CN112000587B (en) | 2021-11-23 |
Family
ID=73475805
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011180987.1A Active CN112000587B (en) | 2020-10-29 | 2020-10-29 | Test man-hour automatic statistical method based on associated object operation statistics |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112000587B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112416807A (en) * | 2020-12-10 | 2021-02-26 | 武汉光庭信息技术股份有限公司 | System and method for analyzing and correlating test case results |
| CN112231196B (en) * | 2020-12-14 | 2021-03-16 | 平安科技（深圳）有限公司 | APP embedded point behavior classification method and device, computer equipment and storage medium |
| CN113076299A (en) * | 2021-04-27 | 2021-07-06 | 山东英信计算机技术有限公司 | Lock time consumption statistical method and device based on operation type |
| CN115617702A (en) * | 2022-12-20 | 2023-01-17 | 中化现代农业有限公司 | Test working hour prediction method and prediction device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018113385A1 (en) * | 2016-12-24 | 2018-06-28 | 上海壹账通金融科技有限公司 | Method and system for dynamically tracking application of client, client, and server |
| CN109271314A (en) * | 2018-08-21 | 2019-01-25 | 郑州云海信息技术有限公司 | A kind of software test personnel performance assessment system and its application method |
| CN110442511A (en) * | 2019-06-25 | 2019-11-12 | 苏宁云计算有限公司 | A test method and device are buried in visualization |
| CN111813697A (en) * | 2020-08-26 | 2020-10-23 | 四川新网银行股份有限公司 | Test coverage rate statistical method based on test object calling mark |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4907237B2 (en) * | 2006-06-22 | 2012-03-28 | 大日本スクリーン製造株式会社 | Test man-hour estimation device and program |
| JP2014092980A (en) * | 2012-11-05 | 2014-05-19 | Fujitsu Ltd | Determination device, determination method, and determination program |
| US10880197B2 (en) * | 2018-07-13 | 2020-12-29 | Keysight Technologies, Inc. | Methods, systems, and computer readable media for testing a network node using source code for programming a packet forwarding plane of the network node |
| CN109634822B (en) * | 2018-11-27 | 2023-04-14 | 平安科技（深圳）有限公司 | Function time consumption statistical method and device, storage medium and terminal equipment |
-
2020
- 2020-10-29 CN CN202011180987.1A patent/CN112000587B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018113385A1 (en) * | 2016-12-24 | 2018-06-28 | 上海壹账通金融科技有限公司 | Method and system for dynamically tracking application of client, client, and server |
| CN109271314A (en) * | 2018-08-21 | 2019-01-25 | 郑州云海信息技术有限公司 | A kind of software test personnel performance assessment system and its application method |
| CN110442511A (en) * | 2019-06-25 | 2019-11-12 | 苏宁云计算有限公司 | A test method and device are buried in visualization |
| CN111813697A (en) * | 2020-08-26 | 2020-10-23 | 四川新网银行股份有限公司 | Test coverage rate statistical method based on test object calling mark |
Non-Patent Citations (1)
| Title |
|---|
| "基于功能点的装备软件成本度量研究";曹杨华 等;《航空财会》;20200315(第2期);第46-49页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112000587A (en) | 2020-11-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112000587B (en) | Test man-hour automatic statistical method based on associated object operation statistics | |
| CN110232024B (en) | Software automation test framework and test method | |
| Nesi et al. | Effort estimation and prediction of object-oriented systems | |
| Fioravanti et al. | Estimation and prediction metrics for adaptive maintenance effort of object-oriented systems | |
| Briand et al. | Modeling development effort in object-oriented systems using design properties | |
| US9354867B2 (en) | System and method for identifying, analyzing and integrating risks associated with source code | |
| KR102356771B1 (en) | Data-driven testing framework | |
| Von Knethen | Change-oriented requirements traceability. Support for evolution of embedded systems | |
| Bianchi et al. | An exploratory case study of the maintenance effectiveness of traceability models | |
| Scott et al. | Practical software process improvement-the IMPACT project | |
| CN115470195A (en) | Index data automatic calculation method and device fusing dimension models | |
| Mockus et al. | On measurement and analysis of software changes | |
| Demeyer et al. | A Pattern Language for Reverse Engineering. | |
| Chen et al. | An empirical study of eServices product UML sizing metrics | |
| CN111813697B (en) | Test coverage rate statistical method based on test object calling mark | |
| Sneed | Impact analysis of maintenance tasks for a distributed object-oriented system | |
| Kanellopoulos et al. | Data mining source code to facilitate program comprehension: experiments on clustering data retrieved from C++ programs | |
| Sabev et al. | Manual to automated testing: An effort-based approach for determining the priority of software test automation | |
| Morozoff | Using a line of code metric to understand software rework | |
| Ratzinger et al. | Quality assessment based on attribute series of software evolution | |
| Hammad et al. | Identifying designers and their design knowledge | |
| Weber et al. | Detecting inconsistencies in multi-view uml models | |
| Pimentel et al. | Application of the independence axiom on the design of object-oriented software using the axiomatic design theory | |
| Munger | A representation-based methodology for developing high-value knowledge engineering systems: Theory and applications | |
| Kumaran et al. | An approach to automatic generation of test cases based on use cases in the requirements phase |
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 |