screen scraping or reading output of program
(terminal control sequences)
I was suggesting precisely to avoid any such "interpretation" of info
output by running the tests non-interactively (e.g., input via
--dribble), and compare the output from info dumping nodes to "expected"
output, as usual. Maybe one of the -escapes options is enough to avoid
terminal dependency.
you have to take care that the test framework is not as complicated
and error-prone as the program being tested.
100% agreed.
There can probably be a simple test framework with incomplete coverage
in some areas, which would still be useful.
100% agreed. Heck, even if there were only tests for non-interactive
features (--help, --version, --whatis, etc.), that would be a lot better
than the nothing we have now.
Anyway, thanks for all.
karl
