Jasmine Core 3.9 Release Notes
New features and bug fixes
Fixed Trusted Types error in
j$.isError_in Chromium-based browsers
Better reporting of unhandled promise rejections with truthy but non-
Errorreasons on Node
Env#executereturns a promise in environments that support promises
oneFailurePerSpecconfig props to
The new names are more self-explanatory and consistent with jasmine-npm. The old names are deprecated but will still work until the next major release.
boot.jsinto two files to allow the env to be configured in between
This is mainly intended to support jasmine-browser-runner, which will load a script that configures the env in between the two boot files (
boot1.js). The single-file
boot.jswill still be included until the next major release.
The Jasmine Ruby gems are deprecated. There will be no further releases after
the end of the Jasmine 3.x series. We recommend that most users migrate to the
npm package, which is the direct replacement for the
jasmine-browser-runner doesn't meet your needs, one of these might:
- The jasmine npm package to run specs in Node.js.
- The standalone distribution to run specs in browsers with no additional tools.
- The jasmine-core npm package if all
you need is the Jasmine assets. This is the direct equivalent of the
- Added API docs for
Env#hideDisableddeprecated in jsdocs
jasmine-core 3.9.0 has been tested in the following environments.
|Node||10, 12, 14, 16|
|Firefox||91, 78, 68|
|Internet Explorer||10, 11|
_Release Notes generated with Anchorman