[LRUG] uncalled methods analysis when running test suite

[Anthony Green]

Or go all out with metric_fu
 
> rcov
> 
> On 16 February 2010 23:20, Tim Cowlishaw <tim at timcowlishaw.co.uk> wrote:
> 
>> Hey all,
>> 
>> I'm working on a fairly complex app, but one with a lot of code that could
>> potentially have been deprecated ages ago, and never removed. I was just
>> wondering if there was some sort of source-code analysis tool that would run
>> my specs and features, and then report on which areas of the codebase where
>> never called as part of the test suite, giving me some idea of areas of the
>> app that can be pruned back. Anyone have any idea whether such a thing
>> exists?
>> 
>> Cheers,
>> 
>> Tim
>> 
>> _______________________________________________
>> Chat mailing list
>> Chat at lists.lrug.org
>> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>> 
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org

-- 
Anthony Green
Client Side Developer
Future Media & Technology for BBC Audio & Music Interactive
Room 718 | 7th Floor | Henry Wood House | Tel: x54341 


http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.