- Having the 'empty' state for a spec result can be considered a breaking change to the reporter interface - Instead, we determine if a spec has no expectations using the added key of 'passedExpectations' in combination of the 'failedExpectations' to determine that there a spec is 'empty' [fixes #73741032]
If an async test has timed-out, there could still be some expectations that are scheduled to run after the fact in which case curerntSpec will be null. Rather than the type error that would result, we now indicate that 'expect' was used at an unexpected time. This also helps cases where an 'expect' is being used at a top-level, showing an error message in the console for this case as well. [fixes #602]
- jasmine-core can now self test with the jasmine-npm - Add node examples files - Add node_boot.js for node environment - Move jasmine-core npm packaging to .npmignore - removing src_dir and src_files from jasmine.json b/c jasmine-npm does not support requiring source files automatically.
will print out. Currently, jasmine's pretty printer will iterate over an entire array, formatting every element recursively. For very large arrays, this can crash the page, or cause a 'slow script' warning. This commit exposes a 'MAX_PRETTY_PRINT_ARRAY_LENGTH' option. If an array larger than this is encountered, recursion will stop and the array length will be printed instead e.g. "Array". The 'MAX_PRETTY_PRINT_ARRAY_LENGTH' option defaults to 100. This is length of array will not kill your browser, but will allow you to see big arrays, if you can stomach the output.