Sep 10

Rails Rumble project reports

dastels @ 10:18 pm

The stats for our project:

+----------------------+-------+-------+---------+---------+-----+-------+
| Name                 | Lines |   LOC | Classes | Methods | M/C | LOC/M |
+----------------------+-------+-------+---------+---------+-----+-------+
| Controllers          |    70 |    55 |       2 |       6 |   3 |     7 |
| Helpers              |     6 |     4 |       0 |       0 |   0 |     0 |
| Models               |   891 |   734 |      13 |     110 |   8 |     4 |
| Libraries            |     0 |     0 |       0 |       0 |   0 |     0 |
| Model specs          |  2283 |  1835 |       0 |       0 |   0 |     0 |
| View specs           |     0 |     0 |       0 |       0 |   0 |     0 |
| Controller specs     |     0 |     0 |       0 |       0 |   0 |     0 |
| Helper specs         |     0 |     0 |       0 |       0 |   0 |     0 |
+----------------------+-------+-------+---------+---------+-----+-------+
| Total                |  3250 |  2628 |      15 |     116 |   7 |    20 |
+----------------------+-------+-------+---------+---------+-----+-------+
  Code LOC: 793     Test LOC: 1835     Code to Test Ratio: 1:2.3

A few things to notice:

  • very “rails” light… small controller… very literally a controller.. all the action happens in the models,
  • all the specs are for model classes, the controller & view do very little.. although the controller could probably do with a few specs, and
  • there’s over twice as much code in the specs than in the working classes.

The spec run:

$rake spec
(in /Users/dastels/Projects/Ruby-Projects/merlin/trunk)
..........................................................................
..........................................................................
..........................................................................
........................................................
Finished in 62.891545 seconds
278 examples, 0 failures

and the coverage report:

SafariScreenSnapz001.png
Note that echo was under development and actually didn’t get finished in time. Also we ran out of time before getting to mindbender.
Tags: 

One Response to “Rails Rumble project reports”

  1. Andy Maleh says:

    Those numbers are definitely something to be proud of.

Leave a Reply