Raspberry Pi 5: Challenges and Solutions in Bringing up an OpenGL/Vulkan Driv...
Patterns for Extracting High Level Information from Bug Reports
1. Patterns for Extracting High Level
Information from Bug Reports
Rodrigo Souza1,*
Christina Chavez1
Roberto Bittencourt2
1 Federal University of Bahia, Brazil
2 State University of Feira de Santana, Brazil
DAPSE’13: International Workshop on Data Analysis Patterns in Software Engineering
* speaker; email: rodrigo@dcc.ufba.br
May 21, 2013 San Francisco, USA
14. You’ll need:
- For each developer
- Number of times he changed
status to VERIFIED (i.e., verifications)
- Number of times he changed
resolution to FIXED (i.e., fixes)
Ingredients
15. 1
Directions
For each developer, compute the ratio:
verifications / (1 + fixes)
2 Choose a threshold and assume that
a developer is a verifier if
ratio > threshold
how?
16. Directions
2.1 For each ratio, use it as the threshold
and compute:
- the number of verifiers in the project
- the % of verifications performed by verifiers
2.2 Plot this data
x
y
17. Directions
90%
80%
70%
60%
50%
40%
30%
2%
4%
6%
8%
10%
12%
14%
1
5
10
15
20
25,
30
35
40
How to choose
a threshold?
size of QE team = number of verifiers (%)
% of verifications
by verifiers
ratio
(threshold candidate)
=
18. Directions
1
5
10
15
20
25,
30
35
40
fit an arm,
find the elbow!
% of verifications
by verifiers
2%
4%
6%
8%
10%
12%
90%
80%
70%
60%
50%
40%
30%
2.3
size of QE team = number of verifiers (%)
19. 3
Directions
If % of verifications by verifiers is high*,
they form a quality engineering team.
* e.g., > 50% 84%
39. If the number of verifications on a particular
day is too high, they may be mass updates
Look Out For Mass Updates and remove them
beforing looking for testing phases
40. Testing phases are less common in projects
with quality engineering teams