From ad26214945333a036a7842bb17648265983678e5 Mon Sep 17 00:00:00 2001 From: Adam Jones Date: Wed, 25 Oct 2017 22:58:38 -0600 Subject: [PATCH] Fix #753, explain the point of skips (#755) 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. --- docs/TESTS.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/TESTS.md b/docs/TESTS.md index 687cb46471..e56cde2487 100644 --- a/docs/TESTS.md +++ b/docs/TESTS.md @@ -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: