Page MenuHomePhabricator
Paste P16643

Test verification for revisionslider
ActivePublic

Authored by Sahilgrewalhere on Jun 18 2021, 5:50 PM.
sahil@sahil-VirtualBox:~/Desktop/newmedi/mediawiki/extensions/RevisionSlider$ sudo fresh-node -env -net
# fresh: 21.04.1 (2021-04-29)
# image: docker-registry.wikimedia.org/releng/node10-test-browser:0.6.3-s2
# software: Debian GNU/Linux 9 (stretch)
# Node.js v10.15.2 (npm 6.14.5)
# Chromium 73.0.3683.75
# Mozilla Firefox 68.12.0esr
# JSDuck 5.3.4 (Ruby 2.3.3)
# mount: /RevisionSlider ➟ /home/sahil/Desktop/newmedi/mediawiki/extensions/RevisionSlider (read-write)
# /RevisionSlider/.git ➟ /home/sahil/Desktop/newmedi/mediawiki/extensions/RevisionSlider/.git (read-only)
# env: MW_*, MEDIAWIKI_* (none found)
# net: expose host
🌱 Fresh!
root@sahil-VirtualBox:/RevisionSlider# npm run selenium-test
> @ selenium-test /RevisionSlider
> wdio tests/selenium/wdio.conf.js
2021-06-18T17:35:29.989Z ERROR @wdio/config:ConfigParser: Failed loading configuration file: /RevisionSlider/tests/selenium/wdio.conf.js: MW_SERVER or MW_SCRIPT_PATH not defined.
See https://www.mediawiki.org/wiki/Selenium/How-to/Set_environment_variables
(node:20) ExperimentalWarning: The dns.promises API is experimental
(node:20) ExperimentalWarning: The fs.promises API is experimental
wdio [command]
The `wdio` command allows you run and manage your WebdriverIO test suite.
If no command is provided it calls the `run` command by default, so:
$ wdio wdio.conf.js
is the same as:
$ wdio run wdio.conf.js
For more information, visit: https://webdriver.io/docs/clioptions
Commands:
wdio config Initialize WebdriverIO and setup
configuration in your current project.
wdio install <type> <name> Add a `reporter`, `service`, or `framework`
to your WebdriverIO project. The command
installs the package from NPM, adds it to
your package.json and modifies the
wdio.conf.js accordingly.
wdio repl <option> [capabilities] Run WebDriver session in command line
wdio run <configPath> Run your WDIO configuration file to
initialize your tests. (default)
Options:
--help Show help [boolean]
--version Show version number [boolean]
--watch Run WebdriverIO in watch mode [boolean]
-h, --hostname automation driver host address [string]
-p, --port automation driver port [number]
--path path to WebDriver endpoints (default "/") [string]
-u, --user username if using a cloud service as automation backend
[string]
-k, --key corresponding access key to the user [string]
-l, --logLevel level of logging verbosity
[choices: "trace", "debug", "info", "warn", "error", "silent"]
--bail stop test runner after specific amount of tests have
failed [number]
--baseUrl shorten url command calls by setting a base url[string]
-w, --waitforTimeout timeout for all waitForXXX commands [number]
-f, --framework defines the framework (Mocha, Jasmine or Cucumber) to
run the specs [string]
-r, --reporters reporters to print out the results on stdout [array]
--suite overwrites the specs attribute and runs the defined
suite [array]
--spec run only a certain spec file - overrides specs piped
from stdin [array]
--exclude exclude certain spec file from the test run - overrides
exclude piped from stdin [array]
--mochaOpts Mocha options
--jasmineOpts Jasmine options
--cucumberOpts Cucumber options
--autoCompileOpts Auto compilation options
Examples:
wdio run wdio.conf.js --suite foobar Run suite on testsuite "foobar"
wdio run wdio.conf.js --spec Run suite on specific specs
./tests/e2e/a.js --spec ./tests/e2e/b.js
wdio run wdio.conf.js --spec Run scenario by line number
./tests/e2e/a.feature:5
wdio run wdio.conf.js --spec Run scenarios by line number
./tests/e2e/a.feature:5:10
wdio run wdio.conf.js --spec Run scenarios by line number in
./tests/e2e/a.feature:5:10 --spec single feature and another complete
./test/e2e/b.feature feature
wdio install reporter spec Install @wdio/spec-reporter
wdio repl chrome -u <SAUCE_USERNAME> -k Run repl in Sauce Labs cloud
<SAUCE_ACCESS_KEY>
Documentation: https://webdriver.io
@wdio/cli (v7.4.6)
Error: MW_SERVER or MW_SCRIPT_PATH not defined.
See https://www.mediawiki.org/wiki/Selenium/How-to/Set_environment_variables
at Object.<anonymous> (/RevisionSlider/node_modules/wdio-mediawiki/wdio-defaults.conf.js:20:8)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at Object.<anonymous> (/RevisionSlider/tests/selenium/wdio.conf.js:3:20)
at Module._compile (internal/modules/cjs/loader.js:689:30)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ selenium-test: `wdio tests/selenium/wdio.conf.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ selenium-test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /cache/_logs/2021-06-18T17_35_30_051Z-debug.log
root@sahil-VirtualBox:/RevisionSlider# npm i @wdio/cli@7.4 --save-dev
root@sahil-VirtualBox:/RevisionSlider# export MW_SERVER=http://localhost:8080
root@sahil-VirtualBox:/RevisionSlider# export MW_SCRIPT_PATH=/w
root@sahil-VirtualBox:/RevisionSlider# export MEDIAWIKI_USER=Admin
root@sahil-VirtualBox:/RevisionSlider# export MEDIAWIKI_PASSWORD=dockerpass
root@sahil-VirtualBox:/RevisionSlider# npm run selenium-test
> @ selenium-test /RevisionSlider
> wdio tests/selenium/wdio.conf.js
Execution of 8 spec files started at 2021-06-18T17:36:31.780Z
(node:52) ExperimentalWarning: The dns.promises API is experimental
(node:52) ExperimentalWarning: The fs.promises API is experimental
[0-0] (node:61) ExperimentalWarning: The dns.promises API is experimental
[0-0] (node:61) ExperimentalWarning: The fs.promises API is experimental
[0-0] RUNNING in chrome - /tests/selenium/specs/autoexpand.js
[0-0] PASSED in chrome - /tests/selenium/specs/autoexpand.js
[0-1] (node:163) ExperimentalWarning: The dns.promises API is experimental
[0-1] (node:163) ExperimentalWarning: The fs.promises API is experimental
[0-1] RUNNING in chrome - /tests/selenium/specs/difflinks.js
[0-1] PASSED in chrome - /tests/selenium/specs/difflinks.js
[0-2] (node:268) ExperimentalWarning: The dns.promises API is experimental
[0-2] (node:268) ExperimentalWarning: The fs.promises API is experimental
[0-2] RUNNING in chrome - /tests/selenium/specs/filterhighlighting.js
[0-2] PASSED in chrome - /tests/selenium/specs/filterhighlighting.js
[0-3] (node:374) ExperimentalWarning: The dns.promises API is experimental
[0-3] (node:374) ExperimentalWarning: The fs.promises API is experimental
[0-3] RUNNING in chrome - /tests/selenium/specs/help.js
[0-3] PASSED in chrome - /tests/selenium/specs/help.js
[0-4] (node:478) ExperimentalWarning: The dns.promises API is experimental
[0-4] (node:478) ExperimentalWarning: The fs.promises API is experimental
[0-4] RUNNING in chrome - /tests/selenium/specs/history.js
[0-4] PASSED in chrome - /tests/selenium/specs/history.js
[0-5] (node:581) ExperimentalWarning: The dns.promises API is experimental
[0-5] (node:581) ExperimentalWarning: The fs.promises API is experimental
[0-5] RUNNING in chrome - /tests/selenium/specs/pointers.js
[0-5] PASSED in chrome - /tests/selenium/specs/pointers.js
[0-6] (node:685) ExperimentalWarning: The dns.promises API is experimental
[0-6] (node:685) ExperimentalWarning: The fs.promises API is experimental
[0-6] RUNNING in chrome - /tests/selenium/specs/timeline.js
[0-6] PASSED in chrome - /tests/selenium/specs/timeline.js
[0-7] (node:790) ExperimentalWarning: The dns.promises API is experimental
[0-7] (node:790) ExperimentalWarning: The fs.promises API is experimental
[0-7] RUNNING in chrome - /tests/selenium/specs/tooltips.js
[0-7] PASSED in chrome - /tests/selenium/specs/tooltips.js
"dot" Reporter:
......................
Spec Files: 8 passed, 8 total (100% completed) in 00:02:08

Event Timeline