Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to navigate to step definition from the feature file #74

Closed
ApurvaNayak opened this issue May 7, 2020 · 9 comments
Closed
Labels
Issue A defect or bug which renders one or more features unusable under certain circumstances Stale Probably not relevant anymore and to be closed

Comments

@ApurvaNayak
Copy link

Description: I am unable to navigate to step definition when I command+click on the steps from feature file. However, the scripts are working fine when we run through jUnit or Maven and there are no issues finding the step definition.

  • Eclipse version: 2020-03 (4.15.0)
  • Build ID: 20200313-1211
  • Plugins:
  • Natural 0.7.6 (installed from market place with cucumber editor)
  • Cucumber Eclipse 1.0.0.202001082311
  • OS: MacOS

Snapshot of the plugins installed:
image

Snapshot of the Runner file and project folder structure:
image

Snapshot of the feature file:
image

Below are the steps I have tried and have not got any success:

  • Uninstall the plug ins
  • Restart the eclipse
  • Reinstall the plugins from the market place
  • Restart the eclipse
  • Convert the project to Cucumber project.

Could someone please check and let me know where am I going wrong and if someone can please help me out with the solution. Also, please note that everything was working fine just until 2 days ago and all of the sudden it has stopped working.

Changes done within these two days were nothing but moving the feature files from one folder to other folder. Earlier I had all the files in just one folder and it was tedious to maintain it so created multiple folder based on my project structure and moved the files in the respective folders.

Would appreciate all the help and pointers i can get from the experts here.

@drkstr101
Copy link
Contributor

drkstr101 commented May 8, 2020

Hi ApurvaNayak,

Sorry to hear you are running into trouble. The current release on the Marketplace is actually 5 years old at this point. However, there will be an update soon (within days) that may address this problem, but there are no specific changes that change this behavior, so it could be entirely unrelated to Natural.

I will do some testing on the upcoming release and make sure linking to step definitions is working as expected.

All the best,
~Aaron

@ApurvaNayak
Copy link
Author

Thanks much Aaron. I will wait for the update and see if that helps me resolving the issue. It is really giving me hard time without the linkage.

@drkstr101
Copy link
Contributor

Also, it looks like this problem may have been around for a while.

#51

There must be something strange in the workspace setup that's causing it to fail. More testing definitely needs to be done to ensure this is working correctly in the upcoming release.

@ApurvaNayak
Copy link
Author

@drkstr101,

Hello Aaron,

Just wanted to check if we had the updates out? if Not, do we have any tentative plans ?

@rlogiacco
Copy link
Owner

Have you tried the latest release, 0.7.7?

@ApurvaNayak
Copy link
Author

ApurvaNayak commented May 27, 2020

Have you tried the latest release, 0.7.7?

Yes. Today i updated the release to 0.7.7 and the problem is still persistent. I am still facing the issue which was reported.

@rlogiacco rlogiacco added the Issue A defect or bug which renders one or more features unusable under certain circumstances label May 27, 2020
@rlogiacco
Copy link
Owner

Thanks.
The issue you are reporting is related to the use of the placeholder within the ScenarioOutline which has never worked properly: our step matching algorithm is unable to resolve the placeholder, thus unable to find a matching step.

I guess you are left with a few options:

  1. step in and solve the problem yourself, maybe contributing your solution back to the project
  2. wait until we decide to prioritize this issue
  3. use the Sponsor button at the top of the page to discover how to force your priorities on us 😄

I'll leave this issue open as a reminder of the problem.

@rlogiacco
Copy link
Owner

Duplicate of #40

@rlogiacco rlogiacco marked this as a duplicate of #40 May 27, 2020
@github-actions
Copy link

This issue has not been updated for a while: marking it as stale.

@github-actions github-actions bot added the Stale Probably not relevant anymore and to be closed label Jul 27, 2020
@github-actions github-actions bot closed this as completed Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue A defect or bug which renders one or more features unusable under certain circumstances Stale Probably not relevant anymore and to be closed
Projects
None yet
Development

No branches or pull requests

3 participants