[rspec-users] Assertions for asynchronous behaviour

Matt Wynne matt at mattwynne.net
Sun Oct 2 17:02:58 EDT 2011

On 28 Sep 2011, at 01:09, Alex Chaffee wrote:

> After a week of stealing minutes, I eventually wrote eventually!
> Please check this out and give me feedback. I can ship it in a new
> Wrong gem as soon as you all tell me it's ready.
> docs:
> https://github.com/alexch/wrong/commit/cae852f09a3d4dcb3f014b486a10d5eb7a10e7f5
> test (spec):
> https://github.com/alexch/wrong/blob/master/test/eventually_test.rb
> code:
> https://github.com/alexch/wrong/blob/master/lib/wrong/eventually.rb
> The only major feature I haven't done is editing the error message
> from inside the block, since Wrong seems to do a good job of this on
> its own. If the block contains a "should" or a Wrong "assert" then it
> ends up looking like it just got called and failed the final time.
> It'd be nice if I could sneak into an exception and append "(after 5
> sec)" to e.message but I don't know if I want to go there...

I haven't used it, but this looks good to me.

> -- 
> Alex Chaffee - alex at stinky.com
> http://alexchaffee.com
> http://twitter.com/alexch
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


Freelance programmer & coach
Author, http://pragprog.com/book/hwcuc/the-cucumber-book (with Aslak Hellesøy)
Founder, http://relishapp.com
+44(0)7974430184 | http://twitter.com/mattwynne

More information about the rspec-users mailing list