Timeline for Does defect clustering in source code effect really exist?
Current License: CC BY-SA 4.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 19 at 0:37 | history | protected | gnat | ||
| S Oct 18 at 19:17 | history | suggested | Kromster | CC BY-SA 4.0 |
Better title
|
| Oct 16 at 18:30 | comment | added | gnasher729 | What is a bug? According to QA a bug is your software as a whole misbehaving. According to the software developer, it’s one incorrect item in your source code. One “developer” bug can cause a dozen “QA” bugs. Or only one. Or none at all, if the software handles an edge case incorrectly, but QA doesn’t test that edge case. | |
| Oct 16 at 9:01 | comment | added | JonasH | I kind of doubt that there are good studies on this. A well controlled study would be very expensive to do, and a observational study could easily suffer from various types of bias, and may not reveal the root cause. You would for example need to account for how much any piece of code has been tested and used, and that is often not recorded systematically. | |
| Oct 16 at 7:07 | comment | added | gnasher729 | @kirie. You have an array of 10 items and write to the twelfth by mistake. That means random things in memory change. Now anything can happen. | |
| Oct 16 at 6:44 | review | Suggested edits | |||
| S Oct 18 at 19:17 | |||||
| Nov 28, 2016 at 1:21 | history | tweeted | twitter.com/StackSoftEng/status/803046069655531520 | ||
| Nov 23, 2016 at 3:03 | review | Close votes | |||
| Nov 24, 2016 at 3:02 | |||||
| Nov 16, 2016 at 4:58 | comment | added | kirie | @gnasher729 I do not know what overwrite bit of information you mention, but this is common when you use DRY principle on early stage when many function havent been fully tested yet already used many times. | |
| Nov 16, 2016 at 1:02 | comment | added | mattnz | I think this is a valid question and would not like to see it closed, as the OP specifiably asked for "concrete non-anecdotal data". However, the answers given so far are not providing this. I would rather see it protected and answers without links to research down voted. | |
| Nov 15, 2016 at 22:24 | comment | added | gnasher729 | Very rarely I have a bug that may overwrite a random bit of information, anywhere. With that kind of bug in the source code, the software could misbehave in gazillions of possible ways. | |
| Nov 15, 2016 at 19:55 | answer | added | Vlad | timeline score: 0 | |
| Nov 15, 2016 at 17:48 | answer | added | Dark Matter | timeline score: 3 | |
| Nov 15, 2016 at 17:18 | answer | added | Doc Brown | timeline score: 5 | |
| Nov 15, 2016 at 17:04 | comment | added | Marshall Tigerus | I'll agree with @kirie here, that a bug in one piece of functionality usually has a cascade effect on other pieces of functionality. The tester may think they are distinct bugs, but they are really all sourced from the one problem. Additionally, humans are well designed to find patterns, which is why we do it in everything. | |
| Nov 15, 2016 at 16:09 | answer | added | Robert Harvey | timeline score: 2 | |
| Nov 15, 2016 at 16:00 | comment | added | kirie | The reason is because one bug can breed other bugs, this happen because code is interlinked, so while tester feel good finding many bug sometimes they dont know that programmer just need to fix that one bug and poof all the other is gone. | |
| Nov 15, 2016 at 15:57 | review | Close votes | |||
| Nov 17, 2016 at 11:42 | |||||
| Nov 15, 2016 at 15:33 | review | First posts | |||
| Dec 15, 2016 at 15:35 | |||||
| Nov 15, 2016 at 15:32 | history | asked | dtldarek | CC BY-SA 3.0 |