What makes a good bug report? BettenBurg, N. Just, S. Schroter, A. Weiss, C. Premraj, R. Zimmermann, T Presented by Yueqi Li

1

Outline ●

Introduction

●

Methodology

●

Results

●

Measuring bug report quality

●

Conclusion

●

Discussion

2

Outline ●

Introduction

●

Methodology

●

Results

●

Measuring bug report quality

●

Conclusion

●

Discussion

3

Introduction ●

●

Bug reports are crucial for developers to locate bugs and fix bugs. What makes a good report in the view of developers?

●

What makes a good report in the view of reporters?

●

Do reporters always provide good reports?

●

Is it possible to measure the quality bug reports automatically? 4

Outline ●

Introduction

●

Methodology

●

Results

●

Measuring bug report quality

●

Conclusion

●

Discussion

5

Methodology ●

● ●

Conducting a survey among 872 developers (156 responses) and 1354 (310 responses) reporters. The survey is in the form of questionnaire. The survey was conducted on 3 open source projects: Apache, Eclipse, and Mozilla.

6

The questionnaire for developers ●

●

Contents of bug reports: –

Which items have developers previously used when fixing bugs?

–

Which three items helped the most?

Problems with bug reports: –

Which problems have developers encountered when fixing bugs?

–

Which three problems caused most delay in fixing bugs? 7

The questionnaire for reporters ●

●

Contents of bug reports: –

Which items have reporters previously provided?

–

Which three items were most difficult to provide?

Contents considered to be relevant: –

Which three items do reporters consider to be most relevant for developers

8

Outline ●

Introduction

●

Methodology

●

Results

●

Measuring bug report quality

●

Conclusion

●

Discussion

9

Results ●

For developers: –

Most widely used items: ● ● ● ●

–

Steps to reproduce Observed and expected behavior Stack traces test cases.

Importance of items: ●

Steps to reproduce

10

Results ●

For reporters: –

Items provided by most reporters: ● ●

–

Expected behavior Steps to reproduce

Items considered to be most useful to developers ●

Steps to reproduce

11

Evidence for information mismatch

The figure is copied from the paper.

12

Outline ●

Introduction

●

Methodology

●

Results

●

Measuring bug report quality

●

Conclusion

●

Discussion

13

Measuring bug report quality ●

Using classification techniques.

●

Input features: –

●

Training and test data: –

●

Itemizations, Keyword completeness, Code Samples, Stack Traces, Patches, Screenshots, Readability. The rating obtained in the survey.

41% of accuracy

14

Outline ●

Introduction

●

Methodology

●

Results

●

Measuring bug report quality

●

Conclusion

●

Discussion

15

Conclusion ●

●

●

Steps to reproduce and stack traces are most useful in bug reports. Most severe problems encountered by developers are errors in steps to reproduce, incomplete information, and wrong observed behavior. It is possible to automatically measure bug report quality and give suggestions for reporter to improve their reports. 16

Outline ●

Introduction

●

Methodology

●

Results

●

Measuring bug report quality

●

Conclusion

●

Discussion

17

Discussion ●

●

Conducting a survey to show the severity of a problem can be a useful way to motivation a work. How to conduct survey among so many people? How to encourage people to participate this kind of survey?

18

Thank you.

19