This is required for using jasmine-given with the reporter, as that library
sets expectations on jasmine.Specs themselves. When the Spec is stringified
as JSON, it ends up stringifying the entire Jasmine environment, including
previous ExpectationResults. Since those previous ExpectationResults have had
their "expected" values stringified, they may include stringified Specs
themselves. This leds to exponential growth in the size of stringified Specs.
Special-casing jasmine.Spec prevents the exponential growth by short-circuting
the value to a small, still-useful String.
The logic which was in place to convert array-like objects to arrays
prevented the circular reference detection to work properly for arrays
and array-like objects.
(These changes does not applyed for verbose level)
Before:
should not pass: failed
should not pass: failed
should not pass: failed
Now:
.....x.x.x.
Failed level 1:: should not pass: failed
Expected true to be false. (1)
Failed level 1:: Level 2:: Level 3:: should not pass: failed
Expected true to be false. (3)
Failed level 1:: Level 2:: Level 3:: Level 4:: should not pass: failed
ReferenceError: Can't find variable: asdf in file:///grunt-contrib-jasmine/test/fixtures/pivotal/spec/PlayerSpec.js (line 85) (1)
Passing console.log from browser to verbose grunt logging
Support for templates as separate node modules
Removed internal requirejs template (see grunt-template-jasmine-requirejs)
General refactor
