Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 14:09
    AutomationReddy commented #6863
  • 10:35
    BorisOsipov closed #6865
  • 10:35
    BorisOsipov commented #6865
  • 10:23
    nilskasseckert opened #6865
  • 02:05
    eoogo opened #6864
  • May 15 18:08
    sqagithub opened #6863
  • May 15 18:05
    jamesmortensen opened #6862
  • May 15 13:18
    wswebcreation closed #6861
  • May 15 13:18
    wswebcreation commented #6861
  • May 15 12:40
    jonn-set commented #6859
  • May 15 12:40
    jonn-set commented #6859
  • May 15 11:10

    christian-bromann on cb-sync-without-fibers

    fix import (compare)

  • May 15 11:00
    guneetgarg opened #6861
  • May 15 10:51

    christian-bromann on cb-sync-without-fibers

    code refactoring transform array operations (compare)

  • May 15 09:05

    christian-bromann on main

    Special characters not properly… (compare)

  • May 15 09:05
    christian-bromann closed #6661
  • May 15 09:05

    christian-bromann on cb-fix-wait-for-cli-install

    (compare)

  • May 15 09:05

    christian-bromann on main

    fix wdio-wait-for install via c… (compare)

  • May 15 09:05
    christian-bromann closed #6858
  • May 15 09:05

    christian-bromann on main

    removing Contributor Guide refe… (compare)

Christoph Herold
@coeamyd
Just wanted to put a ping here again. Is anybody here, who knows a bit about the devtools integration? When turning on performance measuring, it seems to turn extremely sluggish. I remember using it with version 4 a few months back, and at the time, everything was working nicely. The results returned very quickly. We now had to upgrade due to a too new chrome version, and now performance does not seem to work properly anymore. Does anyone have any suggestions, what we might be doing wrong?
We get a lot of "waiting for DOMContentLoaded" messages, until the process finally times out. But page load is actually very fast, so something looks wrong with the page load/idle detection.
Christian Bromann
@christian-bromann
@coeamyd if you have a speicific issue,please report a bug with a reproducible example .. these devtools features can break anytime after every Chrome update
Christoph Herold
@coeamyd
As I mentioned yesterday, I tried out the first example from the documentation, and it already produces the timeout.
Same with the "Chapter 05" example you suggested.
Christian Bromann
@christian-bromann
I tried the workshop example and it worked for me
every page can be different though
which is why I suggested if you run into issues with a particular page file an issue
Christoph Herold
@coeamyd
I tried the exact example and did not change the url. It's not, that it does not work, but it takes >50s once you use the "enablePerformanceAudits()" feature.
Christian Bromann
@christian-bromann
well that is normal .. performance tests take a while to capture all the data
there sure are ways to optimize that
Christoph Herold
@coeamyd
Ok, I just remember with v4 of webdriver, it took <10s, which is why I was wondering.
Which is also why I didn't want to open an issue and rather ask, if that is expected behavior :-)
But, since you say it is expected, I will need to find more optimized ways. Basically, I just need the timing of the DOMContentLoaded and window.load events.
Christian Bromann
@christian-bromann
I am not sure if v4 even had a Lighthouse integration
Christoph Herold
@coeamyd
I believe it was the first one that did. At least, I know, we looked at it when we evaluated that version. Or it may have been wdio5. But definitely pre-6.
Christian Bromann
@christian-bromann
if you are interested in particular that metric you can just do:
browser.execute("return(parseInt(window.performance.timing.domContentLoadedEventEnd)-parseInt(window.performance.timing.navigationStart));”)
Christoph Herold
@coeamyd
And this can be done without calling enablePerformanceAudits()?
To answer my question: Yes, it works without performance audits :-)
@christian-bromann Thanks a lot for your expertise!
krarpitgupta
@krarpitgupta
Hi @christian-bromann We are getting following error while trying to capture browser screenshot : Error: ENOENT: no such file or directory, open 'C:\project\sgfr01-ui-tests\test\evidence\snapshots\16-4-2021-13-47-41\screen_cc
_usd_2019.png' , Can you please help here ?
Christian Bromann
@christian-bromann
@krarpitgupta I advise to direct questions to the channel rather than to individual contributors .. besides there error message is pretty clear here
krarpitgupta
@krarpitgupta
ok point noted...between directory is available at mention path
browser.saveScreenshot(path.join(dirPath,/${screenTitle.toLowerCase()}${companyName.toLowerCase()} ${defaultCurrency.toLowerCase()}_${defaultEndYear}.png));
krarpitgupta
@krarpitgupta
Not sure what I am missing here :(
krarpitgupta
@krarpitgupta
Hi Everyone Can anyone help me to understand how can we take full page screenshot including browser address bar ? I am able to take browser page screenshot but that doesn't include URL address bar
Christoph Herold
@coeamyd
I don't believe, this is possible. The rendering functionality of the browsers typically only render the pages' contents to an image, and not their chrome. I may, however, be mistaken.
Why don't you, instead, save the url in a separate metadata file, and post-process your screenshot by adding some white pixels to the top and adding the address manually?
krarpitgupta
@krarpitgupta
thanks @coeamyd yeah we can save the URL...but before that I am exploring if there is a way to include screenshot that include address bar
Christoph Herold
@coeamyd
Good luck. As I said, I believe, this is not possible. If you do prove me wrong, please post your solution :-) And good luck.
Marijana Rukavina
@mareru
@christian-bromann ok, I hope codemod will be helpful :) Would you say that sync mode can still be used with webdriverIO v7 and Node v 14 without any issues? At least for a while - until node 14 comes to end of life (2023-04-30)
Christian Bromann
@christian-bromann
yes, but I recommend to switch to async as we can’t continue supporting it with Node v16 anymore
cezarybielec-itm
@cezarybielec-itm
hi, i would like to speed up my webdriver io tests. I want to send a login request once and then get the token and set it in storage for each following test. Is there a way to do it using webdriverio features?
Christian Bromann
@christian-bromann
@cezarybielec-itm sure, you run a suite with one spec first that gets you the token and then store it in the environment and kick off all the other tests in parallel
Tuteez
@Tuteez
Guys, how to clear cash with wdio? do hard reset or something
Christian Bromann
@christian-bromann
you mean clear cache? you can use https://webdriver.io/docs/api/browser/reloadSession to get a new browser instance
Tuteez
@Tuteez
yes cache, thank you :) window.location.reload(true) works for me
Christian Bromann
@christian-bromann
really? This just reloads the page, also it has no bool parameter (https://developer.mozilla.org/en-US/docs/Web/API/Location/reload)
cezarybielec-itm
@cezarybielec-itm
@christian-bromann i got it but how do i set the token? is there a way using webdriverio features or should i go with browser.execute and javascript code?
Christian Bromann
@christian-bromann
set the token where?
Tuteez
@Tuteez

really? This just reloads the page, also it has no bool parameter (https://developer.mozilla.org/en-US/docs/Web/API/Location/reload)

'By default, the reload() method reloads the page from the cache, but you can force it to reload the page from the server by setting the forceGet parameter to true: location.reload(true)." -> https://www.quanzhanketang.com/jsref/met_loc_reload.html why here is different info?

Christian Bromann
@christian-bromann
it seems that this parameter exists indeed https://webplatform.github.io/docs/apis/location/reload/
if it works for you, then great!
cezarybielec-itm
@cezarybielec-itm
in the localStorage
Christian Bromann
@christian-bromann
use the execute command, yes
cezarybielec-itm
@cezarybielec-itm
great, thank you
cezarybielec-itm
@cezarybielec-itm
last question for today i promise :D if i call a .waitForDisplayed() on the WebdriverIO.Element is this element re-searched? or am i calling this method on the same, already found element?
Erwin Heitzman
@erwinheitzman
@cezarybielec-itm the element is refetched
or to be more exact, the whole element chain is refetched
this prevents stale element references where one of the parent elements might refresh during two actions