Mercurial > hg > xemacs-beta
view tests/automated/README @ 4318:4d0f773d5e21
Fix the test failures introduced by the non-ISO-2022 coding systems.
APPROVE COMMIT
NOTE: this patch has been committed.
This is patch http://mid.gmane.org/18264.25814.828088.486899@parhasard.net
tests/ChangeLog addition:
2007-12-06 Aidan Kehoe <kehoea@parhasard.net>
* automated/mule-tests.el:
Add a Known-Bug-Expect-Error call testing and documenting that we
don't support all of the Unicode code space in a single session.
* automated/test-harness.el (Known-Bug-Expect-Error):
Provide Known-Bug-Expect-Error, analagous to
Known-Bug-Expect-Failure and Check-Error.
* automated/test-harness.el (Silence-Message):
Dynamically bind the function definition of #'clear-message, as
well as that of #'append-message, to nil.
src/ChangeLog addition:
2007-12-06 Aidan Kehoe <kehoea@parhasard.net>
* tests.c (Ftest_data_format_conversion):
Move those tests that expect that iso-8859-2 is ISO
2022-compatible to testing iso-latin-2-with-esc instead.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Sun, 09 Dec 2007 15:10:46 +0100 |
parents | 74fd4e045ea6 |
children |
line wrap: on
line source
This directory contains XEmacs' automated test suite. The usual way of running all the tests is running `make check' from the top-level source directory. The test suite is unfinished and it's still lacking some essential features. It is nevertheless recommended that you run the tests to confirm that XEmacs behaves correctly. If you want to run a specific test case, you can do it from the command-line like this: $ xemacs -batch -l test-harness.elc -f batch-test-emacs TEST-FILE If something goes wrong, you can run the test suite interactively by loading `test-harness.el' into a running XEmacs and typing `M-x test-emacs-test-file RET <filename> RET'. You will see a log of passed and failed tests, which should allow you to investigate the source of the error and ultimately fix the bug. Adding a new test file is trivial: just create a new file here and it will be run. There is no need to byte-compile any of the files in this directory -- the test-harness will take care of any necessary byte-compilation. Look at the existing test cases for the examples of coding test cases. It all boils down to your imagination and judicious use of the macros `Assert', `Check-Error', `Check-Error-Message', and `Check-Message'.