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

Can't find test files after migrate from cypress-cucumber-preprocessor #1232

Closed
3 tasks done
KarineBrandelli opened this issue Sep 13, 2024 · 2 comments
Closed
3 tasks done

Comments

@KarineBrandelli
Copy link

Current behavior

I'm migrating from cypress-cucumber-preprocessor, and after adjust the config files, it says that the file doesn't have any tests.

I've created a sandbox EXACLTY as my local repo. On the sandbox works perfectly, on my machine don't.

I don't have any errors to go one, maybe some config on my machine is wrong (?)

Sandbox:
image

My local machine:
image

image

If I click on the test name, it redirecs correctly to the test file on the IDE.

I've runned out of ideias. Tried literally everything.

Desired behavior

Find the tests.

Test code to reproduce

This sandbox WORKS.
On my machine, the SAME configuration, doesn't work.
https://codesandbox.io/p/devbox/3y4jwl

My machine: Ubuntu

Versions

  • Cypress version: 13.14.2
  • Preprocessor version: 20.1.2
  • Node version: 20.15.0

Checklist

  • I've read the FAQ.
  • I've read instructions for logging issues.
  • I'm not using cypress-cucumber-preprocessor@4.3.1 (package name has changed and it is no longer the most recent version, see #689).
@badeball
Copy link
Owner

I'm not really sure how I can help with a problem that I can't reproduce nor even experience. You can start by using chrome devtools to see the contents of check-tree.feature after it's been compiled into JS and sent to the browser (post it here).

@KarineBrandelli
Copy link
Author

I'm not really sure how I can help with a problem that I can't reproduce nor even experience. You can start by using chrome devtools to see the contents of check-tree.feature after it's been compiled into JS and sent to the browser (post it here).

You kinda solved it without seeing it lol. The path to my folder test had a special character on it, ex: usr/local/P&D/frontend, and the special character was breaking the path, thus not finding anything. Renamed the folder and worked. Find out looking at the devtools specPath! Thanks 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants