d94b16a74d
Unil 2020-06-15 we were using Xvfb+ffmpeg to record videos.
In eed975d we have switched to wdio-video-reporter npm package.
It has never worked very well. It does not really record videos.
It creates screenshots and creates videos from them.
It does not record modal popups. Sometimes, it doesn't create a video
for a test at all.
I think it's time to switch back to Xvfb+ffmpeg. It has worked well. The
reason we moved to wdio-video-reporter was that it worked on all
platforms. That's not really important any more, since Xvfb+ffmpeg works
in a Fresh container.
Bug: T253113
Change-Id: I221775208576b6496f682ceefd6e6334db488bd4
2.2 KiB
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).
Example test run in Fresh.
fresh-node -env -net
export DISPLAY=:1
Xvfb "$DISPLAY" -screen 0 1280x1024x24 &
npm run selenium-test
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
- Selenium/Node.js on mediawiki.org