Mercurial > hg > xemacs-beta
annotate tests/automated/README @ 1365:02909207294a
[xemacs-hg @ 2003-03-20 13:19:56 by youngs]
2003-03-20 Steve Youngs <youngs@xemacs.org>
* menubar-items.el (default-menubar): Add a "Pre-Release Download
Sites" submenu to "Tools -> Packages" menu.
Filter the package download sites menus through
`menu-split-long-menu'.
* obsolete.el (pui-add-install-directory): New.
(package-get-download-menu): New.
* package-admin.el: (package-admin-add-single-file-package):
Removed.
(package-admin-get-install-dir): Don't rely on an installed
xemacs-base package to guess where a package needs to be installed
to.
(package-admin-get-manifest-file): Whitespace clean up.
(package-admin-check-manifest): Use `directory-sep-char' to
compute regexp.
Only search 'lisp' and 'man' directories to determine package
name.
Don't error is xemacs-base package isn't installed, just don't
sort the MANIFEST file and issue a warning.
(package-admin-add-binary-package): Whitespace clean up.
(package-admin-get-lispdir): Ditto.
(package-admin-delete-binary-package): Use `with-temp-buffer'
instead of creating a temporary buffer manually.
* package-get.el: (package-get-remote): Change custom type so that
only either a single directory or remote host:directory can be
selected.
(package-get-download-sites): Put the sites into alphabetical
order of country.
Make the description element be "Country (site)" instead of the
other way around.
(package-get-pre-release-download-sites): New.
(package-get-require-signed-base-updates): Default to t.
(package-get-download-menu): Removed.
(package-get-locate-file): Change to reflect new format of
'package-get-remote'.
(package-get-update-base-from-buffer): Whitespace clean up and
remove an unneccessary 'when'.
(package-get-interactive-package-query): Whitespace clean up.
(package-get-update-all): Ditto.
(package-get-all): Ditto.
(package-get-init-package): Ditto.
(package-get-info): New.
(package-get): Bring into line with new format of
'package-get-remote'.
Error if non-Mule XEmacsen try to install Mule packages.
Don't rely on a Mule package having 'mule-base' in its
"REQUIRES" to determine if it is a Mule package or not,
instead we test "CATEGORY".
Better handling of the situation where a partial package tarball
exists on the local hard drive from a previous interupted
download.
Clean up after a failed package install.
(package-get-set-version-prop): Removed.
(package-get-installedp): Whitespace clean up.
* package-ui.el: Whitespace clean up.
(pui-info-buffer): Make it a defcustom.
(pui-directory-exists): Removed.
(pui-package-dir-list): Removed.
(pui-add-install-directory): Removed.
(package-ui-download-menu): New.
(package-ui-pre-release-download-menu): New.
(pui-set-local-package-get-directory): New.
(pui-package-symbol-char): Whitespace clean up.
(pui-update-package-display): Ditto.
(pui-toggle-package): Ditto.
(pui-toggle-package-key): Ditto.
(pui-toggle-package-delete): Ditto.
(pui-toggle-package-delete-key): Ditto.
(pui-toggle-package-event): Ditto.
(pui-toggle-verbosity-redisplay): Ditto.
(pui-install-selected-packages): Ditto.
(pui-help-echo): Ditto.
(pui-display-info): Ditto.
(pui-list-packages): Ditto.
* packages.el: Whitespace clean up.
author | youngs |
---|---|
date | Thu, 20 Mar 2003 13:19:59 +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'. |