f12f4395f0
* Top level private APIs (e.g. jasmine.private.whatever) are no longer exposed * jasmineRequire is no longer exposed * core is self-booting * Globals are automatically created in browsers. (They can subsequently be removed by user code if desired.) * Globals are *not* automatically created in Node. An installGlobals function is exported instead. The jasmine package calls installGlobals unless configured not to do so. * In Node, the same instance is returned each time jasmine-core is imported. A reset function is exported. It effectively resets all state by discarding the env and creating a new one. This allows mulitple sequential runs within the same process to be independent of each other, but does not allow multiple concurrent runs. (That probably never worked anyway.) Fixes #2094
12 lines
495 B
JavaScript
12 lines
495 B
JavaScript
(function() {
|
|
// By the time onload is called, getJasmineRequireObj() and
|
|
// getJasmineHtmlRequireObj() will be redefined to point
|
|
// to the Jasmine source files (and not jasmine.js). So re-require.
|
|
const jasmineRequire = getJasmineRequireObj();
|
|
const coreUnderTest = jasmineRequire.core(jasmineRequire);
|
|
window.jasmineUnderTest = coreUnderTest.jasmine;
|
|
window.privateUnderTest = coreUnderTest.private;
|
|
|
|
getJasmineHtmlRequireObj().html(jasmineUnderTest, privateUnderTest);
|
|
})();
|