Hi, --- On Wed, Jul 22, 2009 at 4:46 PM, Thomas Schwinge <tschwi...@gnu.org> wrote: | Before installing these patches, I'd like to have a basic regression test | suite set-up that gives us some confidence that they don't in turn cause | breakage on other parts / uses of rpctrace. \--
Could you furnish more details? --- | Now, testing rpctrace is not like testing libpipe, where you simply come | up with some testing programs that use the libpipe C API and do some | consistency checks alongside. Testing rpctrace means running it against | testee programs, and then parse rpctrace's output and compare that | against a to-be-expected version. Some fuzzy comparisions will be | needed, as PIDs and all sort of other things will vary between two runs | of the same testee. Also some machinery to take care of hanging rpctrace | processes will be needed. \-- Could you give one documented example? --- | I guess that instead of starting to write shell scripts etc. for handling | all this, something like expect, <http://expect.nist.gov/>, or DejaGnu, | <http://www.gnu.org/software/dejagnu/>, should instead be used for this | task, but I have no experience with these. Is someone interested in | working on that? \-- Can we use Check (LGPL)? http://check.sourceforge.net/ SK -- Shakthi Kannan http://www.shakthimaan.com
