summaryrefslogtreecommitdiff
path: root/karma.conf.js
Commit message (Collapse)AuthorAgeFilesLines
* Remove legacy conversion of modulesPierre Ossman2020-10-151-10/+7
| | | | | | | We no longer support Internet Explorer so we can now require that browsers support modules. Some conversion to commonjs still remains for nodejs.
* Use GitHub actions instead of Travis/Sauce LabsPierre Ossman2020-06-231-58/+20
| | | | | | The ability to use Sauce Labs for pull requests has now stopped working, as Travis warned about several years ago. Instead run our tests directly on GitHub on their various virtual machines.
* Remove default Karma optionsPierre Ossman2020-06-231-8/+0
| | | | No need to mention things where we already use the default value.
* Stop transpiling karma testsPierre Ossman2018-07-161-22/+3
| | | | | | This runs our code in the same manner as it would be used if loaded directly in the browser. Includes the same kind of fallback for older browsers.
* Move sinon to karma frameworkPierre Ossman2018-07-131-3/+1
| | | | | This frees us from manual imports, and makes things less magical as those aren't ES modules even if the code suggest that the are.
* Use fat arrow functions `const foo = () => { ... };` for callbacksJuanjo Diaz2018-07-121-1/+1
| | | | and any other function that is passed around and it's not a top level function
* Stop combining test platformsPierre Ossman2018-06-011-3/+0
| | | | | Sauce is very unstable, so spread things out so we can more easily throttle things to more sane levels.
* Add transpilation for IE11 and skip linux testsJuanjo Diaz2018-05-241-18/+20
|
* Use localstorage only to initialize settings mapAndrew Webster2018-02-131-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This only reads from localstorage in order to initialize the settings map. After initializaton, reads will return the value from the map. When writing a value, the settings map and the local storage are updated, unless the setting is a default value or derived from the query string. This has a few advantages: 1. Saved settings will not be overridden by settings specified in the query string. This means a setting could be temporarily changed using the query string, but once removed from the query string, the setting would return back to what the user selected. 2. Default values will not be saved. If a user has always used the default value for a setting, then they can move to a new version with different defaults without clearing localstorage. 3. Changes made to localstorage in a session running in a different window will not affect the settings in the current window (until the page is refreshed). Regarding eraseSetting: It is possible that another tab could change the value, leading to an unexpected value change in the tab that deletes. However, this function is currently unused, so this will be evaluted if and when it used.
* Move localization.js to appSamuel Mannehed2017-11-141-0/+2
| | | | | Since it is no longer used in core. Also splits localization tests into a separate file.
* Fix Travis-Sauce Connectioninfra/fix-travis-sauceSolly Ross2017-06-051-1/+2
| | | | | | | Somethings got messed up in the Travis-Sauce tunnel setup. This should fix it by re-adding the Sauce credentials. It also updates the config to explicitly pass auth information instead of via environment variables.
* Update tests to work with new structureSolly Ross2017-03-211-73/+26
| | | | | | | | | | | This updates the tests to work with the new structure, and removes the old `utils/run_from_console.js` files in favor of just using Karma directly. The Karma debug page now displays the normal mocha HTML, so we can use that instead of the HTML generation functionality of the old test runner. Note that PhantomJS does not work at the moment (PhantomJS 1.5 should make it possible to test on PhantomJS again).
* Move input-related files into core/inputSolly Ross2016-09-161-5/+5
| | | | | | This commit moves all the input-related files from `core/` to `core/input/`, and renames a couple as relevant (input.js --> input/devices.js, keyboard.js --> input/util.js).
* Enable noVNC to become BrowserifiableSolly Ross2016-09-161-15/+15
| | | | | | This commit restructures noVNC, splitting it into the core directory and the app directory, with the former containing core noVNC parts, and the latter containing parts specific to the application.
* QEMU RFB extension - new file xtscancodes.jsDaniel Henrique Barboza2016-08-261-0/+1
| | | | | | | This new file contains the XT scancode mapping that the extension will use in rfb.js file. Signed-off-by: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
* WIP: Switch to Pako for zlibSolly Ross2015-08-061-1/+1
| | | | | This commit introduces an alternate implementation of the zlib decompressor based on Pako (https://github.com/nodeca/pako).
* Launch Sauce Connect through TravisSolly Ross2015-02-271-1/+1
| | | | | This commit makes Travis launch sauce connect, instead of using karma to start Sauce Connect
* Increase Karma-Sauce Connector TimeoutSolly Ross2015-02-271-1/+4
| | | | | | This commit increases the browserNoActivityTimeout to 100s (from the default of 10s) in an attempt to alliviate the timeout issues that we are seeing.
* Fix Travis Sauce Tunnel IssuesSolly Ross2014-09-191-0/+2
| | | | | | Travis is failing because Sauce can't find the appropriate tunnelid. This should fix that but setting the tunnel id to be the Travis job number.
* Fixed assertion collision issuesSolly Ross2014-09-191-0/+1
| | | | | | | | | | | | | | When run via karma, all the tests are loaded into the same page. This was causing a collision in the 'displayed' assertion dealing with using viewportLoc. The assertions are now in their own file, pulled in by tests that need them. Additionally, several tests which only set fb_width and fb_height were correct to set viewportLoc as well. Closes #392 Also-Authored-By: Martin André (github: mandre)
* Add support for Travis CI and SauceLabs TestingSolly Ross2014-09-151-0/+191
This adds support for Travis CI and SauceLabs testing. Testing on SauceLabs in done via the Karma test runner. Note that encrypted Sauce username and access key values need to be inserted into .travis.yml as global environment variables. Additionally, the local test runner (which is still useful for debugging tests and code) was updated to reflect that the 'node_modules' folder now gets placed in the root directory.
View Lorry Controller Status