UnderscoreMatchersForJasmine adds a series of matchers for Jasmine-based JavaScript/Coffeescript testing based on Underscore methods, the Backbone library. Some handy JS expectations are thrown in as well that are helpful when testing your model objects (whether you use Backbone or not). Example:
expect(snafu).toInclude('s', 'n', 'a')
// if snafu is an array, this is equivalent to:
expect(
_(snafu).include('s') && _(snafu).include('n') && _(snafu).include('a')
).toBeTruthy()
// if snafu is a Backbone.js collection, this is equivalent to:
expect(
snafu.include('s') && snafu.include('n') && snafu.include('a')
).toBeTruthy()
That makes your tests easy to read, for example:
$ ->
describe 'States and StateMachines', ->
it 'should associate states with a state machine and the state machine with its states', ->
engine_status = new StateMachine()
running = engine_status.new_state()
idling = engine_status.new_state()
expect(running).toRepondTo('state_machine')
expect(engine_status.states()).toInclude(running, idling)
it 'should generate states with rpm', ->
engine_status = new StateMachine()
running = engine_status.new_state()
expect(running).toBeA(State)
expect(running).toHave('rpm')
The defining characteristic of UnderscoreMatchersForJasmine is its transparent support for Backbone. Expectations like .toInclude and .toHave work with standard JavaScript objects and also with Backbone collections and models transparently. For example, .toHave:
foo =
attributes:
bar: 'bash'
foo.hasOwnProperty('bar')
# => false
foo.hasOwnProperty('attributes')
# => true
_.has(foo, 'bar')
# => false
_.has(foo, 'attributes')
# => true
expect(foo).not.toHave('bar')
expect(foo).toHave('attributes')
When you have a standard JS object, the toHave expectation mirrors .hasOwnProperty or _.has
fooModel = new Backbone.Model
bar: 'bash'
foo.hasOwnProperty('bar')
# => false
foo.hasOwnProperty('attributes')
# => true
_.has(foo, 'bar')
# => false
_.has(foo, 'attributes')
# => true
expect(foo).toHave('bar')
expect(foo).not.toHave('attributes')
When you have a Backbone model, the toHave expectation mirrors .has from Backbone: It tests whether the model has an attribute. This is nearly always what you want.
Yes.
Let's take it point by point:
- Underscore is a utility-belt library for JavaScript. Backbone.js is a lightweight MVC library for JavaScript.
- Jasmine is a Test-Driven Development testing framework for JavaScript. You can run tests in a pretty browser window, you can run tests on the command line with Node.js, you can run tests in the console. If you are writing JavaScript and/or Coffeescript, you should be using Jasmine.
- If you are using Underscore or Backbone and you are using Jasmine, your tests will be cleaner and more readable with these matchers for the same reason that your code is cleaner and more readable with Underscore and Backbone.
Read the code in Coffeescript or JavaScript.
Or, here's the "tl;dr:"
# collections:
expect([...]).toBeEmpty() or expect(new Backbone.Collection(...)).toBeEmpty()
expect([...]).toInclude(foo, bar) or expect(new Backbone.Collection(...)).toInclude(foo, bar)
expect([...]).toIncludeAny(blitz) or expect(new Backbone.Collection(...)).toIncludeAny(blitz)
expect([...]).toBeCompact() or expect(new Backbone.Collection(...)).toBeCompact()
expect([...]).toBeUnique() or expect(new Backbone.Collection(...)).toBeUnique()
# object methods
expect(foo).toRespondTo('push', 'pop')
expect(foo).toRespondToAny('push', 'isEmpty')
# object properties
expect(foo).toHave('length', 'arity')
expect(foo).toHaveAny('length', 'size')
# model properties
var Sidebar = Backbone.Model.extend({
promptColor: function() {
var cssColor = prompt("Please enter a CSS color:");
this.set({color: cssColor});
}
});
myBar = new Sidebar();
expect(myBar).not.toHave('color'); # we haven't set a color
myBar.set({color: ...});
expect(myBar).toHave('color'); # we haven't set a color
# OO and is-a (all synonymous)
expect(new Foo()).toBeAnInstanceOf(Foo)
expect(new Foo()).toBeA(Foo)
expect(new Foo()).toBeAn(Foo)
This is what I happen to need right now for my actual code. As I write more matchers, I'll add them. So, if you're interested, watch the library. I suppose I could go through and make a matcher for every function in Underscore, but I'd rather let it grow organically. If there's a matcher you need that isn't here, well, we're all in the same boat:
- If you're a passenger, send me a message describing the matcher you want. If it seems useful, I'll add it.
- If you're a sailor, fork this project, add the matcher, and send me a pull request.
- If you're the captain of your own ship, and you've already written some matchers like this, run up some signal flags and I'll include links to your project right here.
- And if you're a pirate, take this code and/or just the idea and make your own library. I'm cool with that.
Yes:
npm install UnderscoreMatchersForJasmine
If you're using Coffeescript, put underscore_matchers.coffee in your project. If you're using plain JavaScript, it should therefore follow that you want to put underscore_matchers.js in your project. You can also put underscore_matchers_spec.coffee or underscore_matchers_spec.js in your project if you want to see these matchers test themselves. It's also handy documentation for how the matchers behave!
Yes.
Who's Using This?
I am.
Is there a gem?
No. This is a Coffeescript and JavaScript include file, not a ruby library. Coffeescript and JavaScript files work everywhere, and you can read the source any time you want.
Any gotchas?
Some matchers, such as toInclude(...) and toRespondTo(...) can take multiple arguments. When they do, they have "all" semantics. For example:
expect([1,2,3,4,5]).toRespondTo('push', 'pop')
// => succeeds because arrays respond to .push and .pop
expect([1,2,3,4,5]).toInclude(2,3,4,5,6)
// => fails because 6 is not included.
Now what if you want to test the opposite?
expect([1,2,3,4,5]).not.toInclude(2,3,4,5,6)
// succeeds because it doesn't include 2, 3, 4, 5, AND 6.
If that's what you want, fine. But if what you really want is to test whether it doesn't include ANY of the arguments, you need a slightly different matcher:
expect([1,2,3,4,5]).toRespondToAny('push', 'select_sql', 'diagonalize')
// => succeeds because arrays respond to at least one of the three methods given
expect([1,2,3,4,5]).toIncludeAny(2,3,4,5,6)
// => succeeds because it includes at least one of the arguments
The opposite of an "any" matcher is a "none" matcher:
expect([1,2,3,4,5]).not.toIncludeAny(3, 6, 9)
// => fails because [1,2,3,4,5] includes a 3
expect([1,2,3,4,5]).not.toIncludeAny(6, 9, 12)
// => succeeds because [1,2,3,4,5] does not include ANY of the aarguments
Is this just for underscore stuff?
No. I also sneak in some Backbone stuff here and there, but the code works just fine even if you don't use Backbone.js. For example:
$ ->
describe 'States', ->
it 'should permit cards to be added and removed', ->
state = new State()
card = new Card()
expect(state.cards()).toBeEmpty()
state.cards().add(card)
expect(state.cards()).not.toBeEmpty()
state.cards().remove(card)
expect(state.cards()).toBeEmpty()
toBeEmpty is more than just a wrapper for _.isEmpty:
expect(
_([]).isEmpty()
).toBeTruthy() // => succeeds
expect(
_(new Backbone.Collection()).isEmpty()
).toBeTruthy() // => fails, wtf!?
expect([]).toBeEmpty()
// => succeeds
expect(new Backbone.Collection()).toBeEmpty()
// => succeeds
The same goes for collection tests like .toInclude. You can pass it a backbone collection or an array as you see fit. If you don't want that behaviour, Jasmine includes a contains() matcher that expects an array.
I'm writing a book called CoffeeScript Ristretto. Check it out!
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent