On Thu, Oct 25, 2012 at 9:31 PM, sent-hil <[email protected]> wrote: > Not just test coverage, but stuff like: most commonly occurring error and > etc. My original idea was to create a new outputter and in `example_failed` > method I'd output the info to a json file. Is there a better way?
There is nothing built in that maintains stats, however the next release (2.12.0 - coming very soon) includes a json formatter. Once that's out you can pipe its output to a file with a time-based name and write some code to mine these files over time. Michael Feathers has done some work on mining git repos that might provide some inspiration for you: https://github.com/michaelfeathers/repodepot-ruby Please let us know what you come up with - especially if you end up releasing something other ppl can use to do similar analysis. Cheers, David > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "rspec" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msg/rspec/-/PvdkTSS3mIEJ. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "rspec" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
