select2/tests/helpers.js

// Restore the require/define
var require = $.fn.select2.amd.require;
var define = $.fn.select2.amd.define;

// Disable jQuery's binding to $
jQuery.noConflict();

var Utils = require('select2/utils');

function MockContainer () {
  MockContainer.__super__.constructor.call(this);
}

Utils.Extend(MockContainer, Utils.Observable);

MockContainer.prototype.isOpen = function () {
  return this.isOpen;
};

define('qunit', function () {
  return QUnit;
})
Fixed missing jQuery import Now we are using `jQuery.noConflict()` in tests, so it should be slightly easier to detect when this happens next time. Tests just need to be written for the component. This closes https://github.com/select2/select2/issues/2985. 2015-01-29 16:11:18 +03:00			`// Restore the require/define`
Changed how the builds are done This adds a check that triggers an error if Select2 was not able to detect a copy of jQuery on the page. This should help users when they are setting up Select2. Breaking change: The full build no longer includes jQuery. Previously, the full build included all requirements for Select2, including jQuery, which meant that anyone looking for the optional requirements had to possibly include multiple versions of jQuery on their page. This means that anyone requiring Select2 to also bundle jQuery will now need to include jQuery on their pages alongside Select2. A copy of jQuery is included in the repository. Breaking change: The AMD build of Select2 will now correctly wrap the code in a `define` block. It will still create the named blocks inside of the code, which should be valid in most AMD build systems, so now Select2 is compatible with cases where the file does not have the same name as the Select2 module name. Breaking change: Select2 will re-use the AMD methods if they are available on the page, but it will not longer leak the included AMD loader to the global scope. The AMD methods will still be available on the `jQuery.fn.select2.amd` namespace. The `mock.js` test file has been renamed to `helpers.js` and will handle the escalation of the `require` and `define` variables to the global scope. It should be included in all test files, or the tests will fail. This closes https://github.com/select2/select2/issues/2946. 2015-01-22 22:49:39 +03:00			`var require = $.fn.select2.amd.require;`
			`var define = $.fn.select2.amd.define;`

Fixed missing jQuery import Now we are using `jQuery.noConflict()` in tests, so it should be slightly easier to detect when this happens next time. Tests just need to be written for the component. This closes https://github.com/select2/select2/issues/2985. 2015-01-29 16:11:18 +03:00			`// Disable jQuery's binding to $`
			`jQuery.noConflict();`

Added `selectOnClose` `selectOnClose` is a new option which works very much like the old `selectOnBlur` option. When the `close` event is triggered, the highlighted result is automatically selected. This is useful for single selects, which is where it is designed to be used, but it can also be used on multiple selects. This also adds tests to verify that this works in the future. During the creation of the test, we noticed that we were missing a mock container that could be used for triggering events. One was created and a general mock JS file was created to hold any future mocks for tests. 2015-01-12 05:47:17 +03:00			`var Utils = require('select2/utils');`

			`function MockContainer () {`
			`MockContainer.__super__.constructor.call(this);`
			`}`

			`Utils.Extend(MockContainer, Utils.Observable);`

			`MockContainer.prototype.isOpen = function () {`
			`return this.isOpen;`
			`};`
Hook up with SauceLabs This sets up Select2 to be able to run tests on the SauceLabs environment. This will allow us to run the tests on different browsers in the future, though at the moment we need to start combining test files. This required adding a snippet of code for reporting QUnit test results to SauceLabs within the global test helper file. The tests currently cannot be run on IE 8 because all of the tests are using jQuery 2.x, which is not compatible. 2015-02-14 05:55:04 +03:00
Update grunt-contrib-qunit to latest version (#5530) We needed to define the `qunit` module in the unit tests because there was a change in grunt-contrib-qunit 0.6.0 that breaks when you define an AMD loader. It expects that the AMD loader is also used to load QUnit, instead of just being used to support the tests, so if you don't define the qunit module it will just hang and do nothing. Luckily we have the helpers file to help us out here, since it allows us to globally define this module. 2019-06-05 05:43:52 +03:00			`define('qunit', function () {`
			`return QUnit;`
			`})`