CentralNotice$ npm run @selenium-test
No One
Actions

Authored By

	zeljkofilipin
	Sep 2 2021, 9:32 AM

Size

1 KB

Referenced Files

None

Subscribers

None

CentralNotice$ npm run @selenium-test
View Options

	nobody@docker-desktop:/core/extensions/CentralNotice$ npm run @selenium-test

	> @ @selenium-test /core/extensions/CentralNotice
	> wdio tests/selenium/wdio.conf.js


	Execution of 1 spec files started at 2021-09-02T09:31:51.859Z

	(node:167) ExperimentalWarning: The dns.promises API is experimental
	(node:167) ExperimentalWarning: The fs.promises API is experimental
	[0-0] (node:176) ExperimentalWarning: The dns.promises API is experimental
	[0-0] (node:176) ExperimentalWarning: The fs.promises API is experimental
	[0-0] RUNNING in chrome - /tests/selenium/specs/centralnotice.js
	[0-0] Error in "CentralNotice banner is displayed on Main Page"
	Error: element ("#centralnotice_testbanner") still not existing after 5000ms
	at Context.<anonymous> (/core/extensions/CentralNotice/tests/selenium/specs/centralnotice.js:10:19)
	[0-0] FAILED in chrome - /tests/selenium/specs/centralnotice.js

	"dot" Reporter:
	F

	Spec Files: 0 passed, 1 failed, 1 total (100% completed) in 00:00:15

	npm ERR! code ELIFECYCLE
	npm ERR! errno 1
	npm ERR! @ @selenium-test: `wdio tests/selenium/wdio.conf.js`
	npm ERR! Exit status 1
	npm ERR!
	npm ERR! Failed at the @ @selenium-test script.
	npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

	npm ERR! A complete log of this run can be found in:
	npm ERR! /cache/_logs/2021-09-02T09_32_07_481Z-debug.log