Page MenuHomePhabricator

Error running tests

Authored By
Oct 13 2021, 11:26 AM
5 KB
Referenced Files

Error running tests

lydiakarungi@Lydias-MacBook-Pro AbuseFilter % npm run selenium-test
> @ selenium-test /Users/lydiakarungi/Desktop/outreachy/mediawiki/extensions/AbuseFilter
> wdio tests/selenium/wdio.conf.js
2021-10-13T11:23:00.328Z ERROR @wdio/config:ConfigParser: Failed loading configuration file: /Users/lydiakarungi/Desktop/outreachy/mediawiki/extensions/AbuseFilter/tests/selenium/wdio.conf.js: MW_SERVER or MW_SCRIPT_PATH not defined.
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:
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)
--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
-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
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
wdio run wdio.conf.js --spec Run scenarios by line number
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
@wdio/cli (v7.4.6)
Error: MW_SERVER or MW_SCRIPT_PATH not defined.
at Object.<anonymous> (/Users/lydiakarungi/Desktop/outreachy/mediawiki/extensions/AbuseFilter/node_modules/wdio-mediawiki/wdio-defaults.conf.js:20:8)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:93:18)
at Object.<anonymous> (/Users/lydiakarungi/Desktop/outreachy/mediawiki/extensions/AbuseFilter/tests/selenium/wdio.conf.js:3:20)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
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! /Users/lydiakarungi/.npm/_logs/2021-10-13T11_23_00_377Z-debug.log
lydiakarungi@Lydias-MacBook-Pro AbuseFilter %

File Metadata

Mime Type
text/plain; charset=utf-8
Storage Engine
Storage Format
Raw Data
Storage Handle
Default Alt Text
Error running tests (5 KB)

Event Timeline