- 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
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.
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.
…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 jasmine/jasmine#234
code completion in Spket IDE
…gen of gh-pages.
* bigfix/after_waitsFor: Test that show that afterEach and after are not being called when a waitsFor times out. Test that afterEach is called after a failing spec. Consolidate all waitsFor specs in the same describe block.
The current code makes the assumption that if window is undefined it is being run in an environment which supports the CommonJS Modules spec. This is not the case when Jasmine is being run in rhino or SpiderMonkey (smjs) without EnvJS. The fix is simply to check that exports is an object. Signed-off-by: Kevin Locke <email@example.com>
expected argument is optional
`example_source_tags` and `example_spec_tags` each returned what the other should have returned. I noticed this bug because it made the comments in SpecRunner.html about where to include spec and source files incongruous with the example tags that followed.
… to build it