@nitinWFH https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/welcome.html
Thank you, i will go through it..!
Is this warning suppressable?
[0-0] RUNNING in chrome - /tests/specs/basic.js
[0-0] Warning! Unsupported expect lib is used.
Only Jasmine >= 3.3.0 and Jest's expect are supported.
expect-webdriverio is assigned to global.expectWdioI imagine if I let the native assertion library use expect that'd be fine, but I like using that instead of chai.expect
4 replies
A service failed in the 'onPrepare' hook
Error: Appium exited before timeout (Exit code: 2)
at ChildProcess.exitCallback (/private/tmp/scratchkLlkKg.scratch/test-packageVJzcYO/node_modules/wdio-appium-service/build/launcher.js:94:28)
at Object.onceWrapper (events.js:317:30)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
Continue...
ERROR: ESOCKETTIMEDOUT
4545b75e9e343eb8ba9de068016dd13d5f192e71.ios
at new RuntimeError (/private/tmp/scratchkLlkKg.scratch/test-packageVJzcYO/node_modules/webdriverio/build/lib/utils/ErrorHandler.js:143:12)
at Request._callback (/private/tmp/scratchkLlkKg.scratch/test-packageVJzcYO/node_modules/webdriverio/build/lib/utils/RequestHandler.js:332:43)
at self.callback (/private/tmp/scratchkLlkKg.scratch/test-packageVJzcYO/node_modules/request/request.js:185:22)
at emitOne (events.js:116:13)
at Request.emit (events.js:211:7)
at ClientRequest.<anonymous> (/private/tmp/scratchkLlkKg.scratch/test-packageVJzcYO/node_modules/request/request.js:819:16)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at ClientRequest.emit (events.js:208:7)
at Socket.emitTimeout (_http_client.js:718:34)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at Socket.emit (events.js:208:7)
at Socket._onTimeout (net.js:422:8)
at ontimeout (timers.js:498:11)
at tryOnTimeout (timers.js:323:5)
1 reply
Hi All i'm a bit new to the 'setting up' of automation frameworks. I've got an electron desktop app which I've configured to run spectron which under the hood accesses webdriverIO. Now i've used webdriver before i.e I recall the browser object. Reading online the browser object is application.client.
My automation test access the webdriverIO functions which is awesome! The only problem is. The intelisense for webdriverIO in spectron application.client does not show in VSCode for methods like element(), .getText(), pause(). The things native to webdriverIO how do I get them to appear to the programmer?
But actually something like this might be better:
//iframe[contains(lower-case(@src), ‘exampleapp’)]@Lecale Apparently there's also a 'matches' option with a case-insensitive flag 'i' in xpath 2.0:
//iframe[matches(@src,'exampleapp','i')]Ref. https://stackoverflow.com/questions/2893551/case-insensitive-matching-in-xpath
Hi, faced the issue of stand-alone seleniun driver, there is already a solution?
Could not load plugin wdio from module './plugin/wdio':
Couldn't initialize service selenium-standalone from wdio plugin config.
It should be available either in '@wdio/selenium-standalone-service' package
My config is as follow
{
"name": "automate-qa",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "felix<firomerorom4>",
"license": "ISC",
"dependencies": {
"@codeceptjs/ui": "^0.3.8"
},
"devDependencies": {
"@wdio/selenium-standalone-service": "5.16.10"
}
}Installed codecepts globally
Context: webdriverIO v5
Issue : console ouput variation makes me think local runner doesnt shutdown properly
Normal console log :
Spec Files: 1 passed, 1 total (100% completed) in 00:00:16
2020-05-22T19:48:56.766Z INFO @wdio/local-runner: Shutting down spawned worker
2020-05-22T19:48:57.018Z INFO @wdio/local-runner: Waiting for 0 to shut down gracefully
2020-05-22T19:48:57.018Z INFO @wdio/local-runner: shutting downSuspected issue console:
[firefox 3.10.0-1062.4.3.el7.x86_64 linux #0-0] 29 passing (10m 3.4s)
Spec Files: 1 passed, 1 total (100% completed) in 00:10:08This matters because I am running it in a script that should return 0 and I am wondering why the difference in console ouput.
My screenshots on failure are not happening as I want. I have this as my afterTest function:
afterTest: function (test) {
if (!test.passed) {
const secs = Math.floor(new Date().getTime() / 1000);
const fname = `${encodeURIComponent(test.title.trim().replace(/\s+/g, '-'))}_${secs}.png`;
const fp = join(process.cwd(), this.screenshotPath, fname);
console.info(`saving screenshot: ${fp}`);
browser.saveScreenshot(fp);
}
},but it doesn't seem to happen right at the point of failure, but rather, later, after the bad page state is no longer shown. What would be causing this, and how can I work around/fix it?
