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
28 lines
834 B
JavaScript
28 lines
834 B
JavaScript
'use strict';
|
|
|
|
(function() {
|
|
const env = jasmine.getEnv();
|
|
const urls = new jasmine.HtmlReporterV2Urls();
|
|
|
|
/**
|
|
* Configures Jasmine based on the current set of query parameters. This
|
|
* supports all parameters set by the HTML reporter as well as
|
|
* spec=partialPath, which filters out specs whose paths don't contain the
|
|
* parameter.
|
|
*/
|
|
env.configure(urls.configFromCurrentUrl());
|
|
|
|
const currentWindowOnload = window.onload;
|
|
window.onload = function() {
|
|
if (currentWindowOnload) {
|
|
currentWindowOnload();
|
|
}
|
|
|
|
// The HTML reporter needs to be set up here so it can access the DOM. Other
|
|
// reporters can be added at any time before env.execute() is called.
|
|
const htmlReporter = new jasmine.HtmlReporterV2({ env, urls });
|
|
env.addReporter(htmlReporter);
|
|
env.execute();
|
|
};
|
|
})();
|