@joelwallis thanks for doing this, and thanks to @ronalson for reporting the issue.

There is a way to configure jasmine to run all *spec* files in the current directory, but let's save that for another PR. @joelwallis I can open a new issue for that.

Closes #349

I didn't know that it could be done through configuration. @matthewmorgan let's discuss it on a new issue for sure!

Thank you guys for the quick response. This was my first ever issue reporting. I liked the experience and I'm looking forward to contribute even more in the future. :)

I have one question though: this merge takes immediate effect on exercises documentation or it will be available only in future version of the CLI. If it is immediate, how do I update previously downloaded content?

@ronalson awesome! You can take a look at available issues tagged as good first patch. Those are meant to serve as a good starting point for new contributors 🙂

About seeing the effects, they are definitely not immediate. I've just checked how Exercism CLI works and it fires HTTP requests to http://x.exercism.io/v2 - in this case, to the /exercises/:language-track/:exercise endpoint. I'm seeing outdated content, so language track contents might be cached by the API itself.

You can check it by yourself, running exercism --verbose fetch javascript hello-world.

@joelwallis @ronalson there is a delay, as the UI app is redeployed on a periodic cycle. Once a day, I think? But not instant, for sure.