Skip to content

Commit

Permalink
Fix #753, explain the point of skips (#755)
Browse files Browse the repository at this point in the history
Seems appropriate to link to the below section on disabling all skips, but I couldn't find examples of that happening elsewhere. Also not sure if tying the link in to github's style of id generation is desirable.
  • Loading branch information
awj authored and Insti committed Oct 26, 2017
1 parent e70b8fd commit ad26214
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions docs/TESTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,12 @@ Only the first test will be executed, all the others have been made pending
using the `skip` method. Delete or comment the next `skip` as you get
each test passing.

## Understanding Skips

The `skip` method instructs the test suite to not run a test. This is commonly used to avoid running tests of unimplemented functionality, so you can focus on the part you are currently working on.

The test run summary will list the number of skipped tests. You should disable all of the skips before completing an exercise.

## Customizing Test Reporting

If you want color, execute the tests with:
Expand Down

0 comments on commit ad26214

Please sign in to comment.