On 7/7/05, Yuval Kogman <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 05, 2005 at 23:57:10 +, Chris Hutchinson wrote:
>
> > For what it's worth, I wrote a trivial wrapper for TAP::HTMLMatrix to run
> > tests
> > in a chosen directory and write the html. It requires File::Find::Rule as
> > well
>
On Tue, Jul 05, 2005 at 04:52:34PM -0700, Michael G Schwern wrote:
> I think you're using export_to_level() wrong. $self should really be $class
> for starters. And the way you're using it symlink_ok() always gets
> exported even if the user says "use Test::Symlink ()". You should be passing
> i
On Wed, Jul 06, 2005 at 09:17:59AM +0100, Nik Clayton wrote:
> Hmm. The import() in Test::Symlink is exactly the same (mod
> s/ok/symlink_ok/) as the recommended import() from the Test::Builder
> SYNOPSIS (in Test::Simple 0.60).
>
> Do you mean that the SYNOPSIS in Test::Builder is also wrong?
On Wed, Jul 06, 2005 at 03:02:58PM +0100, Nik Clayton wrote:
> >Although I don't mind writing tests, I'd prefer a
> >test function that doesn't force me to think about the syntax of the test
> >function and let me focus on writing test cases to match the documentation.
>
> Although there are many
On Tue, Jul 05, 2005 at 23:57:10 +, Chris Hutchinson wrote:
> For what it's worth, I wrote a trivial wrapper for TAP::HTMLMatrix to run
> tests
> in a chosen directory and write the html. It requires File::Find::Rule as well
> as the Test::TAP modules. You can grab it from
> http://www.hutchi
Steve Peters wrote:
My concern with symlink_ok() is that I'll go to use it and
have to repeatedly check the syntax to see which should be the link and which
should be the file.
That's why the docs suggests using Perl's fat comma operator as an aid.
I agree,
symlink_ok('foo', 'bar');
is a
On Wed, Jul 06, 2005 at 09:17:59AM +0100, Nik Clayton wrote:
>
> "Small, sharp tools" and all that :-)
One of the smallest, sharpest tools I have is a script called C. It
takes a file name and a link name and creates a link to the file. The best
part is that it doesn't care about the order of
Michael,
Thanks for your comments.
Michael G Schwern wrote:
[re-ordered slightly]
There's no example code in the SYNOPSIS.
>
Your example code which uses Test::Symlink should show how to set up the
plan. Namely: use Test::Symlink tests => 2;
>
> It would be nice to see an example of the gen
On 7/5/05, Paul Johnson <[EMAIL PROTECTED]> wrote:
> "I feel your pain and I will share it". How far each author goes down
> the backwards compatibility route is obviously up to them, and as a
> volunteer effort no one has any right to get upset about their decision.
Wasn't one of the goals of C
On Mon, Jul 04, 2005 at 05:21:01PM +0200, Paul Johnson wrote:
>
> Unfortunately, upgrading isn't always an option. Anyone can type
>
> $ ./Configure -des && make && make test install
>
> but putting the results of such a command into a base operating system
> installation, testing that said o
10 matches
Mail list logo
