In my recently released File::Finder module, I have the basic
tests to ensure that the find options are grabbed correctly,
and that the core and/or/not/parens logic is clean, along with
the easy test to ensure that eval() works.
However, to test the file operations, like "files named moe", I have
On Thu, Dec 18, 2003 at 01:28:57PM -0800, Randal L. Schwartz wrote:
> In my recently released File::Finder module, I have the basic
> tests to ensure that the find options are grabbed correctly,
> and that the core and/or/not/parens logic is clean, along with
> the easy test to ensure that eval() w
> "Michael" == Michael G Schwern <[EMAIL PROTECTED]> writes:
Michael> If you're not planning on your tests modifying the test tree at all,
Michael> you can probably just get away with having t/tree/... as a bunch of
Michael> normal files and directorys in the tarball. Don't ship a seperate
Mi
Op een winterige herfstdag (Thursday 18 December 2003 22:44), schreef Randal
L. Schwartz:
> > "Michael" == Michael G Schwern <[EMAIL PROTECTED]> writes:
>
> Michael> If you're not planning on your tests modifying the test tree at
> all, Michael> you can probably just get away with having t/tr
On Mon, Dec 01, 2003 at 01:45:22AM +0100, Paul Johnson wrote:
People seem to be using this module. I keep getting bug reports, suggestions
and even patches ;-)
Changes in this release:
- Merge data from files with identical MD5 checksums (Arthur Bergman).
- Add do test.
- Handle $x || return