less confusing messages for toHaveBeenCalledWith
cover spy on on undefined method
Added toBeNaN matcher
Add JSDoc @return-tag to 'spyOn' and 'expect' functions support
code completion in Spket IDE
Merge pull request #280 from ronaldploeger/master

JSDoc @return-tag to 'spyOn' and 'expect' functions
Merge pull request #254 from jcracknell/nan-matcher

Added toBeNaN matcher
Merge pull request #225 from gunnarahlberg/master

spec that to spy on an undefined method throws exception
Merge pull request #193 from slackersoft/spy_called_with_messages

less confusing messages for toHaveBeenCalledWith
resolving issue that was identified via pivotal/jasmine#199 where RegExp objects were not properly compared resulting in non-matching RegExp objects to always return true. a patch to jasmine.Env.equals_ adds an extra step for RexExp objects to be compared.
added some specs to strengthen the coverage pivotal/jasmine#234
adding a check for the sticky regExp option supported by Firefox and accepted by the ES6. Note that the tests for this case are checking for the support of the sticky parameter. the logic is still tested by the other expect statements in browsers that do not support sticky but will never enter that block as creating a regExp with that flag is not allowed. Coverage is still good. See pivotal/jasmine#234
Merge pull request #234 from yopefonic/master

comparison for regExp that compares pattern and modifiers
When pretty-printing objects, don't include inherited properties.

When making assertions about complex objects, Jasmine's
failure message are sometimes gigantic and difficult
to read because the string representation of an object
contains all of the methods and properties in its
prototype chain. This commit causes the pretty printer
to only display on object's own properties.
Allow users to set the pretty-printer's recursion depth

Currently, jasmine's pretty printer traverses objects
to 40 levels of nesting. If an object is more deeply
nested than that, an exception is thrown. I find that
after a few levels of nesting, the output becomes
difficult to read. The process of serializing such
deep objects also sometimes crashes the browser or
causes a 'slow script' warning.

This commit exposes a 'MAX_PRETTY_PRINT_DEPTH' option.
It also causes the pretty printer to skip over
parts of an object that are nested to deeply by simply
printing out 'Object' or 'Array', rather than throwing
an exception.
Merge pull request #290 from maxbrunsfeld/smaller-pretty-print2

smaller, more configurable pretty-printing of objects
Releasing 1.3

- Allow users to set the pretty-printer's recursion depth
- When pretty-printing objects, don't include inherited properties.
- Change toBeCloseTo matcher to be more consistent
- Added toBeNaN matcher
- Add checkbox to test runner which toggles catching of exceptions duri
- Add config option which stops jasmine from capturing exceptions in a
Use jasmine-gem for jasmine-core tests
Setup Travis build
Fixing test runner failures in IE 6/7/8 whereby HtmlReporter.js bails out as we're using for (reserved keyword) as object property name. Fix is just to quote the name which allows IE6/7/8 to run the tests. I think this might also fix Issue #303 on main repo (https://github.com/pivotal/jasmine/issues/303)
Re-add pages submodule for release build script

- Use public github url