CN109272225A - A kind of Bug tracing system tester importance ranking method - Google Patents
A kind of Bug tracing system tester importance ranking method Download PDFInfo
- Publication number
- CN109272225A CN109272225A CN201811046244.8A CN201811046244A CN109272225A CN 109272225 A CN109272225 A CN 109272225A CN 201811046244 A CN201811046244 A CN 201811046244A CN 109272225 A CN109272225 A CN 109272225A
- Authority
- CN
- China
- Prior art keywords
- tester
- node
- importance
- bug
- connection
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
- G06Q10/06393—Score-carding, benchmarking or key performance indicator [KPI] analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/105—Human resources
- G06Q10/1053—Employment or hiring
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Educational Administration (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Game Theory and Decision Science (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The present invention provides a kind of Bug tracing system tester importance ranking method, at least includes the following steps: establishing tester's relational network, calculates the weight of each connection；Successive ignition calculates the importance values of each tester until the importance values of each tester restrain；Compare the importance values of each tester, the more big then tester of the importance values is more important.By the present invention in that the tester's importance ranking result obtained with this method is consistent with the real work of tester performance, show that this method has stability by the data set experimental results after random erasure and the selected deletion higher tester of ranking, it therefore can be using this method assessment tester to the contribution degree of test phase, reference frame is provided for the distribution of tester, and then help system administrative staff improve the working efficiency of software test and Bug tracking.
Description
Technical field
The present invention relates to sort method technical fields, specifically, more particularly to a kind of Bug tracing system tester weight
The property wanted sort method.
Background technique
It is increasingly huge with software project scale, how effectively to manage and assign a large amount of Bug report of tester's submission
Accomplish as the problem of software project operation.Presently, there are method in, most of method be Bug is reported itself assessment and
The submitter (tester) that all Bug are reported is thought to have identical by optimization processing for the ease of problem reduction processing
Ability, consciousness and working experience.However in actual items, the ability of the tester of the link, experience and right are participated in
The cognition of software systems may have relatively large difference.Influenced by above-mentioned factor, these testers find Bug ability with
And the subsequent quality for submitting Bug report just has significant gap.Therefore, the factor of tester itself can be in testing process
Different operating efficiency and contribution are embodied, and then different degrees of importance can be generated on the quality of software project to influence.For example,
In software Bug tracing system, an active tester is often big for repairing the percentage contribution that software Bug is made
It contributes in the skilled tester that a quiet developer, one possess test experience for many years often more than one common
Tester.Therefore, quantitative evaluation is carried out to importance of the tester to testing process, tester can be submitted
The prediction of quality of Bug report provides reference, also significant to making smooth advances for software project.
At present to the evaluation of tester's importance mainly according to the statistical indicator to tester's workload, for example submit
The quantity of Bug report, the quantity for being confirmed to be effective Bug report etc..These statistical indicators are to tester to testing process
Contribution have a specific and direct reaction, but these indexs can only often measure tester in testing process body in a certain respect
Existing importance can not fully assess tester to the importance of testing process, and there is not yet integration test link is multi-party
The appropriate weight index in face.On the other hand, it is often had in software project and some focuses on highly difficult task rather than simple work
The accumulative tester of amount, importance can not be measured simply using statistical indicator.
Action behavior of numerous testers in Bug tracing system, including submit Bug report and comment Bug report, body
It is now a kind of behavior of social networks.Submission and comment behavior of the tester in Bug tracing system to Bug report, can be with
The importance being considered as in the social networks.In social networks, in the numerous influence factors propagated information, have compared with
The node of high-impact plays the role of vital.In Bug tracing system, submit the tester of Bug report can be with
The node being considered in social networks, the behavior that tester comments on some Bug report can be considered primary with other nodes
Directed connection, the directed connection between these nodes and node can be conceptualized as social networks, utilize social networks interior joint shadow
Power sort method is rung to assess tester in Bug tracing system and become a kind of feasible method to software test importance.
Summary of the invention
According to technical problem set forth above, and provide a kind of Bug tracing system tester importance ranking method.
The present invention proposes a kind of Bug tracing system tester importance ranking method, which is characterized in that include at least with
Lower step:
S1: it establishes tester's relational network: setting and share N number of node and M directed connection, virtual root node g is set,
Being bi-directionally connected for each node and root node is established, then shares N+1 node and M+2N directed connection in network；
S2: the weight of each connection is calculated；
S3: successive ignition calculates the importance values of each tester until the importance values of each tester restrain；
S4: the importance values of each tester, the more big then tester of the importance values are more important.
Further, in the step S1, according to the correlation for proposing Bug report and comment of tester in the warehouse Bug
Record establishes tester's relational network；
In use, by thering is the N number of tester of the network graph representation of N number of node and M directed connection and M comment to close
System；Virtual root node g is set, establishes being bi-directionally connected for each node and root node, then by N+1 in tester's relational network
A node and M+2N directed connection are constituted.
Further, in the step S2, any two in this tester's relational network are indicated using N+1 dimension matrix W
The connection of node, wherein aijIndicate connection status value；If there are node is to be directed toward node j, a in the networkij=1, i.e.,
Indicate there is connection between node i and j, the weight of the connection is Wij；If connectionless, aij=0；
Weight W in tester's relational network, between nodeijIs defined as:
Wherein, kj inIndicate the in-degree of node j.
Further, in the step S3, the basis of weighting tester's relational network is established according to step S1 and S2, is adopted
The importance of tester is calculated with the method for inclined random walk；Tester's importance are as follows:
Wherein, Si(t) indicate node i the t time calculating when obtain as a result, and Si(0)=1；S simultaneouslyiValue will restrain
In stable result
Method proposed by the present invention can assess tester to the contribution degree of test phase.By the present invention in that with test
The practical work of tester's importance ranking result and tester that personnel's relational network node importance sort method obtains
Make performance to be consistent, passes through the data set experimental results table after random erasure and the selected deletion higher tester of ranking
Bright this method has stability, therefore can be tester using this method assessment tester to the contribution degree of test phase
The distribution of member provides reference frame, and then help system administrative staff improve the working efficiency of software test and Bug tracking.
Detailed description of the invention
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technical description to do simply to introduce, it should be apparent that, the accompanying drawings in the following description is this hair
Bright some embodiments for those of ordinary skill in the art without any creative labor, can be with
It obtains other drawings based on these drawings.
Fig. 1 is overall flow schematic diagram of the invention.
Fig. 2 is a kind of tester's relational network figure of embodiment of the invention according to the report building of Bug_id 47 and 71.
Specific embodiment
In order to enable those skilled in the art to better understand the solution of the present invention, below in conjunction in the embodiment of the present invention
Attached drawing, technical scheme in the embodiment of the invention is clearly and completely described, it is clear that described embodiment is only
The embodiment of a part of the invention, instead of all the embodiments.Based on the embodiments of the present invention, ordinary skill people
The model that the present invention protects all should belong in member's every other embodiment obtained without making creative work
It encloses.
It should be noted that description and claims of this specification and term " first " in above-mentioned attached drawing, "
Two " etc. be to be used to distinguish similar objects, without being used to describe a particular order or precedence order.It should be understood that using in this way
Data be interchangeable under appropriate circumstances, so as to the embodiment of the present invention described herein can in addition to illustrating herein or
Sequence other than those of description is implemented.In addition, term " includes " and " having " and their any deformation, it is intended that cover
Cover it is non-exclusive include, for example, the process, method, system, product or equipment for containing a series of steps or units are not necessarily limited to
Step or unit those of is clearly listed, but may include be not clearly listed or for these process, methods, product
Or other step or units that equipment is intrinsic.
As shown in Figs. 1-2, a kind of Bug tracing system tester importance ranking method, at least includes the following steps:
In the present embodiment, it step S1: establishes tester's relational network: setting and share N number of node and M oriented companies
It connects, virtual root node g is set, establish being bi-directionally connected for each node and root node, then share N+1 node and M+ in network
2N directed connection.
As preferred embodiment, in step S1, reported according to the proposition Bug of tester in the warehouse Bug and comment
Relative recording establish tester's relational network；In use, by there is the network graph representation N of N number of node and M directed connection
A tester and M comment relationship；Virtual root node g is set, establishes being bi-directionally connected for each node and root node, then
It is made of in tester's relational network N+1 node and M+2N directed connection.
As a kind of embodiment of the application, as shown in Fig. 2, before carrying out the calculating of tester's importance, need by
Bug report in information extraction and establish tester's relational network.In the relational network, the role of tester has two
It is a, it is the submitter and commentator of Bug report respectively.Firstly, by submitter and commentator's information extraction in each Bug report.
By taking 71 two Bug reports of bug_id 47 and bug_id as an example, the information of extraction such as table 1.
Submitter and commentator's relationship in 1 Bug of table report
Two Bug report that bug id is 47 as can be seen from Table 1 and bug id is 71 is mentioned by two submitters respectively
It hands over, while each Bug report has been commented on 5 times respectively again.In the two bug reports, there is identical commentator, i.e.,
James_Moody and dj_houghton.The tester's network of personal connections established between two Bug report that bug_id is 47 and 71
Network.
As preferred embodiment, in the assessment of social networks node influence power, the influence power of a node is not only
Depending on the quantity of neighbor node, the influence power of each neighbor node is also depended on.Therefore, in a Bug report, if certain
One commentator has commented on Bug report, then importance of the submitter of Bug report in the relational network also will receive
The influence of the commentator.On the other hand, if a commentator has commented on multiple Bug reports, the importance of the commentator
The submitter for these Bug report that meeting mean effort is commented in him.
Meanwhile in the assessment of social networks node influence power, the influence power of a node depends not only on neighbor node
Quantity, also depend on the influence power of each neighbor node.Therefore, in a Bug report, if some commentator comments on
Bug report, then importance of the submitter of Bug report in the relational network also will receive the shadow of the commentator
It rings.On the other hand, if a commentator has commented on multiple Bug report, the importance of the commentator can mean effort in
The submitter for these Bug report that he comments on.
As shown in Fig. 2, when some tester has commented on the Bug report or comment of another one tester submission
Afterwards, it is believed that a directed connection is produced between the two testers.Jean-michel_ according to table 1
Lemieux has commented on john_arthorne, therefore there are a directed edge in Fig. 1, and direction is from jean-michel_
Lemieux is directed toward john_arthorne.
As preferred embodiment, step S2: the weight of each connection is calculated.In step S2, matrix W is tieed up using N+1
Indicate the connection of any two node in this tester's relational network, wherein aijIndicate connection status value；If the network
In there are node is to be directed toward node j, then aij=1, i.e., there is connection between expression node i and j, the weight of the connection is Wij；If
It is connectionless, then aij=0；
Weight W in tester's relational network, between nodeijIs defined as:
Wherein, kj inIndicate the in-degree of node j.
In the present embodiment, step S3: successive ignition calculates the importance values of each tester until each test
The importance values of personnel restrain.In step S3, the basis of weighting tester's relational network is established according to step S1 and S2, is used
The method of inclined random walk calculates the importance of tester；Tester's importance are as follows:
Wherein, Si(t) indicate node i the t time calculating when obtain as a result, and Si(0)=1；S simultaneouslyiValue will restrain
In stable result
As preferred embodiment, step S4: the importance values of each tester, the importance values
More big then tester is more important.It is to be understood that in other embodiments, can also carry out according to the actual situation other
Setting, with the importance for screening personnel.The serial number of the above embodiments of the invention is only for description, does not represent the excellent of embodiment
It is bad.
In the above embodiment of the invention, it all emphasizes particularly on different fields to the description of each embodiment, does not have in some embodiment
The part of detailed description, reference can be made to the related descriptions of other embodiments.
Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention., rather than its limitations；To the greatest extent
Pipe present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that: its according to
So be possible to modify the technical solutions described in the foregoing embodiments, or to some or all of the technical features into
Row equivalent replacement；And these are modified or replaceed, various embodiments of the present invention technology that it does not separate the essence of the corresponding technical solution
The range of scheme.
Claims (4)
1. a kind of Bug tracing system tester importance ranking method, which is characterized in that at least include the following steps:
S1: tester's relational network is established；If sharing N number of node and M directed connection, virtual root node g is set, is established
Each node and root node are bi-directionally connected, then N+1 node and M+2N directed connection are shared in network；
S2: the weight of each connection is calculated；
S3: successive ignition calculates the importance values of each tester until the importance values of each tester restrain；
S4: the importance values of each tester, the more big then tester of the importance values are more important.
2. a kind of Bug tracing system tester importance ranking method according to claim 1, it is further characterized in that:
In the step S1, is reported according to the proposition Bug of tester in the warehouse Bug and the relative recording of comment establishes tester
Member's relational network；
In use, by having the N number of tester of the network graph representation of N number of node and M directed connection and M comment relationship；
Virtual root node g is set, being bi-directionally connected for each node and root node is established, then by N+1 in tester's relational network
Node and M+2N directed connection are constituted.
3. a kind of Bug tracing system tester's importance based on tester's relational network according to claim 1
Sort method, it is further characterized in that:
In the step S2, the connection feelings of any two node in this tester's relational network are indicated using N+1 dimension matrix W
Condition, wherein aijIndicate connection status value；If there are node is to be directed toward node j, a in the networkij=1, i.e. expression node i and j
Between there is connection, the weight of the connection is Wij；If connectionless, aij=0；
Weight W in tester's relational network, between nodeijIs defined as:
Wherein, kj inIndicate the in-degree of node j.
4. a kind of Bug tracing system tester importance ranking method according to claim 1, it is characterised in that:
In the step S3, the basis of weighting tester's relational network is established according to step S1 and S2, using inclined random walk
Method calculate tester importance；Tester's importance are as follows:
Wherein, Si(t) indicate node i the t time calculating when obtain as a result, and Si(0)=1；S simultaneouslyiValue will converge on surely
Fixed resultI=1,2,, N, N+1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811046244.8A CN109272225A (en) | 2018-09-07 | 2018-09-07 | A kind of Bug tracing system tester importance ranking method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811046244.8A CN109272225A (en) | 2018-09-07 | 2018-09-07 | A kind of Bug tracing system tester importance ranking method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109272225A true CN109272225A (en) | 2019-01-25 |
Family
ID=65188161
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811046244.8A Pending CN109272225A (en) | 2018-09-07 | 2018-09-07 | A kind of Bug tracing system tester importance ranking method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109272225A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104092567A (en) * | 2014-06-26 | 2014-10-08 | 华为技术有限公司 | Method and device for confirming influence sequencing of users |
| CN105630800A (en) * | 2014-10-29 | 2016-06-01 | 杭州师范大学 | Node importance ranking method and system |
| CN107862617A (en) * | 2017-10-20 | 2018-03-30 | 江苏大学 | A kind of microblogging community division method based on user's comprehensive similarity |
| CN108009710A (en) * | 2017-11-19 | 2018-05-08 | 国家计算机网络与信息安全管理中心 | Node test importance appraisal procedure based on similarity and TrustRank algorithms |
| CN108428044A (en) * | 2018-02-02 | 2018-08-21 | 浙江工业大学 | A kind of employee's importance ranking method based on network |
-
2018
- 2018-09-07 CN CN201811046244.8A patent/CN109272225A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104092567A (en) * | 2014-06-26 | 2014-10-08 | 华为技术有限公司 | Method and device for confirming influence sequencing of users |
| CN105630800A (en) * | 2014-10-29 | 2016-06-01 | 杭州师范大学 | Node importance ranking method and system |
| CN107862617A (en) * | 2017-10-20 | 2018-03-30 | 江苏大学 | A kind of microblogging community division method based on user's comprehensive similarity |
| CN108009710A (en) * | 2017-11-19 | 2018-05-08 | 国家计算机网络与信息安全管理中心 | Node test importance appraisal procedure based on similarity and TrustRank algorithms |
| CN108428044A (en) * | 2018-02-02 | 2018-08-21 | 浙江工业大学 | A kind of employee's importance ranking method based on network |
Non-Patent Citations (1)
| Title |
|---|
| 任晓龙: ""网络重要节点排序方法综述"", 《科学通报》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Meneely et al. | Predicting failures with developer networks and social network analysis | |
| Surian et al. | Mining collaboration patterns from a large developer network | |
| CN110417011B (en) | Online dynamic security assessment method based on mutual information and iterative random forest | |
| CN110489898B (en) | Dynamic multi-level system modeling and state prediction method based on hybrid cognition | |
| Delgado | Social conflict analysis on a mining project using shannon entropy | |
| Jumarni et al. | An integration of fuzzy TOPSIS and fuzzy logic for multi-criteria decision making problems | |
| Perisic et al. | A computational study of the effect of experience on problem/solution space exploration in teams | |
| Yan et al. | Scheduling post-disaster power system repair with incomplete failure information: A learning-to-rank approach | |
| Levitin et al. | Optimal spot-checking for collusion tolerance in computer grids | |
| Zavala-Alcívar et al. | Supply chain resilience: a conceptual evolution analysis | |
| Halappanavar et al. | Towards efficient nx contingency selection using group betweenness centrality | |
| Liaqat et al. | A majority voting goal based technique for requirement prioritization | |
| Singh et al. | Predicting testing effort using artificial neural network | |
| Zhang et al. | Service composition based on discrete particle swarm optimization in military organization cloud cooperation | |
| Alweshah et al. | Evolution of software reliability growth models: a comparison of auto-regression and genetic programming models | |
| CN109272225A (en) | A kind of Bug tracing system tester importance ranking method | |
| US12021680B1 (en) | Detecting and mitigating cascading errors in a network to improve network resilience | |
| Bowes et al. | Different classifiers find different defects although with different level of consistency | |
| CN107147520B (en) | Network mining method for terrorist organization | |
| Sultornsanee et al. | Phase synchronization approach to construction and analysis of stock correlation network | |
| Scheinert et al. | The shape of watershed governance: Locating the boundaries of multiplex networks | |
| Betancourt-Vázquez et al. | Modeling and analyzing non-functional requirements interdependencies with neutrosofic logic | |
| Li et al. | Sgvcut: a vertex-cut partitioning tool for random walks-based computations over social network graphs | |
| Lee et al. | Software reliability prediction for open source software adoption systems based on early lifecycle measurements | |
| CN112948469A (en) | Data mining method and device, computer equipment and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190125 |