This repository was archived by the owner on Nov 29, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
feature file resolution does not work on windows machines #601
Comments
coderbyheart
added a commit
that referenced
this issue
Aug 4, 2022
🎉 This issue has been resolved in version 15.1.68-make-wildcards-work-on-windows.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Thanks for reporting, please not that we do not support Windows right now. We recommend to use WSL 2 if you must use Windows. That said, could you try the fix from #602? It might solve your problem. |
yeah that fix works, next issue upcoming tough #603 thanks for the fix |
coderbyheart
added a commit
that referenced
this issue
Aug 4, 2022
🎉 This issue has been resolved in version 15.1.68 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There is an issue where the feature runner cannot resolve the
*.feature
files on a windows machineconst scan = path.join(path.resolve(dir), '*.feature');
path.resolve
will return a platform dependent path on windows something likeC:\Users\maeckle
but glob only works with forward slashesI would have loved just changing the API to pass the whole glob pattern (that would also allow subdirectories **/*.feature) or different filenames, but that would be a breaking change. I will think about how to solve it, maybe something like this.
The text was updated successfully, but these errors were encountered: