Suche senden
Hochladen
Characterizing and Predicting Which Bugs Get Reopened
âą
1 gefÀllt mir
âą
2,002 views
Thomas Zimmermann
Folgen
Presented at ICSE 2012 in Zurich.
Weniger lesen
Mehr lesen
Technologie
Business
Melden
Teilen
Melden
Teilen
1 von 32
Empfohlen
Predicting Method Crashes with Bytecode Operations
Predicting Method Crashes with Bytecode Operations
Thomas Zimmermann
Â
Analytics for smarter software development
Analytics for smarter software development
Thomas Zimmermann
Â
Design for Testability: A Tutorial for Devs and Testers
Design for Testability: A Tutorial for Devs and Testers
TechWell
Â
Design for Testability: A Tutorial for Devs and Testers
Design for Testability: A Tutorial for Devs and Testers
TechWell
Â
Web Application Remediation - OWASP San Antonio March 2007
Web Application Remediation - OWASP San Antonio March 2007
Denim Group
Â
Peter Zimmerer - Evolve Design For Testability To The Next Level - EuroSTAR 2012
Peter Zimmerer - Evolve Design For Testability To The Next Level - EuroSTAR 2012
TEST Huddle
Â
Software Design for Testability
Software Design for Testability
amr0mt
Â
Defect effort prediction models in software
Defect effort prediction models in software
IAEME Publication
Â
Empfohlen
Predicting Method Crashes with Bytecode Operations
Predicting Method Crashes with Bytecode Operations
Thomas Zimmermann
Â
Analytics for smarter software development
Analytics for smarter software development
Thomas Zimmermann
Â
Design for Testability: A Tutorial for Devs and Testers
Design for Testability: A Tutorial for Devs and Testers
TechWell
Â
Design for Testability: A Tutorial for Devs and Testers
Design for Testability: A Tutorial for Devs and Testers
TechWell
Â
Web Application Remediation - OWASP San Antonio March 2007
Web Application Remediation - OWASP San Antonio March 2007
Denim Group
Â
Peter Zimmerer - Evolve Design For Testability To The Next Level - EuroSTAR 2012
Peter Zimmerer - Evolve Design For Testability To The Next Level - EuroSTAR 2012
TEST Huddle
Â
Software Design for Testability
Software Design for Testability
amr0mt
Â
Defect effort prediction models in software
Defect effort prediction models in software
IAEME Publication
Â
Software testability slide share
Software testability slide share
BeBo Technology
Â
AV-Comparatives Performance Test
AV-Comparatives Performance Test
Herbert Rodriguez
Â
SW Engineering Management
SW Engineering Management
Robert Sayegh
Â
Dtl 2012 kl-app_ctl1.2
Dtl 2012 kl-app_ctl1.2
ĐĐŸĐŒŃŃ Đ€Đ°ĐčĐșĐČŃĐ”
Â
Protecting Enterprise - An examination of bugs, major vulnerabilities and exp...
Protecting Enterprise - An examination of bugs, major vulnerabilities and exp...
ESET Middle East
Â
Bill of-rights-white-paper-final-012312
Bill of-rights-white-paper-final-012312
Cristiano Caetano
Â
Alm 4 Azure with screenshots
Alm 4 Azure with screenshots
Clemens Reijnen
Â
Online exa-syste
Online exa-syste
Anand Bavarava
Â
Soffront Defect tracking
Soffront Defect tracking
Soffront Software
Â
Automatic Proactive Troubleshooting with IBM Rational Build Forge
Automatic Proactive Troubleshooting with IBM Rational Build Forge
Bill Duncan
Â
Cross-project defect prediction
Cross-project defect prediction
Thomas Zimmermann
Â
Magenic-White-Paper-Continuous-Inegration-for-QA-Teams
Magenic-White-Paper-Continuous-Inegration-for-QA-Teams
Aaron Humerickhouse
Â
RSA 2015 Blending the Automated and the Manual: Making Application Vulnerabil...
RSA 2015 Blending the Automated and the Manual: Making Application Vulnerabil...
Denim Group
Â
Software Testing Basics
Software Testing Basics
sachinmistry786
Â
Open Source tools in Continuous Integration environment (case study for agil...
Open Source tools in Continuous Integration environment (case study for agil...
suwalki24.pl
Â
San Jose Selenium Meetup 22 Mar 2012: The Restless Are Getting Native
San Jose Selenium Meetup 22 Mar 2012: The Restless Are Getting Native
Dante Briones
Â
Real Cost of Software Remediation
Real Cost of Software Remediation
Denim Group
Â
Attacking antivirus
Attacking antivirus
UltraUploader
Â
Quality Assurance 1: Why Quality Matters
Quality Assurance 1: Why Quality Matters
Marc Miquel
Â
Not my bug! Reasons for software bug report reassignments
Not my bug! Reasons for software bug report reassignments
Thomas Zimmermann
Â
Characterizing and predicting which bugs get fixed
Characterizing and predicting which bugs get fixed
Thomas Zimmermann
Â
Bug Advocacy
Bug Advocacy
nazeer pasha
Â
Weitere Àhnliche Inhalte
Was ist angesagt?
Software testability slide share
Software testability slide share
BeBo Technology
Â
AV-Comparatives Performance Test
AV-Comparatives Performance Test
Herbert Rodriguez
Â
SW Engineering Management
SW Engineering Management
Robert Sayegh
Â
Dtl 2012 kl-app_ctl1.2
Dtl 2012 kl-app_ctl1.2
ĐĐŸĐŒŃŃ Đ€Đ°ĐčĐșĐČŃĐ”
Â
Protecting Enterprise - An examination of bugs, major vulnerabilities and exp...
Protecting Enterprise - An examination of bugs, major vulnerabilities and exp...
ESET Middle East
Â
Bill of-rights-white-paper-final-012312
Bill of-rights-white-paper-final-012312
Cristiano Caetano
Â
Alm 4 Azure with screenshots
Alm 4 Azure with screenshots
Clemens Reijnen
Â
Online exa-syste
Online exa-syste
Anand Bavarava
Â
Soffront Defect tracking
Soffront Defect tracking
Soffront Software
Â
Automatic Proactive Troubleshooting with IBM Rational Build Forge
Automatic Proactive Troubleshooting with IBM Rational Build Forge
Bill Duncan
Â
Cross-project defect prediction
Cross-project defect prediction
Thomas Zimmermann
Â
Magenic-White-Paper-Continuous-Inegration-for-QA-Teams
Magenic-White-Paper-Continuous-Inegration-for-QA-Teams
Aaron Humerickhouse
Â
RSA 2015 Blending the Automated and the Manual: Making Application Vulnerabil...
RSA 2015 Blending the Automated and the Manual: Making Application Vulnerabil...
Denim Group
Â
Software Testing Basics
Software Testing Basics
sachinmistry786
Â
Open Source tools in Continuous Integration environment (case study for agil...
Open Source tools in Continuous Integration environment (case study for agil...
suwalki24.pl
Â
San Jose Selenium Meetup 22 Mar 2012: The Restless Are Getting Native
San Jose Selenium Meetup 22 Mar 2012: The Restless Are Getting Native
Dante Briones
Â
Real Cost of Software Remediation
Real Cost of Software Remediation
Denim Group
Â
Attacking antivirus
Attacking antivirus
UltraUploader
Â
Quality Assurance 1: Why Quality Matters
Quality Assurance 1: Why Quality Matters
Marc Miquel
Â
Was ist angesagt?
(19)
Software testability slide share
Software testability slide share
Â
AV-Comparatives Performance Test
AV-Comparatives Performance Test
Â
SW Engineering Management
SW Engineering Management
Â
Dtl 2012 kl-app_ctl1.2
Dtl 2012 kl-app_ctl1.2
Â
Protecting Enterprise - An examination of bugs, major vulnerabilities and exp...
Protecting Enterprise - An examination of bugs, major vulnerabilities and exp...
Â
Bill of-rights-white-paper-final-012312
Bill of-rights-white-paper-final-012312
Â
Alm 4 Azure with screenshots
Alm 4 Azure with screenshots
Â
Online exa-syste
Online exa-syste
Â
Soffront Defect tracking
Soffront Defect tracking
Â
Automatic Proactive Troubleshooting with IBM Rational Build Forge
Automatic Proactive Troubleshooting with IBM Rational Build Forge
Â
Cross-project defect prediction
Cross-project defect prediction
Â
Magenic-White-Paper-Continuous-Inegration-for-QA-Teams
Magenic-White-Paper-Continuous-Inegration-for-QA-Teams
Â
RSA 2015 Blending the Automated and the Manual: Making Application Vulnerabil...
RSA 2015 Blending the Automated and the Manual: Making Application Vulnerabil...
Â
Software Testing Basics
Software Testing Basics
Â
Open Source tools in Continuous Integration environment (case study for agil...
Open Source tools in Continuous Integration environment (case study for agil...
Â
San Jose Selenium Meetup 22 Mar 2012: The Restless Are Getting Native
San Jose Selenium Meetup 22 Mar 2012: The Restless Are Getting Native
Â
Real Cost of Software Remediation
Real Cost of Software Remediation
Â
Attacking antivirus
Attacking antivirus
Â
Quality Assurance 1: Why Quality Matters
Quality Assurance 1: Why Quality Matters
Â
Ăhnlich wie Characterizing and Predicting Which Bugs Get Reopened
Not my bug! Reasons for software bug report reassignments
Not my bug! Reasons for software bug report reassignments
Thomas Zimmermann
Â
Characterizing and predicting which bugs get fixed
Characterizing and predicting which bugs get fixed
Thomas Zimmermann
Â
Bug Advocacy
Bug Advocacy
nazeer pasha
Â
Bug best practice
Bug best practice
gaoliang641
Â
Classic Testing Mistakes 0226
Classic Testing Mistakes 0226
MBA_Community
Â
Improving developer tester collaboration with microsoft visual studio 2010
Improving developer tester collaboration with microsoft visual studio 2010
Mohamed Samy
Â
10 Reasons Why You Fix Bugs As Soon As You Find Them
10 Reasons Why You Fix Bugs As Soon As You Find Them
Rosie Sherry
Â
DevOps - Continuous Integration, Continuous Delivery - let's talk
DevOps - Continuous Integration, Continuous Delivery - let's talk
D Z
Â
bug-advocacy
bug-advocacy
KALYAN Chakravarthy
Â
5-Ways-to-Revolutionize-Your-Software-Testing
5-Ways-to-Revolutionize-Your-Software-Testing
Mary Clemons
Â
assertYourself - Breaking the Theories and Assumptions of Unit Testing in Flex
assertYourself - Breaking the Theories and Assumptions of Unit Testing in Flex
michael.labriola
Â
Debugging
Debugging
Jonathan Holloway
Â
Continuous integration
Continuous integration
Boris Dominic
Â
How to Reproduce a Non Reproducible Bug
How to Reproduce a Non Reproducible Bug
BugRaptors
Â
midterm_fa08.pdf
midterm_fa08.pdf
RavinderKSingla
Â
Quality of Bug Reports in Open Source
Quality of Bug Reports in Open Source
Thomas Zimmermann
Â
Software engineering 22 error detection and debugging
Software engineering 22 error detection and debugging
Vaibhav Khanna
Â
179 black-box-software-testing-copyright-2003-cem-kaner1652
179 black-box-software-testing-copyright-2003-cem-kaner1652
ngothanhtungth
Â
Agile testing overview
Agile testing overview
raianup
Â
Agile testingoverview
Agile testingoverview
Rangabashyam S
Â
Ăhnlich wie Characterizing and Predicting Which Bugs Get Reopened
(20)
Not my bug! Reasons for software bug report reassignments
Not my bug! Reasons for software bug report reassignments
Â
Characterizing and predicting which bugs get fixed
Characterizing and predicting which bugs get fixed
Â
Bug Advocacy
Bug Advocacy
Â
Bug best practice
Bug best practice
Â
Classic Testing Mistakes 0226
Classic Testing Mistakes 0226
Â
Improving developer tester collaboration with microsoft visual studio 2010
Improving developer tester collaboration with microsoft visual studio 2010
Â
10 Reasons Why You Fix Bugs As Soon As You Find Them
10 Reasons Why You Fix Bugs As Soon As You Find Them
Â
DevOps - Continuous Integration, Continuous Delivery - let's talk
DevOps - Continuous Integration, Continuous Delivery - let's talk
Â
bug-advocacy
bug-advocacy
Â
5-Ways-to-Revolutionize-Your-Software-Testing
5-Ways-to-Revolutionize-Your-Software-Testing
Â
assertYourself - Breaking the Theories and Assumptions of Unit Testing in Flex
assertYourself - Breaking the Theories and Assumptions of Unit Testing in Flex
Â
Debugging
Debugging
Â
Continuous integration
Continuous integration
Â
How to Reproduce a Non Reproducible Bug
How to Reproduce a Non Reproducible Bug
Â
midterm_fa08.pdf
midterm_fa08.pdf
Â
Quality of Bug Reports in Open Source
Quality of Bug Reports in Open Source
Â
Software engineering 22 error detection and debugging
Software engineering 22 error detection and debugging
Â
179 black-box-software-testing-copyright-2003-cem-kaner1652
179 black-box-software-testing-copyright-2003-cem-kaner1652
Â
Agile testing overview
Agile testing overview
Â
Agile testingoverview
Agile testingoverview
Â
Mehr von Thomas Zimmermann
Software Analytics = Sharing Information
Software Analytics = Sharing Information
Thomas Zimmermann
Â
MSR 2013 Preview
MSR 2013 Preview
Thomas Zimmermann
Â
Klingon Countdown Timer
Klingon Countdown Timer
Thomas Zimmermann
Â
Data driven games user research
Data driven games user research
Thomas Zimmermann
Â
Empirical Software Engineering at Microsoft Research
Empirical Software Engineering at Microsoft Research
Thomas Zimmermann
Â
Security trend analysis with CVE topic models
Security trend analysis with CVE topic models
Thomas Zimmermann
Â
Analytics for software development
Analytics for software development
Thomas Zimmermann
Â
Changes and Bugs: Mining and Predicting Development Activities
Changes and Bugs: Mining and Predicting Development Activities
Thomas Zimmermann
Â
Changes and Bugs: Mining and Predicting Development Activities
Changes and Bugs: Mining and Predicting Development Activities
Thomas Zimmermann
Â
Predicting Defects using Network Analysis on Dependency Graphs
Predicting Defects using Network Analysis on Dependency Graphs
Thomas Zimmermann
Â
Meet Tom and his Fish
Meet Tom and his Fish
Thomas Zimmermann
Â
Predicting Subsystem Defects using Dependency Graph Complexities
Predicting Subsystem Defects using Dependency Graph Complexities
Thomas Zimmermann
Â
Got Myth? Myths in Software Engineering
Got Myth? Myths in Software Engineering
Thomas Zimmermann
Â
Mining Workspace Updates in CVS
Mining Workspace Updates in CVS
Thomas Zimmermann
Â
Mining Software Archives to Support Software Development
Mining Software Archives to Support Software Development
Thomas Zimmermann
Â
Unit testing with JUnit
Unit testing with JUnit
Thomas Zimmermann
Â
esolang: Esoterische Programmiersprachen
esolang: Esoterische Programmiersprachen
Thomas Zimmermann
Â
TA-RE: An Exchange Language for Mining Software Repositories
TA-RE: An Exchange Language for Mining Software Repositories
Thomas Zimmermann
Â
Fine-grained Processing of CVS Archives with APFEL
Fine-grained Processing of CVS Archives with APFEL
Thomas Zimmermann
Â
DynaMine: Finding Common Error Patterns by Mining Software Revision Histories
DynaMine: Finding Common Error Patterns by Mining Software Revision Histories
Thomas Zimmermann
Â
Mehr von Thomas Zimmermann
(20)
Software Analytics = Sharing Information
Software Analytics = Sharing Information
Â
MSR 2013 Preview
MSR 2013 Preview
Â
Klingon Countdown Timer
Klingon Countdown Timer
Â
Data driven games user research
Data driven games user research
Â
Empirical Software Engineering at Microsoft Research
Empirical Software Engineering at Microsoft Research
Â
Security trend analysis with CVE topic models
Security trend analysis with CVE topic models
Â
Analytics for software development
Analytics for software development
Â
Changes and Bugs: Mining and Predicting Development Activities
Changes and Bugs: Mining and Predicting Development Activities
Â
Changes and Bugs: Mining and Predicting Development Activities
Changes and Bugs: Mining and Predicting Development Activities
Â
Predicting Defects using Network Analysis on Dependency Graphs
Predicting Defects using Network Analysis on Dependency Graphs
Â
Meet Tom and his Fish
Meet Tom and his Fish
Â
Predicting Subsystem Defects using Dependency Graph Complexities
Predicting Subsystem Defects using Dependency Graph Complexities
Â
Got Myth? Myths in Software Engineering
Got Myth? Myths in Software Engineering
Â
Mining Workspace Updates in CVS
Mining Workspace Updates in CVS
Â
Mining Software Archives to Support Software Development
Mining Software Archives to Support Software Development
Â
Unit testing with JUnit
Unit testing with JUnit
Â
esolang: Esoterische Programmiersprachen
esolang: Esoterische Programmiersprachen
Â
TA-RE: An Exchange Language for Mining Software Repositories
TA-RE: An Exchange Language for Mining Software Repositories
Â
Fine-grained Processing of CVS Archives with APFEL
Fine-grained Processing of CVS Archives with APFEL
Â
DynaMine: Finding Common Error Patterns by Mining Software Revision Histories
DynaMine: Finding Common Error Patterns by Mining Software Revision Histories
Â
KĂŒrzlich hochgeladen
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
Delhi Call girls
Â
CNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of Service
giselly40
Â
The Codex of Business Writing Software for Real-World Solutions 2.pptx
The Codex of Business Writing Software for Real-World Solutions 2.pptx
Malak Abu Hammad
Â
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
The Digital Insurer
Â
Boost PC performance: How more available memory can improve productivity
Boost PC performance: How more available memory can improve productivity
Principled Technologies
Â
Partners Life - Insurer Innovation Award 2024
Partners Life - Insurer Innovation Award 2024
The Digital Insurer
Â
GenCyber Cyber Security Day Presentation
GenCyber Cyber Security Day Presentation
Michael W. Hawkins
Â
Salesforce Community Group Quito, Salesforce 101
Salesforce Community Group Quito, Salesforce 101
Paola De la Torre
Â
TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
TrustArc
Â
2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...
Martijn de Jong
Â
Histor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slide
vu2urc
Â
Handwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed texts
Maria Levchenko
Â
đŹ The future of MySQL is Postgres đ
đŹ The future of MySQL is Postgres đ
RTylerCroy
Â
08448380779 Call Girls In Greater Kailash - I Women Seeking Men
08448380779 Call Girls In Greater Kailash - I Women Seeking Men
Delhi Call girls
Â
08448380779 Call Girls In Civil Lines Women Seeking Men
08448380779 Call Girls In Civil Lines Women Seeking Men
Delhi Call girls
Â
Driving Behavioral Change for Information Management through Data-Driven Gree...
Driving Behavioral Change for Information Management through Data-Driven Gree...
Enterprise Knowledge
Â
The 7 Things I Know About Cyber Security After 25 Years | April 2024
The 7 Things I Know About Cyber Security After 25 Years | April 2024
Rafal Los
Â
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
ThousandEyes
Â
Unblocking The Main Thread Solving ANRs and Frozen Frames
Unblocking The Main Thread Solving ANRs and Frozen Frames
Sinan KOZAK
Â
Kalyanpur ) Call Girls in Lucknow Finest Escorts Service đž 8923113531 đ° Avail...
Kalyanpur ) Call Girls in Lucknow Finest Escorts Service đž 8923113531 đ° Avail...
gurkirankumar98700
Â
KĂŒrzlich hochgeladen
(20)
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
Â
CNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of Service
Â
The Codex of Business Writing Software for Real-World Solutions 2.pptx
The Codex of Business Writing Software for Real-World Solutions 2.pptx
Â
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
Â
Boost PC performance: How more available memory can improve productivity
Boost PC performance: How more available memory can improve productivity
Â
Partners Life - Insurer Innovation Award 2024
Partners Life - Insurer Innovation Award 2024
Â
GenCyber Cyber Security Day Presentation
GenCyber Cyber Security Day Presentation
Â
Salesforce Community Group Quito, Salesforce 101
Salesforce Community Group Quito, Salesforce 101
Â
TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
TrustArc Webinar - Stay Ahead of US State Data Privacy Law Developments
Â
2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...
Â
Histor y of HAM Radio presentation slide
Histor y of HAM Radio presentation slide
Â
Handwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed texts
Â
đŹ The future of MySQL is Postgres đ
đŹ The future of MySQL is Postgres đ
Â
08448380779 Call Girls In Greater Kailash - I Women Seeking Men
08448380779 Call Girls In Greater Kailash - I Women Seeking Men
Â
08448380779 Call Girls In Civil Lines Women Seeking Men
08448380779 Call Girls In Civil Lines Women Seeking Men
Â
Driving Behavioral Change for Information Management through Data-Driven Gree...
Driving Behavioral Change for Information Management through Data-Driven Gree...
Â
The 7 Things I Know About Cyber Security After 25 Years | April 2024
The 7 Things I Know About Cyber Security After 25 Years | April 2024
Â
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
Â
Unblocking The Main Thread Solving ANRs and Frozen Frames
Unblocking The Main Thread Solving ANRs and Frozen Frames
Â
Kalyanpur ) Call Girls in Lucknow Finest Escorts Service đž 8923113531 đ° Avail...
Kalyanpur ) Call Girls in Lucknow Finest Escorts Service đž 8923113531 đ° Avail...
Â
Characterizing and Predicting Which Bugs Get Reopened
1.
Characterizing and Predicting
Which Bugs Get Reopened Thomas Zimmermann Nachiappan Nagappan Microsoft Research Philip J. Guo Stanford University Brendan Murphy Microsoft Research © Microsoft Corporation
2.
A bugâs life Picture
on the right via http://www.bugzilla.org/docs/2.18/html/lifecycle.html © Microsoft Corporation
3.
Final part of
a trilogy⊠Which bugs are fixed? Bug reassignments Bug reopens (this paper) ICSE 2010 CSCW 2011 ICSE 2012 SEIP © Microsoft Corporation
4.
âŠand partly a
remake Emad Shihab, Akinori Ihara, Yasutaka Kamei, Walid M. Ibrahim, Masao Ohira, Bram Adams, Ahmed E. Hassan, Ken-ichi Matsumoto: Predicting Re-opened Bugs: A Case Study on the Eclipse Project. WCRE 2010: 249-258 © Microsoft Corporation
5.
Shihab et. al:
Predicting Reopened Bugs This paper: Characterizing Reopened Bugs (WCRE 2010) Four dimensions: work habits, bug report, bug fix and team Predicted reopened bugs with a precision of 62.9% and a recall of 84.5% (d-trees) Top node analysis found that bug report dimension was most influential | © Microsoft Corporation
6.
Shihab et. al:
Predicting Reopened Bugs This paper: Characterizing Reopened Bugs (WCRE 2010) Four dimensions: work habits, bug report, Partial replication of Shihab et al. bug fix and team New measurements: organizational and Predicted reopened bugs with a precision geographic distance, reputation, how found of 62.9% and a recall of 84.5% (d-trees) Qualitative component on the causes of Top node analysis found that bug report bug reopens (identified with a survey) dimension was most influential Descriptive models (logistic regression) | | © Microsoft Corporation
7.
Methodology
Qualitative âą âIn your experience, what are reasons why a bug would be reopened multiple timesâ survey âą 358 out of 1,773 responded. Card sort. Quantitative âą All bug reports for Windows Vista and Windows 7 analysis âą Logistic regression model for reopened bugs Manual âą Random sample of reopened bugs inspection âą 20 bug reports © Microsoft Corporation
8.
What are reasons
for bug report reopens? © Microsoft Corporation
9.
Causes of bug
reopens Not FIXED Related to Root Cause ï Bugs difficult to reproduce ï Developers misunderstood root cause ï Bug had insufficient information Related to Priority ï Priority of the bug increased FIXED ï Regression bugs Process-related ï Process © Microsoft Corporation
10.
#1: Difficult to
reproduce âThe bug is hard to reproduce and so the fix was made without being able to fully verify it. A good example is a customer who reports something. We think we see the issue in house and fix that. It turns out we saw something differentâŠâ âBugs which are difficult to reproduce generally get re-activated multiple times. At first, developers will give a simple repro attempt before resolving bugs 'Not repro'. But if the bug opener is able to reproduce the issue again, or perhaps comes up with better repro instructions, then the developer will pay more attention the second time the bug is activated.â âHeisenbugsâ © Microsoft Corporation
11.
#2: Misunderstood root
cause âThe bug is tracking an unidentified symptom and it takes a while to fully root cause. This comes up a lot with memory leaks: there will be an unknown memory leak in a component and the owning team plays whack-a-mole with the code defects to remove memory issues one-by-one.â âNot fixing the root cause and only addressing symptoms. Without root cause understood for the bug a patch/hack can often be done that will then be reactivated.â © Microsoft Corporation
12.
#3: Insufficient information
âPoor bug quality. If the bug wasn't described well enough, or not enough diagnostic info was there, the dev will guess and fix *something* in order to make the bug go away. What they fix isn't always what the person who filed the bug ran into.â âIf a bug report does not accurately convey enough information about what is actually wrong (i.e. it describes incorrect behavior but neglects to mention data loss) or if the bug does not convey a dependency (such as another team relying on a fix), a bug may be de-prioritized and resolved without fixing.â © Microsoft Corporation
13.
#4: Increased priority
âBugs are closed because one person or triage team believes the bug is not worthy of fixing (i.e. too risky, don't care, etc.), but then a few days later a VP or external customer reports the same issue, then the bug has a higher priority.â âOther reason is lack of business justification or too late in product cycle; reopened when sufficient justification exists or new cycle begins.â âOne team may feel an issue is critical while the other does not see it as important enough, and instead of carrying a discussion, the bug is bounced around.â © Microsoft Corporation
14.
#5: Regression bugs
âFirst attempt at fix was flawed in some way, and wasn't caught because of lack of testing or unknown related scenario regression.â âI've seen cases in the past where it was thought that a bug was fixed only to find that a corner case had been missed.â âI've also seen cases where the bug was only being hit due to a timing issue and something changed that affected the timing and the bug disappeared again.â © Microsoft Corporation
15.
#6: Process-related bugs
âSometimes bugs are reopened due to a misunderstanding of process. e.g. dev resolves bug when fix is submitted, but tester reactivates because bug still repros (because fix has not yet reached tester).â âBug is verified fixed in a feature of developerâs branch and the fix takes too long to hit the main branch.â © Microsoft Corporation
16.
#6: Process-related bugs
âFirst of all, I donât like the model where we reactivate bugs that were Fixed but the issue was not resolved. Logically it makes sense, but tracking the thread of the issue through multiple checkins & reactivates can be hell if it happens more than once or twice. I would prefer a model where once a checkin has been made for a bug, that bug is done! New issues, or issues that linger despite a previous fix, should/ would be tracked in a new bug.â © Microsoft Corporation
17.
What factors
correlate with bug reopens? © Microsoft Corporation
18.
Does the source
of a bug (how it was found) influence the likelihood of bug reopens? Bug Sources Vista Win7 Reopen rate for all bugs P Q Code analysis tools 0.52ïP 0.73ïQ less likely to be reopened Human review 0.85ïP 0.66ïQ Ad-hoc testing 0.87ïP 0.99ïQ Internal user 1.12ïP 0.97ïQ Component testing 1.13ïP 0.81ïQ System testing 1.21ïP 1.46ïQ more likely to be reopened Customer 1.33ïP 1.12ïQ © Microsoft Corporation
19.
Does opener reputation
influence the likelihood of bug reopens? For each bug, calculate openerâs reputation by aggregating over all bugs in the past. Hooimeijer and Weimer: Modeling bug report quality. ASE 2007. © Microsoft Corporation
20.
Does opener reputation
influence the likelihood of bug reopens? more likely to be reopened less likely to be reopened © Microsoft Corporation
21.
Does organizational and
geographic distance influence the likelihood of bug reopens? Vista Win7 Organizational Opened by and initially assigned to ⊠distance ⊠the same person X R ⊠someone with the same manager 1.13ïX 0.96ïR ⊠someone with a different manager 1.37ïX 1.07ïR Geographic Opened by and initially assigned to ⊠distance ⊠the same person X R ⊠someone in the same building 1.27ïX 0.93ïR ⊠someone in a different building but in the same country 1.45ïX 1.00ïR ⊠someone in a different country 1.52ïX 1.14ïR © Microsoft Corporation
22.
Does organizational and
geographic distance influence the likelihood of bug reopens? Vista Win7 Assigned to opener at some point in time Y S Never assigned to opener, but assigned to 0.54ïY 0.39ïS someone with the same manager as opener Never assigned to anyone with same manager 0.27ïY 0.34ïS Never assigned to opener, but assigned to 0.41ïY 0.37ïS someone in the same building Never assigned to anyone in same building, but 0.31ïY 0.43ïS assigned to someone in the same country Never assigned to anyone in the same country 0.20ïY 0.20ïS © Microsoft Corporation
23.
Descriptive statistical analysis
âą All pre- and post-release bug reports for Windows Vista and Windows 7 until July 2009 âą Logistic regression model to characterize â Probability that a bug will be reopened âą Logistic regression model to characterize â Probability that a bug will be fixed after the bug has been reopened â Probability that a bug will be fixed (Guo et al., ICSE 2010) âą Same factors as in Guo et al., ICSE 2010 © Microsoft Corporation
24.
Factor
Reopen (Vista) Human review not significant Code analysis tool -0.503 Bug source: Component testing 0.238 (categorical) Ad-hoc testing ï§ (baseline) System testing 0.204 Customer 0.239 Internal user not significant Reputation of bug opener -0.266 Reputation of 1st assignee not significant Opened by temporary employee 0.178 Initial severity level 0.127 Severity upgraded? 0.331 Opener / any assignee same manager? 0.721 Opener / any assignee same building? 0.468 Num. editors 0.236 Num. assignee building 0.090 Num. component path changes -0.160 © Microsoft Corporation
25.
Factor
Reopen (Vista) Human review not significant Code analysis tool decrease (-0.503) Bug source: Component testing increase (0.238) (categorical) Ad-hoc testing ï§ (baseline) System testing increase (0.204) Customer increase (0.239) Internal user not significant Reputation of bug opener -0.266 Reputation of 1st assignee not significant Opened by temporary employee 0.178 Initial severity level 0.127 Severity upgraded? 0.331 Opener / any assignee same manager? 0.721 Opener / any assignee same building? 0.468 Num. editors 0.236 Num. assignee building 0.090 Num. component path changes -0.160 © Microsoft Corporation
26.
Factor
Reopen (Vista) Human review not significant Code analysis tool decrease (-0.503) Bug source: Component testing increase (0.238) (categorical) Ad-hoc testing ï§ (baseline) System testing increase (0.204) Customer increase (0.239) Internal user not significant Reputation of bug opener decrease Reputation of 1st assignee not significant Opened by temporary employee increase Initial severity level increase Severity upgraded? increase Opener / any assignee same manager? increase Opener / any assignee same building? increase Num. editors increase Num. assignee building increase Num. component path changes decrease © Microsoft Corporation
27.
Which *reopened*
bugs get fixed? vs. Which bugs get fixed? © Microsoft Corporation
28.
Fixed When
Fixed (Vista) Factor Reopened (Vista) [Guo, ICSE 2010] Human review 0.377 0.511 Code analysis tool not significant 0.357 Bug source: Component testing -0.160 0.065 (categorical) Ad-hoc testing ï§ ï§ System testing not significant -0.129 Customer -0.498 -0.347 Internal user -0.465 -0.454 Reputation of bug opener 1.632 2.193 Reputation of 1st assignee 1.651 2.463 Opened by temporary employee -0.144 -0.125 Initial severity level not significant 0.033 Severity upgraded? not significant 0.256 Opener / any assignee same manager? not significant 0.676 Opener / any assignee same building? not significant 0.270 Num. editors 0.127 0.240 Num. assignee building -0.213 -0.257 Num. component path changes -0.162 -0.232 Num. re-opens n/a -0.135 © Microsoft Corporation
29.
Fixed When
Fixed (Vista) Factor Reopened (Vista) [Guo, ICSE 2010] Human review 0.377 0.511 Code analysis tool not significant 0.357 Bug source: Component testing -0.160 0.065 (categorical) Ad-hoc testing ï§ ï§ System testing not significant -0.129 Customer -0.498 -0.347 Internal user -0.465 -0.454 Reputation of bug opener 1.632 2.193 Reputation of 1st assignee 1.651 2.463 Opened by temporary employee -0.144 -0.125 Initial severity level not significant 0.033 Severity upgraded? not significant 0.256 Opener / any assignee same manager? not significant 0.676 Opener / any assignee same building? not significant 0.270 Num. editors 0.127 0.240 Num. assignee building -0.213 -0.257 Num. component path changes -0.162 -0.232 Num. re-opens n/a -0.135 © Microsoft Corporation
30.
Fixed When
Fixed (Vista) Factor Reopened (Vista) [Guo, ICSE 2010] Human review 0.377 0.511 Code analysis tool not significant 0.357 Bug source: Component testing -0.160 0.065 (categorical) Ad-hoc testing ï§ ï§ System testing not significant -0.129 Customer -0.498 -0.347 Internal user -0.465 -0.454 Reputation of bug opener 1.632 2.193 Reputation of 1st assignee 1.651 2.463 Opened by temporary employee -0.144 -0.125 Initial severity level not significant 0.033 Severity upgraded? not significant 0.256 Opener / any assignee same manager? not significant 0.676 Opener / any assignee same building? not significant 0.270 Num. editors 0.127 0.240 Num. assignee building -0.213 -0.257 Num. component path changes -0.162 -0.232 Num. re-opens n/a -0.135 © Microsoft Corporation
31.
Lessons learned
âą Improve reproducibility of bug reports âą Provide better tools to identify root cause âą Better estimate initial priorities âą Reduce the complexity of branching (bugs were âverifiedâ in the wrong branch) © Microsoft Corporation
32.
Thank you!
Partial replication of Shihab et al. New measurements: ï§ organizational and geographic distance, reputation, how found Qualitative component on the causes of bug reopens (survey): ï§ root cause, priority, process Descriptive models based on logistic regression http://research.microsoft.com/ese © Microsoft Corporation