-
Notifications
You must be signed in to change notification settings - Fork 3
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
Workflow for testing exercises in development #1
Comments
I gave this some thought as well. Something that came to mind for me, is to have a flag on Thinking about it though, that's more integration testing and not local testing of the exercises. So maybe both ways are needed? |
I think it tackles both integration testing and local testing, and honestly I can't complain. Only thing that might be a bit cumbersome is having to jump between 2 projects during such testing. But maybe that could be better automated by having the script (in the exercises project) generate a fresh project and run the mix task. Should be significantly less smelly than the approach I tried at first, which was trying to "manually" compile modules/run tests in the script. Regardless, I like this idea. But that means we'll have to wait for the mix task code to be done (at least an initial version that gets merged into the main branch). |
I'm hoping to have more time to get the generator task functional from github later tonight. At the very least I'll focus on adding a flag for an gh repo of I can't get the file system version working. |
@waseem-medhat is this still open and underway or does it warrant closing? |
I thought to leave it open for future experimentation as I do want to revisit again after we settled on the structure of both repos. |
Since the exercises are in a repo that is separate from when they actually run, I figured we'd need a way to quickly test the exercises (and associated tests) while they are being developed.
I am still strongly leaning towards not making this repo configured like an app with Mix for the following reasons:
So, my suggestion is to have a script that is simply called from the shell (e.g.,
elixir run_tests.exs basic_types
), and it only compiled the two files inside, i.e., compiles the module code and runs its tests.The text was updated successfully, but these errors were encountered: