Boris Osipov

Hi, workaround for this problem is pretty easy - make `cucumberOpts.timeout` greater than any wait\sleep timeouts in your tests - it will help to avoid cucumber timeouts and retries will...

@markmssd you can use workaround in your wdio.conf you can manually filter specs with your tags like that: ``` const fs = require('fs'); const { TagExpressionParser } = require('cucumber-tag-expressions'); const...

@markmssd you're welcome. pay attention it's a bit raw and it handles emails in your feature files as tag (because emails have `@` symbol)

@markmssd yep :)

yes чт, 7 июн. 2018 г. в 22:39, Venkat Rao : > const fs = require('fs'); > const { TagExpressionParser } = require('cucumber-tag-expressions'); > const glob = require('glob'); > >...

>but it opens multiple browser instances don't know why. it must not. for me it works like a charm

Use `cucumber-tag-expressions` for properly parcing tagExpression.

>It seems to not able to handle and and not operators. >I used cucumber-tag-expressions and it is failing when I have: how do you use it?

It works. Cucumber uses `cucumber-tag-expressions` internally for working with tags.

And why did you decide that is not work? You just print `' ===== TAGS =====', expressionNode);` in console...