Re: [Check-users] Dealing with stdout/err using check

[Chris N. <cne...@po...>]

On Sun, Jun 22, 2014 at 17:35:55 +0000, Aorimn wrote:
> Hi,
> 
> I'm testing some cases which are printing information on stdout or stderr.
> 
> Is there an integrated way to deal with stdout and stderr using check  
> or do I need to do it myself? Some kind of catching. Pattern matching  
> would be a bonus.

I would advise caution with implementing this in check itself,
because certain output formats (like TAP) rely on using Unix
stdio to work.  The way this generally works in the Perl world
(where TAP was born) is that stdio is mocked so that testing can
still work.  It wouldn't be very difficult to do this sort of
thing with C's stdio, either--just define private variants of the
functions that you need.  This gets a little more complicated if
your code explicitly writes to the stdout/stderr FILE * pointers,
or the [12] file descriptors.  I'll leave that as an exercise for
the reader. ;)

-- 
Chris Nehren