Mercurial > hg > xemacs-beta
annotate tests/automated/README @ 5916:1152e0091f8c
Avoid confusion about ELC vs. source file encoding, #'load, #'load-internal.
lisp/ChangeLog addition:
2015-06-03 Aidan Kehoe <kehoea@parhasard.net>
* code-files.el (load):
Revise this to respect load-ignore-out-of-date-elc-files, rather
than leaving that to #'load-internal. Avoids a corner case where
the source and the compiled file have different, incompatible
encodings.
Move the call to #'substitute-in-file-name here.
No longer check for a zero-length filename, since #'load-internal
no longer chokes on same and errors correctly.
src/ChangeLog addition:
2015-06-03 Aidan Kehoe <kehoea@parhasard.net>
* lread.c (Fload_internal):
Delegate calling the handler and #'substitute-in-file-name to #'load.
Error correctly with a zero-length file name, instead of giving a
bus error on my machine.
Delegate the check for out-of-date ELC files to #'load,
avoiding a bug where the encoding of the ELC file and the source
file differed.
* lread.c (PRINT_LOADING_MESSAGE_1):
This is simplified, now we no longer have to talk about
out-of-date ELC files.
tests/ChangeLog addition:
2015-06-03 Aidan Kehoe <kehoea@parhasard.net>
* automated/file-tests.el:
Gross sanity check for #'load and #'load-internal with a
zero-length FILE, something that crashed until today.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Wed, 03 Jun 2015 20:13:07 +0100 |
| 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'. |