by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 14:41
    codecov[bot] commented #3708
  • 14:41
    codecov[bot] commented #3148
  • 14:41
    jsf-clabot commented #5404
  • 14:41
    jsf-clabot commented #5570
  • 14:39
    jsf-clabot commented #5570
  • 14:39
    Jnegrier opened #5570
  • 14:34
    SrinivasanTarget synchronize #5566
  • 14:06
    sam-022 commented #5569
  • 08:24
    wswebcreation closed #5569
  • 08:24
    wswebcreation commented #5569
  • 01:08
    sam-022 edited #5569
  • Jul 04 23:28
    sam-022 opened #5569
  • Jul 04 16:10
    christian-bromann labeled #5568
  • Jul 04 16:10
    christian-bromann labeled #5568
  • Jul 04 16:10
    christian-bromann labeled #5568
  • Jul 04 16:10
    christian-bromann labeled #5568
  • Jul 04 16:10
    christian-bromann commented #5568
  • Jul 04 13:05
    monil20 edited #5568
  • Jul 04 13:00
    monil20 edited #5568
  • Jul 04 12:58
    monil20 edited #5568
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
Hi everyone! Good day! Does anyone know if the 'running scenarios in parallel to reduce run time' (webdriverio/webdriverio#205) can be achieved in any framework supported way?
(i'm using WDIO + cucumber)
Christian Bromann
@christian-bromann
@slawomir-brzezinski-at-travcorp just define multiple capabilities in your conf file
currently it is unfortunatelly one process per capability. In future it will be one process per capability per test spec
slawomir-brzezinski-at-travcorp
@slawomir-brzezinski-at-travcorp
@christian-bromann Thanks! Any guess on when this would be possible? Meanwhile, Is there a way to assign each capability a different set of specs (even a dirty way?)
(but ideally not so dirty that it require to break the source of specs manually :) )
perhaps, 5 capabilities each assigned index 0-4, each executing only testSpec which testSpecIndex % x = 0
:D
Dan Dascalescu
@dandv
webdriver-sync has a really nice syntax - https://github.com/jsdevel/webdriver-sync#in-favor-of-this. How close can WebdriverIO get to sync? Is there an example somewhere?
Christian Bromann
@christian-bromann
@slawomir-brzezinski-at-travcorp not yet unfortunatelly .. dirty way would be to fork the project and hack a temporary solution
currently I am not able to spend much time doing open source but this will change in 2 weeks, there is a lot of stuff to catch up with
@dandv I was experimenting with fibers to get sync in webdriverio .. got it working for protocol commands but not for nested commands, definitelly something I wanna add to webdriverio
but this is kinda possible already today using yield
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