Interfaces emerged as the construct with higher negative correlation thus, less correlated with effectively located bugs.
Debugging is the act of locating bugs in software.
Not only is the task huge, it is also deadly dull ("like sorting out your sock drawer," says one veteran).But locating bugs is only the first of the three main stages of the process, to be followed by treating them in one of several ways, and then by testing to try to ensure that the problem is solved.
We unfold our general goal in the following research questions: RQ1: Are BLUiR, BLUiR+, and AmaLgam effective to locate bugs in C# projects?
Effective methods for automatically locating bugs from bug reports are highly desirable (Saha et al. 2013), as they would shorten bug-fixing time, consequently reducing software maintenance costs (Zhou et al. 2012).
Initially, we questioned whether current state-of-the-art bug localization techniques based on structured information retrieval, i.e., BLUiR, BLUiR+, and AmaLgam, would effectively locate bugs in C# projects.
Testbirds has more than 25,000 testers signed up to its current crowd-based testing platform — most, but not all of whom are based in Europe — to kick the tyres of companies' apps for them to help locate bugs and do things like user interface testing.
The lucky receipient of that was a man named Sergey Glazunov, who located a bug that Google is calling, "High Integer overflows in WebKit JavaScript objects".
Given their importance in the system domain, the names of such (class or method) abstractions are often the target of reflection when someone is either reporting or locating a bug.
Experiments with a proof-of-concept implementation, built using Java Pathfinder and WEKA, demonstrate that this heuristic locates bugs faster and more reliably than a conventional counterpart.
