cucumber | cucumber js with selenium-webdriver | Functional Testing library

IDEA uses a simple heuristics to determine which Cucumber version to use. If the latest version is detected, that one is used.

However Karate depends on the older versions of Cucumber. So when using Karate and a recent version of Cucumber IDEA will ignore Karate.

To fix this properly Peter would have to provide his own step definition annotations. And then IDEA could use those next to the ones from Cucumber.

But that means waiting for Jetbrains which I imagine Peter is loath to do.

You can do:

For me it runs ok with Cypress@9.3.0 and cypress-cucumber-preprocessor@4.3.1 which is the latest tag on their Github repo.

But I notice that if you don't specify the version, you get cypress-cucumber-preprocessor@4.2.1, so I guess there's some catching up to do on npm.

In short, specify the latest version

I solved my problem. Turns out the JRE that eclipse had automatically downloaded and was using wasn't compatible with this version of cucumber. I manually changed the path to a jre 1.8 that i had in my ProgramFilex(x86)/Java folder and now everything works fine.

I also stumbled upon this problem and realized that this does not work actually.

As a workaround I therefore moved away from the approach of using cypress-tags and instead adjusted the naming of my feature files. This allowed me to avoid the use of cypress-tags and use the normal cypress run command instead specifying config and feature files like:

I had a similar problem but resolved by following steps.

1. Run the following command. heroku buildpacks:add heroku/nodejs --index 1
2. Update node version from 16.x to 12.16.2 in package.json.

To solve your specific issue, you can generate dummy variables to run your desired clustering.

One way to do it is using the dummy_columns() function from the fastDummies package.

The ariaSelected property of the Element interface reflects the value of the aria-selected attribute, which indicates the current "selected" state of elements that have a selected state.

Value: A DOMString with one of the following values:

• true: The item is selected.
• false: The item is not selected.

Selected/unselected state of this WebElement attribute doesn't effects your tests.

To locate the element you can you can use either of the following Locator Strategies:

• xpath:

The likely reason you can observe such behavior is that there is a thing called "glue path" that is basically a package where Cucumber looks up the code (including custom parameter definitions).

By default cucmber uses glue path taken as the package that contains your runner class. So I assume that when you were having your code in original project that condition was met.

But when you made a library and used it as a dependency in another project Cucumber stopped seeing that since conditions stopped being met.

You need to specify glue path manually like it is mentioned in cucumber docs

By default Cucumber-JVM will search in the package (or sub-packages) of the runner class. You can also tell Cucumber-JVM explicitly which packages (and sub-packages) to search, with: