Characterizing Bug Workflows in Mozilla Firefox (SBES 2016)

Slide 1

Slide 1 text

Characterizing Bug Workflows in Mozilla Firefox Henrique Rocha (UFMG) Guilherme de Oliveira (UFMG) Marco Túlio Valente (UFMG) Humberto Marques-Neto (PUC-Minas) APPLIED SOFTWARE ENGINEERING RESEARCH GROUP / CBSoft 2016 – XXX SBES

Slide 2

Slide 2 text

Summary n  Introduction n  Study Design n  Dataset Overview n  Characterization Study o  All Bugs o  Fixed Bugs o  Duplicate Bugs o  Developers Fixing Bugs n  Conclusion 2

Slide 3

Slide 3 text

Introduction 3

Slide 4

Slide 4 text

Introduction Open source systems have many bugs. 4

Slide 5

Slide 5 text

Objective & Motivation n  Empirical study on Firefox bug reports o  Graph based characterization o  Focusing on the workflow followed by bugs n  Understand the bug handling process o  Overall visualization o  Identify bottlenecks 5

Slide 6

Slide 6 text

Contributions n  Characterization study showing aspects of the bug handling workflow n  Lightweighted methodology supported by graphs 6

Slide 7

Slide 7 text

Study Design 7

Slide 8

Slide 8 text

Bug Flow Graph (BFG) Lightweighted graph based technique showing the bug handling workflow 8

Slide 9

Slide 9 text

Dataset Overview 9

Slide 10

Slide 10 text

Dataset 13K Firefox bugs (2015) 10

Slide 11

Slide 11 text

Resolution time distribution 11

Slide 12

Slide 12 text

Characterization Study All Bugs 12

Slide 13

Slide 13 text

BFG for All Bugs 13

Slide 14

Slide 14 text

BFG for All Bugs 14 39% (136) 17% (157) 3.2k Bugs 0.8k Bugs Lesson Learned: techniques to help devs find these open bugs could improve the bug handling process.

Slide 15

Slide 15 text

BFG for All Bugs 15 38%(16) 22% (3) 90% (3) Lesson Learned: techniques to help devs find and take assignment on bugs could improve the bug handling process.

Slide 16

Slide 16 text

Characterization Study Fixed Bugs 16

Slide 17

Slide 17 text

BFG for Fixed Bugs 17

Slide 18

Slide 18 text

BFG for Fixed Bugs 18 20%(11) Lesson Learned: bugs require more time to be verified than to be fixed (almost 3x).

Slide 19

Slide 19 text

Characterization Study Duplicate Bugs 19

Slide 20

Slide 20 text

BFG for Duplicate Bugs 20

Slide 21

Slide 21 text

BFG for Duplicate Bugs 21 98%(2) 90%(1) Lesson Learned: techniques to identify duplicates before wasting devs time is useful to the process. Lesson Learned: transition time shows the efficacy of Firefox duplicate detection features

Slide 22

Slide 22 text

Characterization Study Developers Fixing Bugs 22

Slide 23

Slide 23 text

Developers Profile 23 Newbie (1-3 bugs) Junior (3-5 bugs) Senior (+5 bugs) Expert (+90 bugs)

Slide 24

Slide 24 text

BFG for Developers 24 48% (8) 96% (5) Newbie 48% (5) 99% (3) Junior 65% (2) 98% (3) Senior 82% (1) 98% (3) Expert Lesson Learned: more skilled devs get assigned more often to fix bugs. Lesson Learned: less skilled devs spend more time waiting to be assigned than actually fixing a bug.

Slide 25

Slide 25 text

Conclusions 25

Slide 26

Slide 26 text

Final Remarks n  BFG – lightweighted technique showing the bug workflow n  13K Firefox (2015) o  Reveal findings in the bug handling process q  Many open bugs might be neglected q  A bug is resolved faster when properly assigned to a dev o  Developers skill on bug handling q  Less skilled devs waits longer to find bugs 26

Slide 27

Slide 27 text

Future Work n  Characterize other types of bugs and time intervals. n  Analyze other systems n  Field study to verify developers impressions on BFGs n  Online tool to generate BFGs 27

Slide 28

Slide 28 text

[email protected] [email protected] [email protected] [email protected] Thank you! Questions? APPLIED SOFTWARE ENGINEERING RESEARCH GROUP / CBSoft 2016 – XXX SBES