Mercurial > hg > xemacs-beta
annotate tests/automated/README @ 5015:d95c102a96d3
cleanups for specifier font stages, from ben-unicode-internal (preparation for eliminating shadowed warnings)
-------------------- ChangeLog entries follow: --------------------
src/ChangeLog addition:
2010-02-08 Ben Wing <ben@xemacs.org>
* faces.c:
* faces.c (face_property_matching_instance):
* faces.c (ensure_face_cachel_contains_charset):
* faces.h (FACE_FONT):
* lisp.h:
* lisp.h (enum font_specifier_matchspec_stages):
* objects-msw.c:
* objects-msw.c (mswindows_font_spec_matches_charset):
* objects-msw.c (mswindows_find_charset_font):
* objects-tty.c:
* objects-tty.c (tty_font_spec_matches_charset):
* objects-tty.c (tty_find_charset_font):
* objects-xlike-inc.c:
* objects-xlike-inc.c (XFUN):
* objects-xlike-inc.c (xft_find_charset_font):
* objects.c:
* objects.c (font_instantiate):
* objects.c (FROB):
* specifier.c:
* specifier.c (charset_matches_specifier_tag_set_p):
* specifier.c (call_charset_predicate):
* specifier.c (define_specifier_tag):
* specifier.c (Fdefine_specifier_tag):
* specifier.c (setup_charset_initial_specifier_tags):
* specifier.c (specifier_instance_from_inst_list):
* specifier.c (FROB):
* specifier.c (vars_of_specifier):
* specifier.h:
Rename the specifier-font-matching stages in preparation for
eliminating shadowed warnings, some other related fixes from
ben-unicode-internal.
1. Rename raw enums:
initial -> STAGE_INITIAL
final -> STAGE_FINAL
impossible -> NUM_MATCHSPEC_STAGES
2. Move `enum font_specifier_matchspec_stages' from
specifier.h to lisp.h.
3. Whitespace changes to match coding standards.
4. Eliminate unused second argument STAGE in charset predicates
that don't use it -- the code that calls the charset predicates
is now smart enough to supply the right number of arguments
automatically.
5. Add some long(ish) comments and authorial notices, esp. in
objects.c.
6. In specifier.c, change Vcharset_tag_lists from a vector over
leading bytes to a hash table over charsets. This change is
unnecessary currently but doesn't hurt and will be required
when we merge in Unicode-internal.
7. In specifier.c, extract out the code that calls charset predicates
into a function call_charset_predicate().
| author | Ben Wing <ben@xemacs.org> |
|---|---|
| date | Mon, 08 Feb 2010 16:51:25 -0600 |
| 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'. |