#1362 Better Precision on rake:stats - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#1362 ✓wontfix

Better Precision on rake:stats

Reported by Brian Cardarella | November 12th, 2008 @ 04:43 PM | in 2.x

Why not increase the precision so we have a more useful test:code metric?

code_statistics.rb

104c104

  puts "  Code LOC: #{code}     Test LOC: #{tests}     Code to Test Ratio: 1:#{sprintf("%.3f", tests.to_f/code)}"

Is there a good reason to keep the precision so low? The metric becomes somewhat useless in a larger app because of Ruby's floating point rounding.

You flagged this item as spam.
Brian Cardarella November 12th, 2008 @ 04:49 PM
Well that looked horrible. :p Attaching the diff as an attachment and learning my lesson on pasting directly.
- code_statistic.diff 252 Bytes
Pratik March 7th, 2009 @ 03:31 PM
- Tag set to “patch”
- State changed from “new” to “wontfix”
I think .1f is just fine :) Not sure it's helpful to show 3 precisions.

Thanks !