Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 20:40
    Selin-PDQ commented #4562
  • 20:16
    L0tso synchronize #6848
  • 18:29
    Travis aduggirala/webdriverio (master) errored (109)
  • 15:19
    L0tso converted_to_draft #6848
  • 15:04
    christian-bromann commented #6780
  • 14:38
    BadNews87 commented #6780
  • 14:24
    L0tso commented #6848
  • 14:13
    L0tso commented #6848
  • 13:45
    L0tso opened #6848
  • 09:37
    fabianschmider opened #6847
  • 09:32
    jimlancien commented #6386
  • 09:23
    christian-bromann closed #6386
  • 09:23
    christian-bromann commented #6386
  • 08:28
    jimlancien commented #6386
  • 08:27
    jimlancien commented #6386
  • 06:57
    chanyk-joseph commented #6839
  • 06:56
    chanyk-joseph commented #6839
  • May 10 21:45

    christian-bromann on main

    Update typescript examples, doc… (compare)

  • May 10 21:45
    christian-bromann closed #6846
  • May 10 21:45
    christian-bromann labeled #6846
Christian Bromann
@christian-bromann
e.g.
expect(yield browser.getTitle()).to.be.equal(“something”);
Dan Dascalescu
@dandv
Thanks. And last question for today: what's the easiest way to get started with WebdriverIO and Cucumber? Still https://github.com/webdriverio/cucumber-boilerplate?
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
@christian-bromann Thanks. I did consider forking. If I embarked on that quest, a noob node.js, or specifically npm question: how easy is it for the wdio package to come from my fork in my project? Is it a matter of changing one url?
Christian Bromann
@christian-bromann
I would use the wdio test runner and maybe port all these snippets over
@dandv ^^^
cucumber-boilerplate is still a good start though
@slawomir-brzezinski-at-travcorp in your package.json just grab your fork
”webdriverio”: "slawomir-brzezinski-at-travcorp/webdriverio”
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
awesome
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
another noob node/npm question. Everywhere I see people running 'wdio wdio.conf.js' but I get ''wdio' is not recognized as an internal or external command'. Is it because everyone installs wdio globally?
asd
I need to have the thing self contained, so I don't want it to pollute the machine globally. The only thing I have global is node. Keeping that in mind, is doing 'node_modules.bin\wdio wdio.conf.js' is the easiest way to run?
Christian Bromann
@christian-bromann
right .. but you can also call it like ./node_modules/.bin/wdio wdio.conf.js
yeah
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
ah, ok, I just came up with that myself, so needed to make sure I'm doing the right thing
thanks
Bitcollage
@SerkanSipahi
I believe the documentation for "http://www.webdriver.io/api.html" is changed !
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'