Is there any way that I can include page response time in the result with webdriverIO
For eg- if I am automating 5 pages then in the results I can see that a respective page was loaded fully in 2 or 3 seconds ??
Any plugin to hook up with webdriverIO which supports any such integration ???
at Element.elementErrorHandlerCallback (node_modules\webdriverio\build\middlewares.js:40:8)
node_modules\@wdio\utils\build\shim.js:60:46
Hi all
I've got a problem with connecting devtools to chrome
I'm running WDIO sync in a container. Chrome is being run in an other container. Here's my docker-sompose.yml:
version: '2'
services:
hub:
image: selenium/standalone-chrome-debug
networks:
e2e_tests_network:
ipv4_address: 172.72.0.2
ports:
- "4444:4444"
- "5900:5900"
- "9222:9222"
environment:
- SCREEN_WIDTH=1920
- SCREEN_HEIGHT=1080
volumes:
- /dev/shm:/dev/shm
- ./:/opt/qa
e2e-tests:
build:
context: .
dockerfile: Dockerfile
image: e2e-tests:latest
depends_on:
- hub
networks:
e2e_tests_network:
ipv4_address: 172.72.0.3
links:
- hub
volumes:
- ./:/opt/qa
networks:
e2e_tests_network:
driver: bridge
ipam:
driver: default
config:
- subnet: 172.72.0.0/24
gateway: 172.72.0.1Here's everything what's related to devtools service.packege.json:
{
...
"dependencies": {
"@wdio/devtools-service": "^5.16.10",
}
}wdio.conf:
services: [
['devtools', {
debuggerAddress: '172.72.0.2:9222',
}],
],The error I get upon launching the tests:
[0-0] (node:86) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 172.72.0.2:9222
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1097:14)debuggerAddress. However, when run in docker container - it causes that error above.
Hey guys how do You go further in the scope of one of the elements picked from list:
Like I've got a list of packages:
let packages = browser.findElements("tag name", "selector1);
And I'm interested in packages[0] element that I would go further with to look for all it childs
Was trying with:
packages[0]. $ $ ("selector2")
but seems like this $$ works only with selectors instead of an objects
takeScreenshot(), it seems that that's part of the w3c webdriver api. And as @erwinheitzman says, [findElement] "... is part of the webdriver api which is out of our control as it's a protocol which is also called the w3c standard", I'm guessing that we wouldn't want to normally call that API (except, perhaps, as specifically directed when using Allure). Or, I guess, conceivably, when the Allure service is configured, it adds that command to make it available when creating the report.
findElementwhen using webdriverio. I have been using webdriverio for about 4 years now and have never needed it. Use $ or $$ and all should be good and if you are having some issues or challenges, just ask here and people will try to help
findElement (as you said), we would not want to use normally use the w3c webdriver API takeScreensot, but, rather, use the webdriverio API saveScreenshot. But in the particular case of the Allure setup, it specifically says, at https://webdriver.io/docs/allure-reporter.html#add-screenshots, "Screenshots can be attached to the report by using the takeScreenshot function from WebDriverIO in afterStep hook.
