NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
drhyde (1683)
Wednesday July 23, 2003
05:15 AM
More on FFR::Permissions
If anyone has any suggestions for sane ways of thoroughly testing this module, please let me know. Unfortunately, a complete test suite would need to be able to change its EUID and consequently would need to be run as root. And to make matters worse, many machines won't have sufficiently complex user/group relationships *and* even the default usernames and group names aren't particularly predictable across platforms. Right now, the only test is that it loads and compiles, and users just have to trust me that I have tested the functionality myself.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Can't you just mock the system side? (Score:2, Interesting)
If it were me I'd mock everything that talks to the system:
Re:Can't you just mock the system side? (Score:1)
Re:Can't you just mock the system side? (Score:1)
That's why I write my tests first. The code tests the tests and the tests test the code. Ouroboric-driven development, that's what I always try to spell.