Test runner, opens empty browser for each feature file with no tests targeted about wdio-cucumber-framework HOT 10 CLOSED

Having the same issue. Using "wdio-cucumber-framework": "0.0.6"

from wdio-cucumber-framework.

I am experiencing the same issue, also using "wdio-cucumber-framework": "0.0.6".

Not a big deal for me when running tests locally but it creates a lot of noise when running tests through SauceLabs or BrowserStack.

from wdio-cucumber-framework.

Hi, any idea as to when we might get a fix on this?

from wdio-cucumber-framework.

@AndrewKeig feel free to start working on it 😉

from wdio-cucumber-framework.

👍 On this. Especially when using tags. Looks like it's spawning a child process for each feature file detected in the chosen features directory. WDIO is only running the tests that are tagged but seems to still spawn a process for the total number of .feature files. I'm going to look into this tonight and work on it if I have time. @christian-bromann would you recommend I start here or look in WDIO directly? Just figured I'd ask if you had any recommendations.

from wdio-cucumber-framework.

I think though this (tagging) should be implemented project wide so it works across frameworks. However I am not sure about the implementation details.

from wdio-cucumber-framework.

Any update on this issue? Thanks! @dcypherthis

from wdio-cucumber-framework.

Tagging in wdio-cucumber framework is not working for me as well. Any luck ? It's running all the test cases even after scenario based tagging. :( @dcypherthis

from wdio-cucumber-framework.

See webdriverio/webdriverio#1247 (comment)

from wdio-cucumber-framework.

This is a general problem and will be tackled in webdriverio/webdriverio#1247

from wdio-cucumber-framework.