Re: [Wikitech-l] Looking for Bugs In All the RIGHT Places
On 11/14/2012 07:06 PM, Jim Laurino wrote: Hello, I attended a talk [1] by Elaine Weyuker [2] on Wed, 7 Nov 2012. The talk, “Looking for Bugs In All the RIGHT Places”, discussed her work on predicting where bugs would be found in the next release of a program product. She and her collaborators have created a well validated tool that predicts, in under a minute, the 20% of the source files of the product, frozen before the next release, that will contain about 80% of the faults that will be corrected in that release. The tool is not a silver bullet, but it is useful; especially because it sometimes points attention to files that were not expected to have a lot of problems. The tool has two parts, a prediction front end and a back end interface to the revision control system and bug tracker. As I remember it, the entire system consisted of under 800 lines of python and under 3000 lines of C++. Using it would require adding a new back end. I thought that this tool might be useful in mediawiki development. She was amenable to helping get it working if there was interest. [1]http://www.ece.udel.edu/spotlight/WeyukerDLS.php [2]http://en.wikipedia.org/wiki/Elaine_Weyuker Thanks for the heads-up, Jim. I second Mark Holmquist's question -- can you point us to the code for the tool so we can start playing around with it? Thanks! -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Looking for Bugs In All the RIGHT Places
Hello, I attended a talk [1] by Elaine Weyuker [2] on Wed, 7 Nov 2012. The talk, “Looking for Bugs In All the RIGHT Places”, discussed her work on predicting where bugs would be found in the next release of a program product. She and her collaborators have created a well validated tool that predicts, in under a minute, the 20% of the source files of the product, frozen before the next release, that will contain about 80% of the faults that will be corrected in that release. The tool is not a silver bullet, but it is useful; especially because it sometimes points attention to files that were not expected to have a lot of problems. The tool has two parts, a prediction front end and a back end interface to the revision control system and bug tracker. As I remember it, the entire system consisted of under 800 lines of python and under 3000 lines of C++. Using it would require adding a new back end. I thought that this tool might be useful in mediawiki development. She was amenable to helping get it working if there was interest. [1]http://www.ece.udel.edu/spotlight/WeyukerDLS.php [2]http://en.wikipedia.org/wiki/Elaine_Weyuker -- Jim Laurino wican.x.jiml...@dfgh.net Please direct any reply to the list. Only mail from the listserver reaches this address. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Looking for Bugs In All the RIGHT Places
I thought that this tool might be useful in mediawiki development. She was amenable to helping get it working if there was interest. Where, pray tell, is the software? :) -- Mark Holmquist Software Engineer, Wikimedia Foundation mtrac...@member.fsf.org http://marktraceur.info * Sent from Ubuntu GNU/Linux * ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
