Comments on: Jasmine.Async: Making Asynchronous Testing With Jasmine Suck Less

By: wcanyon

wcanyon — Mon, 18 Feb 2013 23:17:00 +0000

Black text on a dark grey background? Yuck.

By: Alon Salant

Alon Salant — Fri, 30 Nov 2012 20:23:00 +0000

Oops. I see that another poster already pointed this out.

By: Alon Salant

Alon Salant — Fri, 30 Nov 2012 20:22:00 +0000

It’s worth noting that jasmine-node has supported the same async style as Mocha since Feb 2012. http://bytes.goodeggs.com/post/13332056735/better-asynchronous-jasmine-node-specs

Note to the author of Jasmine.Async – if you wanted you could have Jasmine.Async patch jasmine (as shown in the post above) so then when you include it, jasmine would support the done callback without having to create a new AsyncSpec.

By: millermedeiros

millermedeiros — Tue, 27 Nov 2012 21:44:00 +0000

jasmine-node monkey patches the `it`, `beforeEach` and `afterEach` methods: https://github.com/mhevery/jasmine-node/blob/master/lib/jasmine-node/async-callback.js – I find it simpler.

By: Derick Bailey

Derick Bailey — Thu, 06 Sep 2012 21:14:00 +0000

the it statement doesn’t need to be async in this case, though the plugin does support it.

By: Derick Bailey

Derick Bailey — Thu, 06 Sep 2012 21:14:00 +0000

the it statement doesn’t need to be async in this case, though the plugin does support it.

By: Dan Hollenbeck

Dan Hollenbeck — Thu, 06 Sep 2012 20:56:00 +0000

Typo in your gist?

async.it(“did stuff”, function(){
instead of

it(“did stuff”, function(){

By: Dan Hollenbeck

Dan Hollenbeck — Thu, 06 Sep 2012 20:56:00 +0000

Typo in your gist?

async.it(“did stuff”, function(){
instead of

it(“did stuff”, function(){

By: Rodrigo Rosenfeld Rosas

Rodrigo Rosenfeld Rosas — Fri, 24 Aug 2012 20:53:00 +0000

I won’t repeat myself on this issue once more. Please see my opinions here:

https://github.com/busterjs/buster/issues/193

By: Derick Bailey

Derick Bailey — Fri, 24 Aug 2012 17:49:00 +0000

if you can, do that. it’s not always possible, though. There are times when it’s far more difficult or creates too much of a brittle test, to spy/mock/stub the internal working of an object. in those cases, async tests are important. the prime example for me, right now, is WinJS/Promises. but also in API design for my Backbone applications, I often want to ensure my promises are working correctly for loading data through an API in my app instead of directly through a model or collection.