1d522f475SmrgTests for xterm:
2d522f475Smrg
3d522f475SmrgIf system supports window size (i.e., some combination of SIGWINCH,
4d522f475SmrgTIOCSSIZE, TIOCSWINSZ), start a full-screen program (e.g., Emacs,
5d522f475SmrgJove, vi) and resize the xterm window.  The program must immediately
6d522f475Smrgupdate its screen image for the new size.
7d522f475Smrg
8d522f475SmrgIf compiled with -DUTMP, starting a new xterm should create a new utmp
9d522f475Smrgentry.  ("who" will show this info.)  Exiting xterm should remove the
10d522f475Smrgentry.  Killing the xterm window (or other unnatural exit) should also
11d522f475Smrgremove the entry.  When should entries be made in the wtmp file?
12d522f475Smrg
13d522f475SmrgProcess group stuff should be correct.
14d522f475Smrg
15d522f475SmrgShould work without access to /dev/tty, say started from an xdm
16d522f475Smrgstarted from a boot-time script.
17d522f475Smrg
18d522f475SmrgIf "xterm -help" offers the -C option, it should work.
19d522f475Smrg
20d522f475Smrgecho "test" > /dev/tty
21d522f475Smrg
22d522f475Smrgvi with lines that wrap.
23d522f475Smrg
24d522f475SmrgExec'ing things other than shells.
25d522f475Smrg
26d522f475SmrgAnother thing that has caused problems in the past is process groups,
27d522f475Smrgespecially w.r.t. signal propagation to the child.
28d522f475Smrg
29d522f475SmrgPopup menu signals: running only a shell, click on "Send INT Signal."
30d522f475SmrgDo you get a new prompt from the shell?  (Same as typing ^C at it.)
31d522f475Smrg
32d522f475SmrgShould scroll *fast* with jumpScroll enabled.
33d522f475Smrg
34d522f475SmrgWhile a mouse button is down tracing out a selection, output to the
35d522f475Smrgscreen should be suspended.
36d522f475Smrg
37d522f475SmrgSelections more than one screen long.
38d522f475Smrg
39d522f475Smrgstart xterm running only Tek widget: "xterm -t"
40d522f475Smrg
41d522f475Smrg
42d522f475SmrgPlease add to this list if you find xterm failing in some way.
43