Page MenuHomePhabricator
Paste P15092

Tried to run selenium tests on my local machine

Authored by Anjali_Kumari_41 on Mar 30 2021, 3:27 PM.
I was trying to run the selenium tests to complete my task [[ | microtask]].
However I am facing the following issue.
npm run selenium-test
> @ selenium-test /mnt/c/users/anjali kumari/onedrive/desktop/core
> wdio ./tests/selenium/wdio.conf.js
2021-03-30T15:00:21.466Z DEBUG @wdio/config:utils: Couldn't find ts-node package, no TypeScript compiling
Execution of 6 spec files started at 2021-03-30T15:00:34.421Z
[0-0] RUNNING in chrome - /tests/selenium/wdio-mediawiki/specs/BlankPage.js
[0-0] 2021-03-30T15:01:38.855Z ERROR @wdio/runner: Error: connect ECONNREFUSED
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
[0-0] Error: connect ECONNREFUSED
[0-0] 2021-03-30T15:01:43.882Z ERROR @wdio/runner: Error: Some reporters are still unsynced: Video
at Timeout.<anonymous> (/mnt/c/users/anjali kumari/onedrive/desktop/core/node_modules/@wdio/runner/build/reporter.js:86:25)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
[0-0] FAILED in chrome - /tests/selenium/wdio-mediawiki/specs/BlankPage.js
Steps to reproduce:
I followed the [[| Mediawiki-docker setup]].
1) Docker and docker-compose installation
2) .env file and docker-compose.override.yml created.
3) echo "MW_DOCKER_UID=$(id -u)
MW_DOCKER_GID=$(id -g)" >> .env
4) docker-compose up -d
docker-compose exec mediawiki composer update
docker-compose exec mediawiki /bin/bash /docker/
5) Deleted LocalSettings.php and cache/sqlite
docker-compose exec mediawiki /bin/bash /docker/
6) git clone "" extensions/examples
echo "wfLoadExtension( 'examples' );" >> LocalSettings.php
docker-compose exec mediawiki php maintenance/update.php
7) git clone "" skins/Vector
echo "wfLoadSkin( 'Vector' );" >> LocalSettings.php
8) npm ci
npm run selenium-test

Event Timeline

@Anjali_Kumari_41 Is MediaWiki is running on your localhost after you followed all the steps of

Do you have chromedriver running?

No, I went through the docs and I guess chromedriver is not needed anymore for testing.