Mercurial > hg > xemacs-beta

comparison tests/ChangeLog @ 5040:3daf9fc57cd4

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
fixes to test harness to allow backtracing/debugging of failures -------------------- ChangeLog entries follow: -------------------- tests/ChangeLog addition: 2010-02-20 Ben Wing <ben@xemacs.org> * automated/test-harness.el: * automated/test-harness.el (test-harness-bug-expected): New. * automated/test-harness.el (test-harness-unexpected-error-enter-debugger): New. * automated/test-harness.el (test-harness-assertion-failure-enter-debugger): New. * automated/test-harness.el (test-harness-unexpected-error-show-backtrace): New. * automated/test-harness.el (test-harness-assertion-failure-show-backtrace): New. * automated/test-harness.el (test-harness-assertion-failure-do-debug): New. * automated/test-harness.el (test-harness-unexpected-error-do-debug): New. * automated/test-harness.el (test-harness-unexpected-error-condition-handler): New. * automated/test-harness.el (test-harness-error-wrap): New. * automated/test-harness.el (test-harness-from-buffer): New variables that allow a backtrace to be displayed and/or the debugger to be entered when an assertion failure or unexpected error occurs. By default, debugging occurs when interactive and debug-on-error is set, and backtrace-displaying occurs either (a) when stack-trace-on-error is set, or (b) always, when an unexpected error occurs. (However, no backtracing or debugging occurs when a bug is expected.)
author Ben Wing <ben@xemacs.org>
date Sat, 20 Feb 2010 20:04:44 -0600
parents 9624523604c5
children 548f1f47eb82
comparison
equal deleted inserted replaced
5039:f8ae1031c706 5040:3daf9fc57cd4
1 2010-02-20 Ben Wing <ben@xemacs.org>
2
3 * automated/test-harness.el:
4 * automated/test-harness.el (test-harness-bug-expected): New.
5 * automated/test-harness.el (test-harness-unexpected-error-enter-debugger): New.
6 * automated/test-harness.el (test-harness-assertion-failure-enter-debugger): New.
7 * automated/test-harness.el (test-harness-unexpected-error-show-backtrace): New.
8 * automated/test-harness.el (test-harness-assertion-failure-show-backtrace): New.
9 * automated/test-harness.el (test-harness-assertion-failure-do-debug): New.
10 * automated/test-harness.el (test-harness-unexpected-error-do-debug): New.
11 * automated/test-harness.el (test-harness-unexpected-error-condition-handler): New.
12 * automated/test-harness.el (test-harness-error-wrap): New.
13 * automated/test-harness.el (test-harness-from-buffer):
14 New variables that allow a backtrace to be displayed and/or the
15 debugger to be entered when an assertion failure or unexpected error
16 occurs. By default, debugging occurs when interactive and debug-on-error
17 is set, and backtrace-displaying occurs either
18 (a) when stack-trace-on-error is set, or (b) always, when an unexpected
19 error occurs. (However, no backtracing or debugging occurs when a bug
20 is expected.)
21
1 2010-02-19 Aidan Kehoe <kehoea@parhasard.net> 22 2010-02-19 Aidan Kehoe <kehoea@parhasard.net>
2 23
3 * automated/lisp-tests.el: 24 * automated/lisp-tests.el:
4 Change the #'split-string-by-char text to use US federal 25 Change the #'split-string-by-char text to use US federal
5 government information instead of a couple of sentences from the 26 government information instead of a couple of sentences from the