Re: Unit testing built-in functions

[davidrw]

per perldoc for unlink, it returns the number of files deleted .. so can you just change the calls to something like this?

  if( unlink( $filename ) != 1 ){
    die "couldn't unlink '$filename': $!;
  }
# or:
  unlink( $filename ) or die "couldn't unlink '$filename': $!;

Your unit tests could also check for both the existance before the unlink, and non-existence afterward ...

[ikegami]

I believe you misunderstood. The OP wants to override unlink so he can test how the script handles errors from unlink. He's not asking how to check if unlink returned an error.

We do something similar at my workplace. In our test environment, we hook into the OS to control the exit codes returned by the disk reading function, the analog input reading function, the analog output writing function, etc. to ensure that our software properly handles those errors.

[aijin]

Yes, exactly.

I want to get built-in functions to return specific values when called from specific test cases.

It looks like over-rides and globals will be the easiest way to go so far.