Hopiu/fabric.js
1
0
Fork 0
mirror of https://github.com/Hopiu/fabric.js.git synced 2026-05-17 02:01:05 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
fabric.js/testem.json

34 lines
619 B
JSON
Raw Normal View History

Introduced testem test runner (#3327) * Introduced testem test runner. Install testem via 'npm install -g testem' Run testem via 'testem' * Fixed fixture image paths in tests
2016-10-05 07:12:26 +00:00
{
Fix testem runner, and further improvements (#4593) * Switched qunit dependency to npm * Fixed testem not working * Switched test.js build to use node-qunit. As stated in the QUnit docs: The qunit package prior to 2.4.1 is an alternative CLI that is now published as node-qunit. * Introduced qunit 2.4.1, with an npm script for running node tests * Switched testem page fixture to use qunit package instead of qunitjs * Configured testem to run in headless mode, and use new npm node test script for "Node" launcher configuration. This means that individual tests will show up in testem output via the the `tap` test protocol. * Made canvas_static 'toDataURL cropping' test asynchronous. * Configured QUnit testTimeout and enabled 'noglobals' config * Updated .travis.yml config to do cross-browser/env testing via Testem * Specify qunit binary directly to fix confict with binary from node-qunit * Avoid test hanging by aborting the animated cursor * Firefox test fix, and enabled in Testem config
2017-12-31 08:51:07 +00:00
"framework": "qunit",
Introduced testem test runner (#3327) * Introduced testem test runner. Install testem via 'npm install -g testem' Run testem via 'testem' * Fixed fixture image paths in tests
2016-10-05 07:12:26 +00:00
"serve_files": [
"dist/fabric.js",
"test/unit/*.js"
],
Fix testem runner, and further improvements (#4593) * Switched qunit dependency to npm * Fixed testem not working * Switched test.js build to use node-qunit. As stated in the QUnit docs: The qunit package prior to 2.4.1 is an alternative CLI that is now published as node-qunit. * Introduced qunit 2.4.1, with an npm script for running node tests * Switched testem page fixture to use qunit package instead of qunitjs * Configured testem to run in headless mode, and use new npm node test script for "Node" launcher configuration. This means that individual tests will show up in testem output via the the `tap` test protocol. * Made canvas_static 'toDataURL cropping' test asynchronous. * Configured QUnit testTimeout and enabled 'noglobals' config * Updated .travis.yml config to do cross-browser/env testing via Testem * Specify qunit binary directly to fix confict with binary from node-qunit * Avoid test hanging by aborting the animated cursor * Firefox test fix, and enabled in Testem config
2017-12-31 08:51:07 +00:00
"routes": {
"/fixtures": "test/fixtures"
},
"test_page": "tests.mustache?hidepassed&hideskipped&timeout=60000",
"browser_args": {
"Chrome": [ "--headless", "--disable-gpu", "--remote-debugging-port=9222" ],
"Firefox": [ "--headless" ]
},
Introduced testem test runner (#3327) * Introduced testem test runner. Install testem via 'npm install -g testem' Run testem via 'testem' * Fixed fixture image paths in tests
2016-10-05 07:12:26 +00:00
"launch_in_dev": [
Fix testem runner, and further improvements (#4593) * Switched qunit dependency to npm * Fixed testem not working * Switched test.js build to use node-qunit. As stated in the QUnit docs: The qunit package prior to 2.4.1 is an alternative CLI that is now published as node-qunit. * Introduced qunit 2.4.1, with an npm script for running node tests * Switched testem page fixture to use qunit package instead of qunitjs * Configured testem to run in headless mode, and use new npm node test script for "Node" launcher configuration. This means that individual tests will show up in testem output via the the `tap` test protocol. * Made canvas_static 'toDataURL cropping' test asynchronous. * Configured QUnit testTimeout and enabled 'noglobals' config * Updated .travis.yml config to do cross-browser/env testing via Testem * Specify qunit binary directly to fix confict with binary from node-qunit * Avoid test hanging by aborting the animated cursor * Firefox test fix, and enabled in Testem config
2017-12-31 08:51:07 +00:00
"Chrome",
"Node",
"Firefox"
],
"launch_in_ci": [
"Chrome",
"Node",
"Firefox"
Introduced testem test runner (#3327) * Introduced testem test runner. Install testem via 'npm install -g testem' Run testem via 'testem' * Fixed fixture image paths in tests
2016-10-05 07:12:26 +00:00
],
"launchers": {
"Node": {
removed old test setup (#5070) * removed ol dep * no build
2018-06-26 10:52:25 +00:00
"command": "npm run test",
Fix testem runner, and further improvements (#4593) * Switched qunit dependency to npm * Fixed testem not working * Switched test.js build to use node-qunit. As stated in the QUnit docs: The qunit package prior to 2.4.1 is an alternative CLI that is now published as node-qunit. * Introduced qunit 2.4.1, with an npm script for running node tests * Switched testem page fixture to use qunit package instead of qunitjs * Configured testem to run in headless mode, and use new npm node test script for "Node" launcher configuration. This means that individual tests will show up in testem output via the the `tap` test protocol. * Made canvas_static 'toDataURL cropping' test asynchronous. * Configured QUnit testTimeout and enabled 'noglobals' config * Updated .travis.yml config to do cross-browser/env testing via Testem * Specify qunit binary directly to fix confict with binary from node-qunit * Avoid test hanging by aborting the animated cursor * Firefox test fix, and enabled in Testem config
2017-12-31 08:51:07 +00:00
"protocol": "tap"
Introduced testem test runner (#3327) * Introduced testem test runner. Install testem via 'npm install -g testem' Run testem via 'testem' * Fixed fixture image paths in tests
2016-10-05 07:12:26 +00:00
}
},
"timeout": 540,
"parallel": 4
}
Reference in a new issue Copy permalink