Mercurial > hg > xemacs-beta
view tests/automated/README @ 4984:f23cd0184dcf
xlike, doc changes
-------------------- ChangeLog entries follow: --------------------
man/ChangeLog addition:
2010-02-05 Ben Wing <ben@xemacs.org>
* internals/internals.texi (A Summary of the Various XEmacs Modules):
* internals/internals.texi (Conversion to and from External Data):
* internals/internals.texi (General Guidelines for Writing Mule-Aware Code):
Correct names of files renamed common -> xlike.
Fix up outdated explanation of old-style DFC conversion macros.
Add a section on the different types of character and their uses,
taken from a long comment in lisp.h.
src/ChangeLog addition:
2010-02-05 Ben Wing <ben@xemacs.org>
* depend:
Regenerate.
* make-src-depend (PrintPatternDeps):
Remove refs to xgccache, no longer existent.
* select-gtk.c (THIS_IS_GTK):
* select-gtk.c (gtk_decline_selection_request):
* select-x.c (THIS_IS_X):
* select-xlike-inc.c:
* select-xlike-inc.c (selection_data_to_lisp_data):
Rename PROCESSING_X_CODE to THIS_IS_X and PROCESSING_GTK_CODE to
THIS_SI_GTK for consistency with other xlike code.
Rename select-xlike-inc.c from select-common.h, in keeping with
xlike terminology.
author | Ben Wing <ben@xemacs.org> |
---|---|
date | Fri, 05 Feb 2010 12:11:12 -0600 |
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'.