comparison tests/automated/test-harness.el @ 4368:1740095ec116

Automated merge with file:/Sources/xemacs-21.5-checked-out
author Aidan Kehoe <kehoea@parhasard.net>
date Sun, 30 Dec 2007 15:34:02 +0100
parents 7b628daa39d4
children bceb3e285ae7
comparison
equal deleted inserted replaced
4367:69e6352406f0 4368:1740095ec116
69 69
70 ;; Declared for dynamic scope; _do not_ initialize here. 70 ;; Declared for dynamic scope; _do not_ initialize here.
71 (defvar unexpected-test-file-failures) 71 (defvar unexpected-test-file-failures)
72 72
73 (defvar test-harness-test-compiled nil 73 (defvar test-harness-test-compiled nil
74 "Non-nil means the test code was compiled before execution.") 74 "Non-nil means the test code was compiled before execution.
75
76 You probably should not make tests depend on compilation.
77 However, it can be useful to conditionally change messages based on whether
78 the code was compiled or not. For example, the case that motivated the
79 implementation of this variable:
80
81 \(when test-harness-test-compiled
82 ;; this ha-a-ack depends on the failing compiled test coming last
83 \(setq test-harness-failure-tag
84 \"KNOWN BUG - fix reverted; after 2003-10-31 notify stephen\n\"))")
75 85
76 (defvar test-harness-verbose 86 (defvar test-harness-verbose
77 (and (not noninteractive) (> (device-baud-rate) search-slow-speed)) 87 (and (not noninteractive) (> (device-baud-rate) search-slow-speed))
78 "*Non-nil means print messages describing progress of emacs-tester.") 88 "*Non-nil means print messages describing progress of emacs-tester.")
79 89