The jobs are running a subset of tests. (Tests containing string `@daily` in the name.) To find the tests we are using `--mochaOpts.grep` WebdriverIO command line option. The filter is executed after the tests have already started. Since some test files have no tests with string `@daily`, they are skipped. That results in JUnit reporter creating a couple of empty XML files. Jenkins thinks empty files are failures and fails the build. This commit creates a suite of files that have tests with string `@daily` and runs only those files. Bug: T281505 Change-Id: Id844da81feac49f2a2b6820e98ead98d7e932e9f |
||
|---|---|---|
| .. | ||
| pageobjects | ||
| specs | ||
| wdio-mediawiki | ||
| .eslintrc.json | ||
| README.md | ||
| wdio.conf.js | ||
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
wdio-video-reporter is used to record videos. All videos will be stored by default in the tests/selenium/log directory. This can be overridden by setting the LOG_DIR environment variable. To record videos only for failed tests, set the saveAllVideos = false in tests/selenium/wdio.conf.js file.
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