annotate tests/automated/README @ 5191:71ee43b8a74d
Add #'equalp as a hash test by default; add #'define-hash-table-test, GNU API
tests/ChangeLog addition:
2010-04-05 Aidan Kehoe <kehoea@parhasard.net>
* automated/hash-table-tests.el:
Test the new built-in #'equalp hash table test. Test
#'define-hash-table-test.
* automated/lisp-tests.el:
When asserting that two objects are #'equalp, also assert that
their #'equalp-hash is identical.
man/ChangeLog addition:
2010-04-03 Aidan Kehoe <kehoea@parhasard.net>
* lispref/hash-tables.texi (Introduction to Hash Tables):
Document that we now support #'equalp as a hash table test by
default, and mention #'define-hash-table-test.
(Working With Hash Tables): Document #'define-hash-table-test.
src/ChangeLog addition:
2010-04-05 Aidan Kehoe <kehoea@parhasard.net>
* elhash.h:
* elhash.c (struct Hash_Table_Test, lisp_object_eql_equal)
(lisp_object_eql_hash, lisp_object_equal_equal)
(lisp_object_equal_hash, lisp_object_equalp_hash)
(lisp_object_equalp_equal, lisp_object_general_hash)
(lisp_object_general_equal, Feq_hash, Feql_hash, Fequal_hash)
(Fequalp_hash, define_hash_table_test, Fdefine_hash_table_test)
(init_elhash_once_early, mark_hash_table_tests, string_equalp_hash):
* glyphs.c (vars_of_glyphs):
Add a new hash table test in C, #'equalp.
Make it possible to specify new hash table tests with functions
define_hash_table_test, #'define-hash-table-test.
Use define_hash_table_test() in glyphs.c.
Expose the hash functions (besides that used for #'equal) to Lisp,
for people writing functions to be used with #'define-hash-table-test.
Call define_hash_table_test() very early in temacs, to create the
built-in hash table tests.
* ui-gtk.c (emacs_gtk_boxed_hash):
* specifier.h (struct specifier_methods):
* specifier.c (specifier_hash):
* rangetab.c (range_table_entry_hash, range_table_hash):
* number.c (bignum_hash, ratio_hash, bigfloat_hash):
* marker.c (marker_hash):
* lrecord.h (struct lrecord_implementation):
* keymap.c (keymap_hash):
* gui.c (gui_item_id_hash, gui_item_hash):
* glyphs.c (image_instance_hash, glyph_hash):
* glyphs-x.c (x_image_instance_hash):
* glyphs-msw.c (mswindows_image_instance_hash):
* glyphs-gtk.c (gtk_image_instance_hash):
* frame-msw.c (mswindows_set_title_from_ibyte):
* fontcolor.c (color_instance_hash, font_instance_hash):
* fontcolor-x.c (x_color_instance_hash):
* fontcolor-tty.c (tty_color_instance_hash):
* fontcolor-msw.c (mswindows_color_instance_hash):
* fontcolor-gtk.c (gtk_color_instance_hash):
* fns.c (bit_vector_hash):
* floatfns.c (float_hash):
* faces.c (face_hash):
* extents.c (extent_hash):
* events.c (event_hash):
* data.c (weak_list_hash, weak_box_hash):
* chartab.c (char_table_entry_hash, char_table_hash):
* bytecode.c (compiled_function_hash):
* alloc.c (vector_hash):
Change the various object hash methods to take a new EQUALP
parameter, hashing appropriately for #'equalp if it is true.
| author |
Aidan Kehoe <kehoea@parhasard.net> |
| date |
Mon, 05 Apr 2010 13:03:35 +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'.
|
