Getting warning on feature file after upgrading to Katalon 9.7.1 "Step definitions detection works only when the project is configured as cucumber project."

Product Forums Katalon Studio
,
1

I have a katalon project with UI and API tests but facing below issue:

  1. Getting warning on feature file after upgrading to Katalon 9.7.1 “Step definitions detection works only when the project is configured as cucumber project.”
  2. Clicking on the steps in the feature file doesn’t take to the corresponding step definition. I tried “find Step definition too” and nothing happens.
  3. The Feature files are correctly in the path "Include-> features → ProjectName → FeatureName → test1.feature.
  4. I tried creating a new feature file too and it still complains about the project not being configured as Cucumber project.

The Feature file didn’t show any warning earlier to this version.
However the execution is working fine and its picking the relevant step definition during execution.

image
image916×361 107 KB

image
image975×528 176 KB

1 Like
2

Hi there, :wave:

Thank you very much for your topic! It may take a little while before Katalon team member or others forum members respond to you.

In the meantime, you can double-check your post to see if you can add any extra information i.e. error logs, HTML codes, screenshots, etc. Check out this posting guide to help us help you better!

Thanks! :sunglasses:
Katalon Community team

3

Hi @ckrishnamurthy,

Can you please help share the warning?

4

“Step definitions detection works only when the project is configured as cucumber project.”
My screenshot on the feature file shows the same warning

5

Hi @ckrishnamurthy,

We have acknowledged this issue and plan to fix it in v9.7.2. I will keep you up-to-date with the progress. Thank you!

1 Like
6

This is still not fixed in version v9.7.2. I was transitioning from Cypress to Katalon and I lost hours trying to figure out what I had done wrong in my first BDD/Cucumber to come here and see this… I downloaded version 8.6.9 just to be told that I can’t use it as it is a legacy version. Unbelievable…

7

Hi @jose.ribeiro,

Sorry for my late response. Our team is still investigating it and has moved this to a later release. Currently, we still have not had a clear plan for this but I will keep you updated with this.