Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.ruby > #3167
| From | milki <milki@rescomp.berkeley.edu> |
|---|---|
| Newsgroups | comp.lang.ruby |
| Subject | Re: Hook into rake for reporting results |
| Date | 2011-04-19 08:17 -0500 |
| Organization | Service de news de lacave.net |
| Message-ID | <20110419131348.GB67946@hal.rescomp.berkeley.edu> (permalink) |
| References | <20110418214818.GA67946@hal.rescomp.berkeley.edu> <DAA1931AD25443859DA82372B512F9AC@gmail.com> |
On 09:05 Tue 19 Apr , Michael Sokol wrote: > I guess you could simply analyze the output of a `rake test` task. > Maybe create a rake task that calls the :test task and processes its output? I think this could work, but I'm not sure if it would destinguish between pending test results or individual test results. -- milki
Back to comp.lang.ruby | Previous | Next — Previous in thread | Find similar | Unroll thread
Hook into rake for reporting results milki <milki@rescomp.berkeley.edu> - 2011-04-18 16:48 -0500
Re: Hook into rake for reporting results Steve Klabnik <steve@steveklabnik.com> - 2011-04-18 17:44 -0500
Re: Hook into rake for reporting results milki <milki@rescomp.berkeley.edu> - 2011-04-19 08:17 -0500
Re: Hook into rake for reporting results Steve Klabnik <steve@steveklabnik.com> - 2011-04-19 08:45 -0500
Re: Hook into rake for reporting results Michael Sokol <mikaa123@gmail.com> - 2011-04-18 19:05 -0500
Re: Hook into rake for reporting results milki <milki@rescomp.berkeley.edu> - 2011-04-19 08:17 -0500
csiph-web