@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?
I would use the wdio test runner and maybe port all these snippets over
cucumber-boilerplate is still a good start though
@slawomir-brzezinski-at-travcorp in your package.json just grab your fork
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?
right .. but you can also call it like ./node_modules/.bin/wdio wdio.conf.js
ah, ok, I just came up with that myself, so needed to make sure I'm doing the right thing