Comments on: JSpec: BDD for JS

By: Tj

Tj — Mon, 06 Apr 2009 19:14:55 +0000

Just released 1.0, check it out at http://visionmedia.github.com/jspec/

By: Tj

Tj — Sun, 15 Mar 2009 07:11:28 +0000

I have a library named JSpec as well, far more robust :) and will top pretty much every javascript bdd framework out there once it hits 1.0

http://github.com/visionmedia/jspec/tree/master

By: David Parker

David Parker — Mon, 28 Jan 2008 20:48:46 +0000

How does this work with JQuery? Note: I’m not a JavaScript master yet.

By: Jörn Zaefferer

Jörn Zaefferer — Sat, 10 Nov 2007 13:49:40 +0000

How about returning an object from should() that provides the methods you want to use? Something like 7.should().equal(…) or document.should().exist().

That way you can keep the number of methods on Object.prototype low and still stick with methods instead of parameters.

By: wycats

wycats — Sat, 10 Nov 2007 02:31:41 +0000

@Jörn: This way people can add to the matchers by just modifying the jspec.matchers object, instead of needing to define a new method on the Object prototype.

Also, while I have extended the Object prototype, I really don’t like it, and want to keep the number of extended objects finite and determinable (that way someone can still test jQuery.extend as long as they understand that should and should_not will be on the new Object erroneously).

By: Jörn Zaefferer

Jörn Zaefferer — Sat, 10 Nov 2007 02:22:59 +0000

That example looks interesting.

I wonder why you use should(“include”, …) instead of should_include(…) or should(“==”, …) instead of should_equal(…). You’ve started adding to Object.prototype anyway, so why stop halfway through?

On a side note: What is BDD?

By: Phil

Phil — Sat, 10 Nov 2007 01:02:56 +0000

Let’s get a repo going. I’m gonna mix it up with some mozrepl magick. http://hyperstruct.net/projects/mozrepl/