Looking for a Code review tool for ruby(checkstyle)

Rails
#1

I have been looking around for something like checkstyle (Java code
review tool) for ruby.
http://checkstyle.sourceforge.net/availablechecks.html
Has anyone here ever come across a similar dilema wherein we need to
enforce the quality of ruby code written in different projects.
What strategy could we adopt?
Plan B would be to maybe use a web based code review tool with manual
reviews, but thats really going back.

cheers…

#2

The best code review tool is another person. Preferrably versed in the
way
of the Ruby.

On Jan 17, 2008 3:33 PM, Jet [email protected] wrote:

cheers…

–
Ryan B.
http://www.frozenplague.net
Feel free to add me to MSN and/or GTalk as this email.

#3

Hi Jet,
This is the only one I could find, haven’t tried it yet, but it seems
promising, if a bit young:

http://github.com/martinjandrews/roodi/tree

Jet wrote:

I have been looking around for something like checkstyle (Java code
review tool) for ruby.
http://checkstyle.sourceforge.net/availablechecks.html
Has anyone here ever come across a similar dilema wherein we need to
enforce the quality of ruby code written in different projects.
What strategy could we adopt?
Plan B would be to maybe use a web based code review tool with manual
reviews, but thats really going back.

cheers…

#4

On Jul 13, 12:19 pm, Danny C. [email protected] wrote:

Hi Jet,
This is the only one I could find, haven’t tried it yet, but it seems
promising, if a bit young:

http://github.com/martinjandrews/roodi/tree

Metric_fu includes roodi - it’s a decent place to start.

Jet wrote:

I have been looking around for something like checkstyle (Java code
review tool) for ruby.
http://checkstyle.sourceforge.net/availablechecks.html

I’ve personally found that (as Ryan suggested) the best “review” is a
human reading the code. This is easier in Ruby than in Java, since
there’s considerably less visual noise in a well-written block of
Ruby.

The metric_fu tools do identify several of the remaining issues (code
duplication, excessive cyclomatic complexity,etc) but aren’t really
intended to be used proscriptively (in other words, making a hard rule
“no complexity ratings over 5 EVAR!” will lead to problems) but rather
as a roadmap for detailed human review.

–Matt J.