procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source 
(Tests and Their Environment): Mention skip-unless.
This commit is contained in:
Michael Albinus 2013-10-24 09:40:05 +02:00
parent 4ddbf12836
commit 955ada112b
2 changed files with 22 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/misc/ChangeLog
View file

@ -1,3 +1,8 @@
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:

20
doc/misc/ert.texi
View file

@ -183,9 +183,10 @@ tests run. It looks like this:
@example
Selector: t
Passed: 31
Failed: 2 (2 unexpected)
Total: 33/33
Passed: 31
Skipped: 0
Failed: 2 (2 unexpected)
Total: 33/33
Started at: 2008-09-11 08:39:25-0700
Finished.
@ -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