wiki.techinc.nl/tests/selenium
2019-10-08 21:45:33 +00:00
..
pageobjects selenium: Fix more inefficient MWBot use and simplify wdio-mediawiki Api 2019-10-04 18:16:28 +01:00
specs Disable flaky Selenium test 2019-10-08 20:50:37 +00:00
wdio-mediawiki selenium: Fix more inefficient MWBot use and simplify wdio-mediawiki Api 2019-10-04 18:16:28 +01:00
.eslintrc.json eslint: Use correct global values, and use jquery rules in selenium tests 2019-10-08 13:12:17 +01:00
README.md selenium: Improve README docs 2019-10-03 17:17:28 +00:00
wdio.conf.js selenium: Replace ES5 one-var assignments with const/let per line 2019-10-01 02:18:19 +00:00

Selenium tests

Getting started

See https://www.mediawiki.org/wiki/Selenium/Node.js for how to best run these locally. Below the internal prerequisites are documented, but you might not need to install these yourself.

Prerequisites

Usage

There are three supported modes of running the tests.

Headless

The Selenium tests default to headless mode, unless a DISPLAY environment variable is set. This variable may be set on Linux desktop and XQuartz environments. To run headless there, unset the DISPLAY environment variable first.

npm run selenium

Or:

DISPLAY= npm run selenium

Visible browser

To see the browser window, ensure the DISPLAY variable is set. On Linux desktop and in XQuartz environments this is probably set already. On macOS, set it to a dummy value like 1.

DISPLAY=1 npm run selenium

Video recording

To capture a video, the tests have to run in the context of an X11 server, with the DISPLAY environment variable set to its display name. If the shell has no X11 server or if you want to hide the output, you can also launch a virtual X11 display using Xvfb. Recording videos is currently supported only on Linux, and is triggered by the DISPLAY value starting with a colon (as Xvfb typically would). For example:

DISPLAY=:2 npm run selenium

Filter

Run a specific spec:

npm run selenium -- --spec tests/selenium/specs/page.js

To filter by test case, e.g. with the name containing "preferences":

npm run selenium -- --mochaOpts.grep preferences

Configuration

The following environment variables decide where to find MediaWiki and how to login:

  • MW_SERVER: The value of $wgServer.
  • MW_SCRIPT_PATH: The value of $wgScriptPath.
  • MEDIAWIKI_USER: Username of a wiki account with sysop rights.
  • MEDIAWIKI_PASSWORD: Password for this user.

Further reading