Re: Why a taint flag on test files?

The obvious reason for testing that a module works under taint is that at some point someone might try to use your module within a taint-enabled program.

Dave.

Comment on Re: Why a taint flag on test files?

Replies are listed 'Best First'.
Re^2: Why a taint flag on test files? by xdg (Monsignor) on Oct 13, 2005 at 21:28 UTC
Testing a module under taint, I get. But on every test file? Even ones like pod-coverage that aren't running any code of yours? And if it's a good practice, why wouldn't that be the default for boilerplate-generated test scripts? -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply]

Replies are listed 'Best First'.

Re^2: Why a taint flag on test files?
by xdg (Monsignor) on Oct 13, 2005 at 21:28 UTC

Testing a module under taint, I get. But on every test file? Even ones like pod-coverage that aren't running any code of yours? And if it's a good practice, why wouldn't that be the default for boilerplate-generated test scripts?

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

[reply]