2014-01-31 02:03:11 +00:00
|
|
|
{
|
2015-09-26 13:32:06 +00:00
|
|
|
"private": true,
|
2014-01-31 02:03:11 +00:00
|
|
|
"scripts": {
|
2020-01-13 16:46:08 +00:00
|
|
|
"api-testing": "npm run api-testing-lint && mocha --timeout 0 --recursive tests/api-testing",
|
|
|
|
|
"api-testing-lint": "eslint --cache --max-warnings 0 tests/api-testing/**",
|
2019-01-23 23:51:49 +00:00
|
|
|
"build": "grunt minify",
|
|
|
|
|
"test": "grunt lint",
|
2017-11-22 18:48:27 +00:00
|
|
|
"qunit": "grunt qunit",
|
2015-03-08 17:34:06 +00:00
|
|
|
"doc": "jsduck",
|
2016-12-19 16:39:29 +00:00
|
|
|
"postdoc": "grunt copy:jsduck",
|
selenium: Replace wdio-chromedriver with ./selenium.sh script
This package was serving two purposes:
* Install chromedriver automatically.
* Start chromedriver automatically when using the
'npm run selenium' entry point (e.g. for local development).
For the CI entry points (selenium-test, selenium-daily) the
chromedriver is skipped. For those, we expect the CI runner to
have started a chromedriver server already, which allows the
server to continue running between different the test suites
of different extensions etc.
By letting WDIO start the chromedriver for local development,
we had the benefit of 'npm run selenium' directly being an alias
to the 'wdio' command. This made it easy to pass additional
arguments like --spec or --mochaOpts for running specific tests
only and overall makes things easier to reason about from a
developer perspective with fewer (required) layers of
indirection you see and need to understand when debugging.
But, this has also caused problems. Specifically, it means
developers have to use the same version of Chrome locally
as we specify in package.json which isn't very flexible. While
we could try to keep this up-to-date roughly, that too isn't
an option because the secure environments we recommend for local
use (Quibble and Fresh-node) both use a Debian distro with
typically older versions of Chromium than your local auto-updating
Google Chrome.
For now, let's go back to moving the responsibility of installing
chromedriver together with the responsibility to install Chrome
itself.
== Changes ==
For CI, nothing changes (it already installs both).
For developers using Quibble, Vagrant or Fresh nothing changes
(already installs both).
For developers who make their own secure environment, they will
need to make sure chromedriver is installed, just as we required
between 2017 and Aug 2019 before my commit 1955a8aa56.
== How ==
wdio-chromedriver cannot start a foreign install because the
protocol can change between versions, so unfortunately together
with not using chromedriver from npm, we also can't use
the wdio-chromedriver autostart mechanism. Instead, I'm bringing
back Antoine's shell script that did this prior to ebda397c5450.
But, with a few tweaks so that it forwards shell arguments,
this way developers continue to enjoy the benefit of 1955a8aa56,
which is that 'npm run selenium -- --spec foo.js' works.
Bug: T234610
Change-Id: I03ca94315d0611d2b6abccc12cf9076d41b2c00e
2019-12-17 17:35:47 +00:00
|
|
|
"selenium": "./tests/selenium/selenium.sh",
|
2019-06-03 17:58:18 +00:00
|
|
|
"selenium-daily": "npm run selenium-test -- --mochaOpts.grep @daily",
|
selenium: Replace wdio-chromedriver with ./selenium.sh script
This package was serving two purposes:
* Install chromedriver automatically.
* Start chromedriver automatically when using the
'npm run selenium' entry point (e.g. for local development).
For the CI entry points (selenium-test, selenium-daily) the
chromedriver is skipped. For those, we expect the CI runner to
have started a chromedriver server already, which allows the
server to continue running between different the test suites
of different extensions etc.
By letting WDIO start the chromedriver for local development,
we had the benefit of 'npm run selenium' directly being an alias
to the 'wdio' command. This made it easy to pass additional
arguments like --spec or --mochaOpts for running specific tests
only and overall makes things easier to reason about from a
developer perspective with fewer (required) layers of
indirection you see and need to understand when debugging.
But, this has also caused problems. Specifically, it means
developers have to use the same version of Chrome locally
as we specify in package.json which isn't very flexible. While
we could try to keep this up-to-date roughly, that too isn't
an option because the secure environments we recommend for local
use (Quibble and Fresh-node) both use a Debian distro with
typically older versions of Chromium than your local auto-updating
Google Chrome.
For now, let's go back to moving the responsibility of installing
chromedriver together with the responsibility to install Chrome
itself.
== Changes ==
For CI, nothing changes (it already installs both).
For developers using Quibble, Vagrant or Fresh nothing changes
(already installs both).
For developers who make their own secure environment, they will
need to make sure chromedriver is installed, just as we required
between 2017 and Aug 2019 before my commit 1955a8aa56.
== How ==
wdio-chromedriver cannot start a foreign install because the
protocol can change between versions, so unfortunately together
with not using chromedriver from npm, we also can't use
the wdio-chromedriver autostart mechanism. Instead, I'm bringing
back Antoine's shell script that did this prior to ebda397c5450.
But, with a few tweaks so that it forwards shell arguments,
this way developers continue to enjoy the benefit of 1955a8aa56,
which is that 'npm run selenium -- --spec foo.js' works.
Bug: T234610
Change-Id: I03ca94315d0611d2b6abccc12cf9076d41b2c00e
2019-12-17 17:35:47 +00:00
|
|
|
"selenium-test": "wdio ./tests/selenium/wdio.conf.js"
|
2014-01-31 02:03:11 +00:00
|
|
|
},
|
|
|
|
|
"devDependencies": {
|
2019-09-27 03:08:00 +00:00
|
|
|
"@wdio/cli": "5.13.2",
|
|
|
|
|
"@wdio/devtools-service": "5.13.2",
|
|
|
|
|
"@wdio/dot-reporter": "5.13.2",
|
|
|
|
|
"@wdio/junit-reporter": "5.13.2",
|
|
|
|
|
"@wdio/local-runner": "5.13.2",
|
|
|
|
|
"@wdio/mocha-framework": "5.13.2",
|
|
|
|
|
"@wdio/sauce-service": "5.13.2",
|
|
|
|
|
"@wdio/sync": "5.13.2",
|
2020-01-13 16:46:08 +00:00
|
|
|
"api-testing": "1.0.3",
|
2019-10-23 10:22:41 +00:00
|
|
|
"eslint-config-wikimedia": "0.15.0",
|
2020-02-03 23:54:11 +00:00
|
|
|
"eslint-plugin-vue": "^6.1.2",
|
2019-04-30 20:25:38 +00:00
|
|
|
"grunt": "1.0.4",
|
2019-10-23 10:22:41 +00:00
|
|
|
"grunt-banana-checker": "0.8.1",
|
2016-03-17 19:45:21 +00:00
|
|
|
"grunt-contrib-copy": "1.0.0",
|
2018-06-15 11:46:46 +00:00
|
|
|
"grunt-contrib-watch": "1.1.0",
|
2019-10-23 10:22:41 +00:00
|
|
|
"grunt-eslint": "22.0.0",
|
2019-05-21 21:26:41 +00:00
|
|
|
"grunt-karma": "3.0.2",
|
2019-10-23 10:22:41 +00:00
|
|
|
"grunt-stylelint": "0.12.0",
|
2019-02-07 05:53:50 +00:00
|
|
|
"grunt-svgmin": "5.0.0",
|
2019-05-10 14:25:24 +00:00
|
|
|
"jpeg-js": "0.3.5",
|
2020-02-03 21:25:49 +00:00
|
|
|
"karma": "4.4.1",
|
|
|
|
|
"karma-chrome-launcher": "3.1.0",
|
|
|
|
|
"karma-firefox-launcher": "1.3.0",
|
2017-10-25 19:53:56 +00:00
|
|
|
"karma-mocha-reporter": "2.2.5",
|
2020-02-03 21:25:49 +00:00
|
|
|
"karma-qunit": "4.0.0",
|
2018-09-05 15:14:54 +00:00
|
|
|
"postcss-less": "2.0.0",
|
2020-02-03 21:25:49 +00:00
|
|
|
"qunit": "2.9.3",
|
2019-10-23 10:22:41 +00:00
|
|
|
"stylelint-config-wikimedia": "0.7.0",
|
2018-05-02 17:48:24 +00:00
|
|
|
"wdio-mediawiki": "file:tests/selenium/wdio-mediawiki",
|
2019-09-27 03:08:00 +00:00
|
|
|
"webdriverio": "5.13.2"
|
2014-01-31 02:03:11 +00:00
|
|
|
}
|
|
|
|
|
}
|
