Rails testing Goat

[Pascal Rettig]

Hi All,

I was looking for a way to check coverage of changes a new remote developer was committing and didn't find anything via Google, so I wrote a quick-and-dirty script to drop commits #'s and committer names into the rcov coverage reports via `git blame` - I realized it might as well pull out total stats on the project and find out who the least diligent in test coverage among us was (i.e. the testing scapegoat)

I put code for the script in a Gist in case anyone else thinks that might be interesting: https://gist.github.com/1404986

-Pascal

[Bryan Helmkamp]

Cool hack, Pascal.

Based on your use case, I thought it might be worth noting that some
people have found a project I'm working on, Code Climate, useful for
helping new/junior developers improve the quality of their
contributions to a project. If you're interested, it can be found
here:

https://codeclimate.com/

It doesn't deal with coverage yet (but planned), but it can send you a
weekly email outlining how classes in your code have changed from a
quality standpoint. It uses static analysis of complexity and
duplication.

Cheers,

-Bryan

> --
> You received this message because you are subscribed to the Boston Ruby
> Group mailing list
> To post to this group, send email to boston-r...@googlegroups.com
> To unsubscribe from this group, send email to
> boston-rubygro...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/boston-rubygroup

[Pascal Rettig]

Hi Bryan,

Just taking a quick scan at what it offers, that looks very cool - will definitely give Code Climate a shot.

-Pascal