Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 5 additions & 17 deletions exercises/shared/.docs/help.md
Original file line number Diff line number Diff line change
@@ -1,21 +1,9 @@
# Help

<!-- TODO: write document
If you're having trouble, try these resources:

This document should contain track-specific instructions on how to get help when
the student is stuck.
- [Learning Resources](https://moonscript.org/#learning) on the MoonScript website.
- The [`moonscript` channel](https://discord.com/channels/454435414044966913/454435533792346142) on the MoonScript Discord.
- The [`get-help` channel](https://discord.com/channels/854117591135027261/1082698079163134073) on Exercism's Discord.

The instructions should be short and to the point.

You could link to resources like Gitter channels, forums or mailing lists:
whatever can help a student become unstuck.

This document should **not** link to Exercism-wide (track-agnostic) help resources,
as those resources will automatically be included in the HELP.md file.

The links in this document can overlap with those in docs/LEARNING.md or docs/RESOURCES.md

When a student downloads an exercise via the CLI, this file's contents are
included into the HELP.md file.

See https://exercism.org/docs/building/tracks/shared-files for more information. -->
Make sure you read the [installation instructions](https://exercism.org/docs/tracks/moonscript/installation) so you are set up correctly.
30 changes: 21 additions & 9 deletions exercises/shared/.docs/tests.md
Original file line number Diff line number Diff line change
@@ -1,15 +1,27 @@
# Tests
# Testing on the MoonScript Track

<!-- TODO: write document
Testing on the MoonScript track is exactly like [testing on the Lua track][lua-tests].
From an exercise directory, enter:

This document should contain instructions on how to run the exercise's tests.
```console
$ busted
```

The instructions should be short and to the point.
## Pending tests

The docs/TESTS.md file can contain a more verbose description on how to run tests.
This track follows Exercism's [Test-Driven Development][tdd] methodology.
You are given a complete test suite, but only the first test is "active".

When a student downloads an exercise via the CLI, this file's contents are
included into the HELP.md file.
To enable the tests, change a test's command from `pending` to `it`.

See https://exercism.org/docs/building/tracks/shared-files for more information.
-->
For those of you that like to run all the tests all the time, you can use a command-line tool to change them all at once.
Here's an example using perl (which is installed just about everywhere):

```console
$ perl -i -pe 's/^\s+\Kpending\b/it/' two_fer_spec.moon
```

When you are working in the online editor, the test runner will automatically run all the tests.

[lua-tests]: https://exercism.org/docs/tracks/lua/tests
[tdd]: https://exercism.org/docs/using/solving-exercises/tdd
Loading