currently it is unfortunatelly one process per capability. In future it will be one process per capability per test spec
(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
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?
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”);
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?
@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”
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?
yeah
thanks
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?
i found the changelog: https://github.com/webdriverio/webdriverio/blob/master/CHANGELOG.md :)
well, is documentation changed?
from V2 to V3?
But for most parts you can do both I think.
we want to move to v3
is v3 callback based, too?
the browser object will be available there
with before hook I am talking about the one in your wdio.conf
perhaps I interpret it wrong, maybe it's indeed exactly what I need