annotate tests/automated/README @ 578:190b164ddcac
[xemacs-hg @ 2001-05-25 11:26:50 by ben]
device-msw.c, eldap.c, emodules.c, hpplay.c, process-unix.c, sound.h, tooltalk.c, win32.c: Revert Martin's attempted compile-warnings fix. It does fix
the warnings, but not the right way. We are trying to eliminate
the raw use of `char' and `unsigned char' absolutely everywhere.
There is never an occasion to reintroduce these.
buffer.h: Instead, we fix these macros so they don't care about the type of
their lvalues. We already do this for the non-C-string
equivalents of these, and it's correct because it should be OK to
pass in an SBufbyte *, for example. In any case, we do not need
any type-correctness checking here -- errors will be caught for
sure as soon as we remove the -Wno-sign-compare switch.
mule-charset.c: Use invalid_argument, not generic signal_error (Qerror, ).
alloc.c, chartab.c, console-gtk.c, console-msw.c, console-stream.c, console-stream.h, console-tty.c, console-tty.h, console-x.c, console.c, console.h, device-x.c, device.c, elhash.c, eval.c, faces.c, faces.h, fns.c, glyphs.c, glyphs.h, gui.c, gui.h, lisp.h, lread.c, nt.c, objects-gtk.c, objects-gtk.h, objects-msw.c, objects-tty.c, objects-x.c, objects.c, process-unix.c, rangetab.c, search.c, specifier.c, toolbar.c, window.c, window.h:
Rename Error_behavior to Error_Behavior, to be consistent with
general naming practices (Lisp_Object, Char_Binary, etc.).
author |
ben |
date |
Fri, 25 May 2001 11:27:01 +0000 |
parents |
74fd4e045ea6 |
children |
|
rev |
line source |
398
|
1 This directory contains XEmacs' automated test suite. The usual way
|
|
2 of running all the tests is running `make check' from the top-level
|
|
3 source directory.
|
|
4
|
|
5 The test suite is unfinished and it's still lacking some essential
|
|
6 features. It is nevertheless recommended that you run the tests to
|
|
7 confirm that XEmacs behaves correctly.
|
|
8
|
|
9 If you want to run a specific test case, you can do it from the
|
|
10 command-line like this:
|
|
11
|
|
12 $ xemacs -batch -l test-harness.elc -f batch-test-emacs TEST-FILE
|
|
13
|
|
14 If something goes wrong, you can run the test suite interactively by
|
|
15 loading `test-harness.el' into a running XEmacs and typing
|
|
16 `M-x test-emacs-test-file RET <filename> RET'. You will see a log of
|
|
17 passed and failed tests, which should allow you to investigate the
|
|
18 source of the error and ultimately fix the bug.
|
|
19
|
|
20 Adding a new test file is trivial: just create a new file here and it
|
|
21 will be run. There is no need to byte-compile any of the files in
|
|
22 this directory -- the test-harness will take care of any necessary
|
|
23 byte-compilation.
|
|
24
|
|
25 Look at the existing test cases for the examples of coding test cases.
|
|
26 It all boils down to your imagination and judicious use of the macros
|
|
27 `Assert', `Check-Error', `Check-Error-Message', and `Check-Message'.
|