Package Exports

sinon
sinon/lib/sinon/assert
sinon/lib/sinon/collection
sinon/lib/sinon/mock
sinon/lib/sinon/sandbox
sinon/lib/sinon/spy
sinon/lib/sinon/stub
sinon/lib/sinon/test
sinon/lib/sinon/test_case
sinon/lib/sinon/util/event
sinon/lib/sinon/util/fake_xml_http_request
sinon/package.json

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (sinon) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Sinon.JS

Standalone and test framework agnostic JavaScript test spies, stubs and mocks.

Installation

via npm (node package manager)

$ sudo npm install sinon

or install via git by cloning the repository and including sinon.js in your project, as you would any other third party library.

Usage

See the sinon project homepage

Goals

No global pollution
Easy to use
Require minimal “integration”
Easy to embed seamlessly with any testing framework
Easily fake any interface
Ship with ready-to-use fakes for XMLHttpRequest, timers and more

Develop?

Check out todo.org in the project repository

Running tests on Rhino

I've added a rudimentary setup for running the tests on Rhino with env.js (as this is a fairly common test setup, Sinon should support it). The files are located in test/rhino, but there are currently quite a few test failures. I believe these are not all bugs - many are probably problems with the tests running in Rhino. Run tests from the project root (load paths depend on it):

$ java -jar js.jar -opt -1 test/rhino/run.js