aboutsummaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorBen Elliston <bje@gnu.org>2016-02-15 15:00:53 +1100
committerBen Elliston <bje@gnu.org>2016-02-15 15:00:53 +1100
commitd506c9a5943ac7789e4178d06c9362a79e055f78 (patch)
tree713029fec1abb452904fe623c56e6dde9650f00e /TODO
parent03f6140a1775318016c5de0f0e2613139a94bf06 (diff)
downloaddejagnu-d506c9a5943ac7789e4178d06c9362a79e055f78.zip
dejagnu-d506c9a5943ac7789e4178d06c9362a79e055f78.tar.gz
dejagnu-d506c9a5943ac7789e4178d06c9362a79e055f78.tar.bz2
* TODO: Update.
Diffstat (limited to 'TODO')
-rw-r--r--TODO40
1 files changed, 0 insertions, 40 deletions
diff --git a/TODO b/TODO
index 0940dda..5d4eb0c 100644
--- a/TODO
+++ b/TODO
@@ -9,43 +9,3 @@ Bigger items
* Add more support for target boards and RTOSes.
* Use the new expect terminal support for an "escape codes" API.
* Use expectk and write a GUI testing API, complete with record/playback.
-
-Documentation
-=============
-
-* Add a "testing methodologies" section to the manual.
-
-
-From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
-Subject: my dejagnu wish list
-Newsgroups: gmane.comp.sysutils.dejagnu.general
-Date: Sat, 31 Jan 2004 21:02:21 -0500 (EST)
-
-My wish list for dejagnu:
-
-. clean up the exit status value.
-
- The current situation is:
-
- 1 a FAIL, XPASS, KPASS, or UNRESOLVED result occurred
- 1 an unknown TCL procedure was called
- 1 --status option and a TCL error happened
- 0 all other cases
-
- I would like to see something like:
-
- 0 all tests are okay
- 1 at least one test is not okay (FAIL, XPASS, KPASS, UNRESOLVED)
- 2 a TCL error occured
- 130 user hit ^C (SIGINT)
- 131 user hit ^\ (SIGQUIT)
-
- The important part is that I want to detect whether dejagnu ran
- to completion or whether the user interrupted it with ^C or ^\.
-
-. When the compiler produces error messages, default_target_compile
- calls "verbose -log ...". There is no need for "-log", because
- runtest.exp already turned on "expect" logging with
- "log_file -a $outdir/$tool.log", so there is already a copy of
- the compiler output in the log file. Just "verbose ..." or
- nothing at all.