* ert.texi (Running Tests Interactively): Adapt examle output.

(Tests and Their Environment): Mention skip-unless.

doc/misc/ChangeLog

+2013-10-24  Michael Albinus  <michael.albinus@gmx.de>
+
+	* ert.texi (Running Tests Interactively): Adapt examle output.
+	(Tests and Their Environment): Mention skip-unless.
+
 2013-10-23  Glenn Morris  <rgm@gnu.org>
 
 	* dired-x.texi, ebrowse.texi, ede.texi, eieio.texi, eshell.texi:

doc/misc/ert.texi

@@ -184,6 +184,7 @@ tests run.  It looks like this:
 @example
 Selector: t
 Passed:  31
+Skipped: 0
 Failed:  2 (2 unexpected)
 Total:   33/33
 
@@ -454,6 +455,19 @@ versions, specific architectures, etc.:
 @node Tests and Their Environment
 @section Tests and Their Environment
 
+Sometimes, it doesn't make sense to run a test due to missing
+preconditions.  A required Emacs feature might not be compiled in, the
+function to be tested could call an external binary which might not be
+available on the test machine, you name it.  In this case, the macro
+@code{skip-unless} could be used to skip the test:
+
+@lisp
+(ert-deftest test-dbus ()
+  "A test that checks D-BUS functionality."
+  (skip-unless (featurep 'dbusbind))
+  ...)
+@end lisp
+
 The outcome of running a test should not depend on the current state
 of the environment, and each test should leave its environment in the
 same state it found it in.  In particular, a test should not depend on