1 | # should.js
|
2 |
|
3 | [![Join the chat at https://gitter.im/shouldjs/should.js](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/shouldjs/should.js)
|
4 |
|
5 | [![Build Status](https://travis-ci.org/shouldjs/should.js.svg?branch=master)](https://travis-ci.org/shouldjs/should.js)
|
6 |
|
7 | [![Selenium Test Status](https://saucelabs.com/browser-matrix/shouldjs.svg)](https://saucelabs.com/u/shouldjs)
|
8 |
|
9 | _should_ is an expressive, readable, framework-agnostic assertion library. The main goals of this library are __to be expressive__ and __to be helpful__. It keeps your test code clean, and your error messages helpful.
|
10 |
|
11 | By default (when you `require('should')`) _should_ extends the `Object.prototype` with a single non-enumerable getter that allows you to express how that object should behave. It also returns itself when required with `require`.
|
12 |
|
13 | It is also possible to use should.js without getter (it will not even try to extend Object.prototype), just `require('should/as-function')`. Or if you already use version that auto add getter, you can call `.noConflict` function.
|
14 |
|
15 | **Results of `(something).should` getter and `should(something)` in most situations are the same**
|
16 |
|
17 | ### Upgrading instructions
|
18 |
|
19 | Please check [wiki page](https://github.com/shouldjs/should.js/wiki/Breaking-changes) for upgrading instructions.
|
20 |
|
21 | ### FAQ
|
22 |
|
23 | You can take look in [FAQ](https://github.com/shouldjs/should.js/wiki/FAQ).
|
24 |
|
25 | ## Example
|
26 | ```javascript
|
27 | var should = require('should');
|
28 |
|
29 | var user = {
|
30 | name: 'tj'
|
31 | , pets: ['tobi', 'loki', 'jane', 'bandit']
|
32 | };
|
33 |
|
34 | user.should.have.property('name', 'tj');
|
35 | user.should.have.property('pets').with.lengthOf(4);
|
36 |
|
37 | // If the object was created with Object.create(null)
|
38 | // then it doesn't inherit `Object.prototype`, so it will not have `.should` getter
|
39 | // so you can do:
|
40 | should(user).have.property('name', 'tj');
|
41 |
|
42 | // also you can test in that way for null's
|
43 | should(null).not.be.ok();
|
44 |
|
45 | someAsyncTask(foo, function(err, result){
|
46 | should.not.exist(err);
|
47 | should.exist(result);
|
48 | result.bar.should.equal(foo);
|
49 | });
|
50 | ```
|
51 | ## To begin
|
52 |
|
53 | 1. Install it:
|
54 |
|
55 | ```bash
|
56 | $ npm install should --save-dev
|
57 | ```
|
58 |
|
59 | 2. Require it and use:
|
60 |
|
61 | ```js
|
62 | var should = require('should');
|
63 |
|
64 | (5).should.be.exactly(5).and.be.a.Number();
|
65 | ```
|
66 |
|
67 | ```js
|
68 | var should = require('should/as-function');
|
69 |
|
70 | should(10).be.exactly(5).and.be.a.Number();
|
71 | ```
|
72 |
|
73 | 3. For TypeScript users:
|
74 |
|
75 | ```js
|
76 | import * as should from 'should';
|
77 |
|
78 | (0).should.be.Number();
|
79 | ```
|
80 |
|
81 | ## In browser
|
82 |
|
83 | Well, even when browsers by complaints of authors have 100% es5 support, it does not mean it has no bugs. Please see [wiki](https://github.com/shouldjs/should.js/wiki/Known-Bugs) for known bugs.
|
84 |
|
85 | If you want to use _should_ in browser, use the `should.js` file in the root of this repository, or build it yourself. To build a fresh version:
|
86 |
|
87 | ```bash
|
88 | $ npm install
|
89 | $ npm run browser
|
90 | ```
|
91 |
|
92 | The script is exported to `window.should`:
|
93 |
|
94 | ```js
|
95 | should(10).be.exactly(10)
|
96 | ```
|
97 |
|
98 | You can easy install it with npm or bower:
|
99 |
|
100 | ```sh
|
101 | npm install should -D
|
102 | # or
|
103 | bower install shouldjs/should.js
|
104 | ```
|
105 |
|
106 | ## API docs
|
107 |
|
108 | Actual api docs generated by jsdoc comments and available at [http://shouldjs.github.io](http://shouldjs.github.io).
|
109 |
|
110 | ## Usage examples
|
111 |
|
112 | Please look on usage in [examples](https://github.com/shouldjs/examples)
|
113 |
|
114 | ## .not
|
115 |
|
116 | `.not` negates the current assertion.
|
117 |
|
118 | ## .any
|
119 |
|
120 | `.any` allow for assertions with multiple parameters to assert any of the parameters (but not all). This is similar to the native JavaScript [array.some](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/some).
|
121 |
|
122 | # Assertions
|
123 | ## chaining assertions
|
124 |
|
125 | Every assertion will return a `should.js`-wrapped Object, so assertions can be chained.
|
126 | To help chained assertions read more clearly, you can use the following helpers anywhere in your chain: `.an`, `.of`, `.a`, `.and`, `.be`, `.have`, `.with`, `.is`, `.which`. Use them for better readability; they do nothing at all.
|
127 | For example:
|
128 | ```js
|
129 | user.should.be.an.instanceOf(Object).and.have.property('name', 'tj');
|
130 | user.pets.should.be.instanceof(Array).and.have.lengthOf(4);
|
131 | ```
|
132 | Almost all assertions return the same object - so you can easy chain them. But some (eg: `.length` and `.property`) move the assertion object to a property value, so be careful.
|
133 |
|
134 | ## Adding own assertions
|
135 |
|
136 | Adding own assertion is pretty easy. You need to call `should.Assertion.add` function. It accept 2 arguments:
|
137 |
|
138 | 1. name of assertion method (string)
|
139 | 2. assertion function (function)
|
140 |
|
141 | What assertion function should do. It should check only positive case. `should` will handle `.not` itself.
|
142 | `this` in assertion function will be instance of `should.Assertion` and you **must** define in any way this.params object
|
143 | in your assertion function call before assertion check happen.
|
144 |
|
145 | `params` object can contain several fields:
|
146 |
|
147 | - `operator` - it is string which describe your assertion
|
148 | - `actual` it is actual value, you can assume it is your own this.obj if you need to define you own
|
149 | - `expected` it is any value that expected to be matched this.obj
|
150 |
|
151 | You can assume its usage in generating AssertionError message like: expected `obj`? || this.obj not? `operator` `expected`?
|
152 |
|
153 | In `should` sources appeared 2 kinds of usage of this method.
|
154 |
|
155 | First not preferred and used **only** for shortcuts to other assertions, e.g how `.should.be.true()` defined:
|
156 |
|
157 | ```javascript
|
158 | Assertion.add('true', function() {
|
159 | this.is.exactly(true);
|
160 | });
|
161 | ```
|
162 | There you can see that assertion function do not define own `this.params` and instead call within the same assertion `.exactly`
|
163 | that will fill `this.params`. **You should use this way very carefully, but you can use it**.
|
164 |
|
165 | Second way preferred and i assume you will use it instead of first.
|
166 |
|
167 | ```javascript
|
168 | Assertion.add('true', function() {
|
169 | this.params = { operator: 'to be true', expected: true };
|
170 |
|
171 | should(this.obj).be.exactly(true);
|
172 | });
|
173 | ```
|
174 | in this case this.params defined and then used new assertion context (because called `.should`). Internally this way does not
|
175 | create any edge cases as first.
|
176 |
|
177 | ```javascript
|
178 | Assertion.add('asset', function() {
|
179 | this.params = { operator: 'to be asset' };
|
180 |
|
181 | this.obj.should.have.property('id').which.is.a.Number();
|
182 | this.obj.should.have.property('path');
|
183 | })
|
184 |
|
185 | //then
|
186 | > ({ id: '10' }).should.be.an.asset();
|
187 | AssertionError: expected { id: '10' } to be asset
|
188 | expected '10' to be a number
|
189 |
|
190 | > ({ id: 10 }).should.be.an.asset();
|
191 | AssertionError: expected { id: 10 } to be asset
|
192 | expected { id: 10 } to have property path
|
193 | ```
|
194 |
|
195 | ## Additional projects
|
196 |
|
197 | * [`should-sinon`](https://github.com/shouldjs/sinon) - adds additional assertions for sinon.js
|
198 | * [`should-immutable`](https://github.com/shouldjs/should-immutable) - extends different parts of should.js to make immutable.js first-class citizen in should.js
|
199 | * [`should-http`](https://github.com/shouldjs/http) - adds small assertions for assertion on http responses for node only
|
200 | * [`should-jq`](https://github.com/shouldjs/jq) - assertions for jq (need maintainer)
|
201 | * [`karma-should`](https://github.com/seegno/karma-should) - make more or less easy to work karma with should.js
|
202 | * [`should-spies`](https://github.com/shouldjs/spies) - small and dirty simple zero dependencies spies
|
203 |
|
204 |
|
205 | ## Contributions
|
206 |
|
207 | [Actual list of contributors](https://github.com/visionmedia/should.js/graphs/contributors) if you want to show it your friends.
|
208 |
|
209 | To run the tests for _should_ simply run:
|
210 |
|
211 | $ npm test
|
212 |
|
213 | See also [CONTRIBUTING](./CONTRIBUTING.md).
|
214 |
|
215 | ## OMG IT EXTENDS OBJECT???!?!@
|
216 |
|
217 | Yes, yes it does, with a single getter _should_, and no it won't break your code, because it does this **properly** with a non-enumerable property.
|
218 |
|
219 | Also it is possible use it without extension. Just use `require('should/as-function')` everywhere.
|
220 |
|
221 | ## License
|
222 |
|
223 | MIT. See LICENSE for details.
|