No changes are made to the configuration file. It has just been regenerated with the latest WebdriverIO version. Minor whitespace cleanup has been made to the file after it has been generated so it conforms to our ESLint configuration. This is the first step in updating configuration so videos of failed tests are recorded. Bug: T179188 Change-Id: Id0db3743ae7d828357b1527770bb7dcd2e02f99b |
||
|---|---|---|
| .. | ||
| pageobjects | ||
| specs | ||
| .eslintrc.json | ||
| README.md | ||
| wdio.conf.jenkins.js | ||
| wdio.conf.js | ||
Selenium tests
Prerequisites
Set up MediaWiki-Vagrant:
cd mediawiki/vagrant
vagrant up
Installation
cd mediawiki
npm install
Usage
npm run selenium
To run only one file (for example page.js), you first need to spawn the chromedriver:
chromedriver --url-base=wd/hub --port=4444
Then in another terminal:
cd tests/selenium
../../node_modules/.bin/wdio --spec specs/page.js
To run only one test (name contains string 'preferences'):
../../node_modules/.bin/wdio --spec specs/user.js --mochaOpts.grep preferences
The runner reads the config file wdio.conf.js and runs the spec listed in
page.js.
The defaults in the configuration files aim are targeting a MediaWiki-Vagrant installation on http://127.0.0.1:8080 with a user Admin and password 'vagrant'. Those settings can be overridden using environment variables:
MW_SERVER: to be set to the value of your $wgServer
MW_SCRIPT_PATH: ditto with $wgScriptPath
MEDIAWIKI_USER: username of an account that can create users on the wiki
MEDIAWIKI_PASSWORD: password for above user
Example:
MW_SERVER=http://example.org MW_SCRIPT_PATH=/dev/w npm run selenium