-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Follow the Crystal convention of placing tests in a spec/ directory #47
Comments
Hey there! Yeah... so we're following the second method (compile and run individual spec files) so that this track can follow the structure of the other track repos (so that the cli and other services can have a standardized way to find all the files). I'm all for conforming with spec but... I'm not sure if there's a way to change the spec target directory (similar to how xelixir does it here). Unfortunately, I don't think we can configure that in a If you can figure out a way to keep the existing repo structure but also use |
Hi, thanks for taking the time to explain! I'm not sure I fully understand the problem, yet. It looks like the Clojure track is somehow able to have exercises that each have I see that we have a Makefile in this repo that manages running the spec files for each exercise. That could certainly be adjusted to Am I missing something? |
Ah I didn't know that xclojure had such a different exercise structure. Interesting! I think that it could work then. I'm still just a bit concerned about changing the whole structure of exercises after launching but... if it works, it works. I say go for it. I think the steps are to:
Since this is a pretty big change. I'm going to start a Thanks! |
According to the Crystal Spec module documentation:
Are we interested in following this convention? One reason I'm interested in this is that the excellent vim-crystal plugin has keybindings to run specs, but it only works if your project follows the convention of having your spec files in a
spec/
directory.If we're agreed, I'd be happy to contribute a PR updating the existing exercises.
The text was updated successfully, but these errors were encountered: