-
Notifications
You must be signed in to change notification settings - Fork 70
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
Allow run the tests from any subdirectory under the project directory #130
Comments
Do I understand correctly, that if I want to have e.q. a custom matcher shared between tests in subdirectories, then this can go to If so, then this is awesome. Then even if #138 is inappropriate to be merged in, I can make it a custom matcher to be shared between my tests. |
Nice. Unfortunately I realised this does not work with my |
@ko1nksm I see you have added |
There was more work to do than I expected, so it's taking longer. I'm going to release 0.28.0 after at least addressing #144. I can't promise, but I hope to release it by the end of this month. |
@AntoniMarcinek The development of version 0.28.0 is finished, and only the documentation remains, but there are some number of projects that have installed the latest version (without specifying the version) with CI, so I will release it on 2021-01-05 midday (UTC) to keep a peaceful new year 🎍. If you want to try the latest version, use the master branch. |
Splendid, thank you! |
The current implementation does not work properly when run from a subdirectory of the project, because the working directory is not the project root directory . It doesn't make much sense, so change it so that the working directory is the project root directory, no matter which directory you run from.
This is a change that needs attention, but the impact is likely to be minor because it should not be working at present.
And we also need to load such as
spec_helper.sh
from the thespec
directory under the project root instead of thespec
directory under the current directory. Thespec
directory is the default directory and need to add the--helper-dir
option to able to change. Issue #123 is also relevant.This Issue is a fix to address the issue of the Issue #121 working directory.
The text was updated successfully, but these errors were encountered: