in reply to Re^2: Unit testing OS rich code
in thread Unit testing OS rich code

I really don't like having filesystem state for tests.

If your code manipulates the filesystem, how will you know if it works unless you test that it manipulates the filesystem?

Improve your skills with Modern Perl: the free book.

Replies are listed 'Best First'.
Re^4: Unit testing OS rich code
by Voronich (Hermit) on Oct 12, 2011 at 20:30 UTC
    At some point you have to trust that the primitives are doing their job. Otherwise "full code coverage" would always include unit tests that cover perl itself. So keeping an onion-skin layer on top allows me to preserve testability.
    Me
[reply]

In Section Seekers of Perl Wisdom