jquery/test/node_smoke_tests/lib/ensure_jquery.js

"use strict";

const assert = require( "node:assert" );

// Check if the object we got is the jQuery object by invoking a basic API.
const ensureJQuery = ( jQuery ) => {
	assert( /^jQuery/.test( jQuery.expando ),
		"jQuery.expando was not detected, the jQuery bootstrap process has failed" );
};

module.exports = { ensureJQuery };
Core: Test all factory use cases from intro.js There is a lot of logic in intro.js; now we test four cases: 1. (implicitly, via QUnit tests) A real browser with window being the global 2. Browserify where there are both global & window variables. 3. Node with jsdom where window is passed manually to the jQuery factory. 4. Pure Node with incorrect window passed; jQuery should throw then. Previously the second & fourth case was not tested and the third was tested in a way that interfered with the main test environment. We now also test if in the Browserify case we're not creating a jQuery global by default. Fixes gh-2181 Closes gh-2234 2015-04-26 17:33:05 +00:00			`"use strict";`

Build: Generate the slim build on `grunt` & run `compare_size` on it Summary of the changes: * expand `node_smoke_tests` to test the full & slim builds * run `compare_size` on all built minified files; don't run it anymore on unminified files where they don't provide lots of value The main goal of this change is to make it easier to compare sizes of both the full & slim builds between the `3.x-stable` & `main` branches. Closes gh-5291 Ref gh-5255 (partially cherry-picked from commit 8be4c0e4f89d6c8f780e5937a0534921d8c7815e) 2023-07-10 18:45:30 +00:00			`const assert = require( "node:assert" );`
Build: Refactor Node smoke tests Utilize the assert module, avoid inline JSHint comments. 2015-06-01 21:25:38 +00:00
Core: Test all factory use cases from intro.js There is a lot of logic in intro.js; now we test four cases: 1. (implicitly, via QUnit tests) A real browser with window being the global 2. Browserify where there are both global & window variables. 3. Node with jsdom where window is passed manually to the jQuery factory. 4. Pure Node with incorrect window passed; jQuery should throw then. Previously the second & fourth case was not tested and the third was tested in a way that interfered with the main test environment. We now also test if in the Browserify case we're not creating a jQuery global by default. Fixes gh-2181 Closes gh-2234 2015-04-26 17:33:05 +00:00			`// Check if the object we got is the jQuery object by invoking a basic API.`
Build: Update jsdom; migrate a test with Symbol polyfill to an iframe test So far, we've been testing that jQuery element iteration works with polyfilled Symbol & transpiled for-of via a Node test with jsdom with the Symbol global removed. Unfortunately, jsdom now requires Symbol to be present for its internal functionality so such a test is no longer possible. Instead, it's been migrated to an iframe test with transpiled JavaScript. This PR also enables us to use ECMAScript 2017 or newer in Node.js code. Closes gh-4305 2019-03-04 17:30:51 +00:00			`const ensureJQuery = ( jQuery ) => {`
Build: Refactor Node smoke tests Utilize the assert module, avoid inline JSHint comments. 2015-06-01 21:25:38 +00:00			`assert( /^jQuery/.test( jQuery.expando ),`
			`"jQuery.expando was not detected, the jQuery bootstrap process has failed" );`
Core: Test all factory use cases from intro.js There is a lot of logic in intro.js; now we test four cases: 1. (implicitly, via QUnit tests) A real browser with window being the global 2. Browserify where there are both global & window variables. 3. Node with jsdom where window is passed manually to the jQuery factory. 4. Pure Node with incorrect window passed; jQuery should throw then. Previously the second & fourth case was not tested and the third was tested in a way that interfered with the main test environment. We now also test if in the Browserify case we're not creating a jQuery global by default. Fixes gh-2181 Closes gh-2234 2015-04-26 17:33:05 +00:00			`};`
Build: Update jsdom; migrate a test with Symbol polyfill to an iframe test So far, we've been testing that jQuery element iteration works with polyfilled Symbol & transpiled for-of via a Node test with jsdom with the Symbol global removed. Unfortunately, jsdom now requires Symbol to be present for its internal functionality so such a test is no longer possible. Instead, it's been migrated to an iframe test with transpiled JavaScript. This PR also enables us to use ECMAScript 2017 or newer in Node.js code. Closes gh-4305 2019-03-04 17:30:51 +00:00
Build: Generate the slim build on `grunt` & run `compare_size` on it Summary of the changes: * expand `node_smoke_tests` to test the full & slim builds * run `compare_size` on all built minified files; don't run it anymore on unminified files where they don't provide lots of value The main goal of this change is to make it easier to compare sizes of both the full & slim builds between the `3.x-stable` & `main` branches. Closes gh-5291 Ref gh-5255 (partially cherry-picked from commit 8be4c0e4f89d6c8f780e5937a0534921d8c7815e) 2023-07-10 18:45:30 +00:00			`module.exports = { ensureJQuery };`