I''ve started using specs as a to-do list. I write explicitly violated specs so I know what to come back to. But a lot of the time, that means if I start to work on another piece of functionality covered by the same spec, it''s hard to tell what I''m working on now from the explicit failues. I run all my specs through TextMate to use the HTML output, so I go by the "95 specifications, 3 failures" line at the top. I''d find it useful if I could mark specs as failing but unimportant, eg "95 specifications, 1 failure, 2 deferred". You could even display these limbo specs in orange to separate them visually. Anyone else think this is a good idea, or is there too much chance of it being abused as a way of saying, "I''ll get round to it when I can be bothered"? It''s definitely better than commenting out specs, which is really risky. Ashley
On 2/23/07, Ashley Moran <work at ashleymoran.me.uk> wrote:> I''ve started using specs as a to-do list. I write explicitly > violated specs so I know what to come back to. But a lot of the > time, that means if I start to work on another piece of functionality > covered by the same spec, it''s hard to tell what I''m working on now > from the explicit failues. > > I run all my specs through TextMate to use the HTML output, so I go > by the "95 specifications, 3 failures" line at the top. I''d find it > useful if I could mark specs as failing but unimportant, eg "95 > specifications, 1 failure, 2 deferred". You could even display these > limbo specs in orange to separate them visually. > > Anyone else think this is a good idea, or is there too much chance of > it being abused as a way of saying, "I''ll get round to it when I can > be bothered"? It''s definitely better than commenting out specs, > which is really risky.There is a similar RFE: http://rubyforge.org/tracker/index.php?func=detail&aid=8139&group_id=797&atid=3152 Also, the rspec-ext project does something like this: http://rashkovskii.com/articles/2007/2/16/rspec-ext-gem> > Ashley > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
*de-lurking*, ... so let me first thank you guys for rspec! That''s an absolute amazing tool :-) Am 23.02.2007 um 16:59 schrieb Ashley Moran:> I''ve started using specs as a to-do list. I write explicitly > violated specs so I know what to come back to. But a lot of the > time, that means if I start to work on another piece of functionality > covered by the same spec, it''s hard to tell what I''m working on now > from the explicit failues. > > I run all my specs through TextMate to use the HTML output, so I go > by the "95 specifications, 3 failures" line at the top. I''d find it > useful if I could mark specs as failing but unimportant, eg "95 > specifications, 1 failure, 2 deferred". You could even display these > limbo specs in orange to separate them visually.<http://rubyforge.org/tracker/index.php? func=detail&aid=8139&group_id=797&atid=3152> seems to describe something similar, does it? -- sven fuchs fon: +49 (58 45) 98 89 58 artweb design fax: +49 (58 45) 98 89 57 breite stra?e 65 www: http://www.artweb-design.de de-29468 bergen mail: svenfuchs at artweb-design.de