Mercurial > hg > xemacs-beta
comparison tests/automated/README @ 398:74fd4e045ea6 r21-2-29
Import from CVS: tag r21-2-29
| author | cvs |
|---|---|
| date | Mon, 13 Aug 2007 11:13:30 +0200 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 397:f4aeb21a5bad | 398:74fd4e045ea6 |
|---|---|
| 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'. |