ID | input_buggy | input_open | text_buggy |
---|---|---|---|
1 | Don’t have | No | Yes. Running manual tests. |
2 | Brazil | https://github.com/bfsc/qmethod | Yes. Through looking code. |
3 | No | No | A lot of times a notice changes that introduce bugs. In most of the cases I perceive the buggy code running unit tests. |
4 | Brazil | NA | when i tested the aplication. |
5 | No longer have access to it or can’t disclose the ones that used the issue system. Unfortunately, I have access to some buggy code, but I can’t identify the commits that were buggy. The commits are huge and the bugs were too many, so many bugs were fixed in a single commit (and the commit does not explicit that). | Yes. | |
https | ://github.com/mgechev/javascript-algorithms Yes. Usually, I perceive buggy code when I investigate (debug) why a functionality is not working as expected. Sometimes, I also perceive buggy code when a ​code is taking too l | ong to execute or consuming too much memory. | |
6 | NA | NA | NA |
7 | NA | No | NA |
8 | |||
9 | NA | no | I note the buggy code when the code doesn’t work properly |
10 | NA | No, I haven’t | Making small chances and manually testing. |
11 | NA | NA | |
12 | No, I couldn’t. | No, I haven’t. | Yes, I did. My perception was when I verific the code before of deploy. |
13 | NA | https://github.com/eclipse/openj9 | I think it is hard to notice that manually. I used to run automated tests before sending a pull request. |
14 | NA | Apenas em Projetos fechados. | Acredito que a introdução de lógicas negativas tem a probabilidade muito maior no aparecimento de bugs. |
15 | NA | No | no |
16 | NA | NA | Yes. Revising the logic of the changed snippet and the methods it has achieved |
17 | https://github.com/vazaazika/zika-core/commit/eb673022f586988f3dbbfa6e9e6d67c034f434de | no | Either when I ran the tests or when I ran the program and I noticed an usual behavior |
18 | NA | NA | Não |
19 | NA | Yes. When a change in certain portion of the system broke another adjacent part. Certain functionality stopped to work. | |
20 | No | NA | Manually testing |
21 | NA | No | Yes, in some cases, when we change a name of class or your property we get some bugs. |
22 | NA | Yes. | |
https | ://github.com/leofernandesmo/emp_experiment | ||
https | ://github.com/easy-software-ufal/muJava-AUM | ||
https | ://github.com/easy-software-ufal/Nimrod No | ||
23 | NA | NA | NA |
24 | Brazil | No. | Yes, when the expected behavior for a certain action did not occur. |
25 | NA | NA | NA |
26 | https://github.com/grails/grails-core/commit/362800402acbb9c6641198e4d0c3a6b913ab069f | Yes. | |
https | ://github.com/grails/grails-core | ||
https | ://github.com/spring-projects/spring-boot Yes. Unexpected behavior after updating the version of a third-party framework | ||
27 | It was a closed project. | No. | Yes. It was discovered due to problems like the running time of the code. |
28 | NA | No | NA |
29 | NA | NA | Yes, when we didn’t care much about the documentation the introducion of bugs highsed. |
30 | No | ||
31 | NA | NA | NA |
32 | Brazil | No. | Yes. Based on experience and history of software evolution. |
33 | I can’t. | NA | During development it is noticed that bugs are usually associated with the introduction of a new functionality that interferes with an already existing one. Developers do not bother to check the interrelationships and architectures of the software, which causes bugs of these interactions. Usually the bug is noticed when this new functionality is called in modules it interacts with others. |
34 | NA | No. | No. |
35 | é um projeto privado | NA | Sim. Quando houve conflito de merge no sistema |
36 | Unfortunately, the code is private so that I cannot share it with you. | NA | Yes, I did. Several times, I would say. And I just realized that my code was buggy when the quality assurance team has sent me the bug report. |
37 | No | No | New syntax for different language versions |
38 | NA | Yes, I do. Projects at https://launchpad.net/, https://code.google.com/archive/p/sisjus/ | Yes, the team realized through automated testing, due to the fact that a team developer had no knowledge of the business rule, but had experience in the language |
39 | USA | https://github.com/python/mypy | Of course. Many ways: the code was obviously wrong, the tests threw a warning, static analysis tools complained… |
40 | No | No | When I ran and it crashed. |
41 | NA | NA | Working with Objective-C, I often see potentially buggy code, specially from developers that don’t have enough experience with the language - they are also often tricky. Some examples might include nil values that fail silently, using NSNumbers as booleans etc |
Degree (Factor A):
edu | Frequency | percent |
---|---|---|
mscstu | 4 | 36.363636 |
msc | 2 | 18.181818 |
understu | 2 | 18.181818 |
other | 1 | 9.090909 |
phd | 1 | 9.090909 |
under | 1 | 9.090909 |
Jobs (Factor A):
selectedJobs | Frequency | percent |
---|---|---|
Industrial Developer | 3 | 27.27273 |
Academic Researcher | 2 | 18.18182 |
Industrial Developer,Open Source Developer | 2 | 18.18182 |
Industrial Developer,Other | 2 | 18.18182 |
Other | 2 | 18.18182 |
Expertise (Factor A):
Degree (Factor B):
edu | Frequency | percent |
---|---|---|
mscstu | 2 | 40 |
under | 2 | 40 |
understu | 1 | 20 |
Jobs (Factor B):
selectedJobs | Frequency | percent |
---|---|---|
Academic Researcher | 1 | 20 |
Academic Researcher,Industrial Developer | 1 | 20 |
Academic Researcher,Industrial Developer,Industrial Researcher | 1 | 20 |
Industrial Developer | 1 | 20 |
Open Source Developer | 1 | 20 |
Expertise (Factor B):
Degree (Factor C):
edu | Frequency | percent |
---|---|---|
mscstu | 4 | 66.66667 |
understu | 2 | 33.33333 |
Jobs (Factor C):
selectedJobs | Frequency | percent |
---|---|---|
Academic Researcher | 1 | 16.66667 |
Academic Researcher,Industrial Developer,Other | 1 | 16.66667 |
Academic Researcher,Open Source Developer | 1 | 16.66667 |
Industrial Developer | 1 | 16.66667 |
Industrial Developer,Other | 1 | 16.66667 |
Open Source Developer | 1 | 16.66667 |
Expertise (Factor C):
Degree (Factor D):
edu | Frequency | percent |
---|---|---|
mscstu | 1 | 33.33333 |
under | 1 | 33.33333 |
understu | 1 | 33.33333 |
Jobs (Factor D):
selectedJobs | Frequency | percent |
---|---|---|
Academic Researcher | 2 | 66.66667 |
Academic Researcher,Industrial Developer | 1 | 33.33333 |
Expertise (Factor D):
Degree (Factor E):
edu | Frequency | percent |
---|---|---|
other | 2 | 50 |
understu | 2 | 50 |
Jobs (Factor E):
selectedJobs | Frequency | percent |
---|---|---|
Academic Researcher | 1 | 25 |
Academic Researcher,Other | 1 | 25 |
Industrial Developer | 1 | 25 |
Other | 1 | 25 |
Expertise (Factor E):