0.0
No commit activity in last 3 years
No release in over 3 years
Implementation of simple bug prediction hotspot heuristic
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Runtime

>= 0.21.0
 Project Readme

Bugspots - Bug Prediction Heuristic

An implementation of the simple bug prediction heuristic outlined by the Google Engineering team: Bug Prediction at Google

Well, we actually have a great, authoritative record of where code has been requiring fixes: our bug tracker and our source control commit log! The research indicates that predicting bugs from the source history works very well, so we decided to deploy it at Google.

Point bugspots at any git repo and it will identify the hotspots for you.

Usage

$> gem install MFOL-bugspots
$> bugspots /path/to/repo -b develop -f ".php"
$> git bugspots (in root of current git project, --help for options)
  • With the "-f" tag you could specify one file extension to go through, the default value is ".php"
  • The files with very very low scores are ignored in the result list.

An example of the command could be:

bugspots /PATH/TO/REPO -b develop -f .php -r "/^bug( |-)/i"

This means to find all comments starting with bug(case insensitive) from the REPO in the "develop" branch and then caculate on only php files.

License

(MIT License) - Copyleft (c) 2015 Xiaoming Cai