On Fri, Dec 18, 2009 at 11:50 PM, Eric Pouech <eric.pou...@orange.fr> wrote: > If you want to control more closely commands vs output you can toy with > http://github.com/ericZp/wdtp/blob/master/test_cl.h
I would have thought that overkill for a batch mode program like cmd, but it appears to have several interactive commands: pause choice set /p so yeah, something like that will be needed. Then there's the question of how to integrate it into the wine test suite. I suspect the way to go is to have a make rule that converts the input and expected output files into hex byte arrays in a generated .c file, to use the normal wine test infrastructure by copying dlls/Maketest.rules.in to programs/Maketest.rules.in Sound good?