Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 04:55
    ashishnarmen commented #5545
  • May 06 18:58
    mikesalvia synchronize #6836
  • May 06 17:25
    mikesalvia commented #6836
  • May 06 15:45
    th0car commented #6816
  • May 06 15:09
    th0car commented #6816
  • May 06 14:35
    mikesalvia synchronize #6836
  • May 06 14:23
    mikesalvia commented #6836
  • May 06 14:21
    mikesalvia edited #6836
  • May 06 14:21
    mikesalvia edited #6836
  • May 06 14:21
    mikesalvia edited #6836
  • May 06 14:20
    mikesalvia opened #6836
  • May 06 13:33

    github-actions[bot] on v7.5.7

    v7.5.7 (compare)

  • May 06 13:32

    github-actions[bot] on main

    v7.5.7 (compare)

  • May 06 13:32

    github-actions[bot] on v7.5.7

    (compare)

  • May 06 13:28

    christian-bromann on main

    fix package-lock (compare)

  • May 06 13:05

    christian-bromann on cb-reload-devtools-session

    (compare)

  • May 06 13:05

    christian-bromann on main

    Fix reloading devtools sessions… (compare)

  • May 06 13:05
    christian-bromann closed #6832
  • May 06 12:59
    christian-bromann commented #4452
  • May 06 12:40
    Trueside commented #4452
Bitcollage
@SerkanSipahi
We use webdriverio 2.4.5
our commands look like this js browser.click(element, function(err) { //.... })
but now i see every call has a then after every call..
what is changed from v2 to v3?
any changelog there?
well, is documentation changed?
from V2 to V3?
csoete
@csoete
Its promise based instead of callback based.
But for most parts you can do both I think.
Bitcollage
@SerkanSipahi
ok thanks
we want to move to v3
is v3 callback based, too?
Bitcollage
@SerkanSipahi
@csoete thank you ...
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
How do I set timeoutsImplicitWait only once per tests run, i.e. in onPrepare? I can see that the global browser object does not exist there yet?
Christian Bromann
@christian-bromann
just set it in your before hook
the browser object will be available there
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
@christian-bromann Doing it per every test seems redundant. Maybe worth having a 'onBrowserReady' event. Thanks though!
Christian Bromann
@christian-bromann
you definitely need to set it once per session..the before hook gets executed after a session was created, so there should be no redundancy at all
with before hook I am talking about the one in your wdio.conf
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
yes, but doesn't it run per every test or so?
perhaps I interpret it wrong, maybe it's indeed exactly what I need
Christian Bromann
@christian-bromann
nope .. it runs once before it starts running all tests
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
ah cool
thanks
Christian Bromann
@christian-bromann
see it like: onPrepare -> session gets created -> before -> test1 -> test2 -> test3 -> after -> session gets closed -> onComplete
in your test spec you can define a before hook that runs before each spec within the test
This message was deleted
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
ah simples
I am working on incorporating selenium-standalone.start and kill into 'prepare' and 'onComplete', like discussed yesterday. I am capturing the child process in onPrepare, and then .kill() it in onComplete. The killing works fine, the browser window dissapears, but for some reason this leaves the whole execution hanging, i.e. the whole wdio command never finishes.
should I kill it somehow more gracefully?
csoete
@csoete
maybe try calling end(); on the browser/client object?
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
oh sorry, it doesn't even reach 'onComplete'
Christian Bromann
@christian-bromann
the wdio runner calls end for you…I will probably remove these commands so people can’t mess around with it
"oh sorry, it doesn't even reach ‘onComplete’” why is that?
only reason I can think of is that one test never finished
csoete
@csoete
if I would use the client without any testrunner wouldn't I need the end() call?
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
@christian-bromann 'only reason I can think of is that one test never finished' - ah could be. I did tinker with the test
but now I see I never called the kill
and I'm now only trying to do it, but I'm having a hard time with it.
Not sure what I should kill, and how to passit around from onPrepare to onComplete
I thought that just assigning a global 'seleniumStandaloneChild' variable in: seleniumStandalone.start({}, function (err, child) { seleniumStandaloneChild = child; })
I will be able to access it in onComplete
Christian Bromann
@christian-bromann
@csoete the runner takes care of initialising and ending the selenium session, without it you have to do it by yourself
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
but it seems to be null in the 'after'
csoete
@csoete
@christian-bromann I undestand, just wondering because you just wrote that you want to remove the method. But if you are using the driver standalone it would be required. Just confused.
Christian Bromann
@christian-bromann
@csoete sorry about that. I would only remove it if someone uses the wdio test runner
csoete
@csoete
ah ok
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
aha! It seems that what I assign in 'onPrepare:' is not visible in onComplete!