Mercurial > hg > xemacs-beta
annotate tests/automated/README @ 4568:1d74a1d115ee
Add #'query-coding-region tests; do the work necessary to get them running.
lisp/ChangeLog addition:
2008-12-28 Aidan Kehoe <kehoea@parhasard.net>
* coding.el (default-query-coding-region):
Declare using defun*, so we can #'return-from to it on
encountering a safe-charsets value of t. Comment out a few
debug messages.
(query-coding-region):
Correct the docstring, it deals with a region, not a string.
(unencodable-char-position):
Correct the implementation for non-nil COUNT, special-case a zero
value for count, treat it as one. Don't rely on dynamic scope when
calling the main lambda.
* unicode.el (unicode-query-coding-region):
Comment out some debug messages here.
* mule/mule-coding.el (8-bit-fixed-query-coding-region):
Comment out some debug messages here.
* code-init.el (raw-text):
Add a safe-charsets property to this coding system.
* mule/korean.el (iso-2022-int-1):
* mule/korean.el (euc-kr):
* mule/korean.el (iso-2022-kr):
Add safe-charsets properties for these coding systems.
* mule/japanese.el (iso-2022-jp):
* mule/japanese.el (jis7):
* mule/japanese.el (jis8):
* mule/japanese.el (shift-jis):
* mule/japanese.el (iso-2022-jp-1978-irv):
* mule/japanese.el (euc-jp):
Add safe-charsets properties for all these coding systems.
* mule/iso-with-esc.el:
Add safe-charsets properties to all the coding systems in
here. Comment on the downside of a safe-charsets value of t for
iso-latin-1-with-esc.
* mule/hebrew.el (ctext-hebrew):
Add a safe-charsets property for this coding system.
* mule/devanagari.el (in-is13194-devanagari):
Add a safe-charsets property for this coding system.
* mule/chinese.el (cn-gb-2312):
* mule/chinese.el (hz-gb-2312):
* mule/chinese.el (big5):
Add safe-charsets properties for these coding systems.
* mule/latin.el (iso-8859-14):
Add an implementation for this, using #'make-8-bit-coding-system.
* mule/mule-coding.el (ctext):
* mule/mule-coding.el (iso-2022-8bit-ss2):
* mule/mule-coding.el (iso-2022-7bit-ss2):
* mule/mule-coding.el (iso-2022-jp-2):
* mule/mule-coding.el (iso-2022-7bit):
* mule/mule-coding.el (iso-2022-8):
* mule/mule-coding.el (escape-quoted):
* mule/mule-coding.el (iso-2022-lock):
Add safe-charsets properties for all these coding systems.
src/ChangeLog addition:
2008-12-28 Aidan Kehoe <kehoea@parhasard.net>
* file-coding.c (Fmake_coding_system):
Document our use of the safe-chars and safe-charsets properties,
and the differences compared to GNU.
(make_coding_system_1): Don't drop the safe-chars and
safe-charsets properties.
(Fcoding_system_property): Return the safe-chars and safe-charsets
properties when asked for them.
* file-coding.h (CODING_SYSTEM_SAFE_CHARSETS):
* coding-system-slots.h:
Make the safe-chars and safe-charsets slots available in these
headers.
tests/ChangeLog addition:
2008-12-28 Aidan Kehoe <kehoea@parhasard.net>
* automated/query-coding-tests.el:
New file, testing the functionality of #'query-coding-region and
#'query-coding-string.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Sun, 28 Dec 2008 14:46:24 +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'. |