Re: mocking or trapping system calls

I'd write a subroutine that

calls system on the command, redirecting STDOUT to a fixed name (say, /log/application.out)
if successful, read the file back in

Comment on Re: mocking or trapping system calls

Replies are listed 'Best First'.
Re^2: mocking or trapping system calls by almut (Canon) on May 09, 2008 at 15:58 UTC
...but that won't help if the "commands are either executable only by the root-user and/or do things you'd rather not do in a test" — as desired by the OP.	[reply]