Re: Testing for NULL return values in test scripts

2005-04-13 Thread Tels
-BEGIN PGP SIGNED MESSAGE- Moin, On Wednesday 13 April 2005 22:52, Walter Goulet wrote: > So the good news is that I was able to convince the author to let me > include my dependancies in the test library. So I'll switch to > Test::More. > > Thanks for the help. Thats very good news! Be

Re: Testing for NULL return values in test scripts

2005-04-13 Thread Michael G Schwern
On Wed, Apr 13, 2005 at 03:52:43PM -0500, Walter Goulet wrote: > So the good news is that I was able to convince the author to let me > include my dependancies in the test library. So I'll switch to > Test::More. Huzzah for sanity!

Re: Testing for NULL return values in test scripts

2005-04-13 Thread Walter Goulet
So the good news is that I was able to convince the author to let me include my dependancies in the test library. So I'll switch to Test::More. Thanks for the help. On 4/12/05, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Tue, Apr 12, 2005 at 04:15:01PM -0500, Walter Goulet wrote: > > I thin

Re: Testing for NULL return values in test scripts

2005-04-12 Thread Michael G Schwern
On Tue, Apr 12, 2005 at 04:15:01PM -0500, Walter Goulet wrote: > I think the suggestion to use Test::Legacy was based on the statement > 'backwards compatibility reasons' require me to use Test.pm. I should > have been clearer in my explanation; the module author is not > permitting me to use any a

Re: Testing for NULL return values in test scripts

2005-04-12 Thread Michael G Schwern
On Tue, Apr 12, 2005 at 10:57:02PM +0200, Tels wrote: > > Try Test::Legacy, it gives you an upgrade path away from Test.pm. > > http://search.cpan.org/dist/Test-Legacy/ > > > > It almost perfectly emulates the Test.pm interface and it works in > > conjunction with other test modules. If you're wor

Re: Testing for NULL return values in test scripts

2005-04-12 Thread Walter Goulet
I think the suggestion to use Test::Legacy was based on the statement 'backwards compatibility reasons' require me to use Test.pm. I should have been clearer in my explanation; the module author is not permitting me to use any additional modules that aren't included in perl 5.6.0 to test his module

Re: Testing for NULL return values in test scripts

2005-04-12 Thread Tels
-BEGIN PGP SIGNED MESSAGE- Moin, On Tuesday 12 April 2005 22:15, Michael G Schwern wrote: > On Tue, Apr 12, 2005 at 01:39:59PM -0500, Walter Goulet wrote: > > I can't use Test::Simple, I have to use Test.pm for this module for > > backwards compatibility reasons. > > Try Test::Legacy, it

Re: Testing for NULL return values in test scripts

2005-04-12 Thread Michael G Schwern
On Tue, Apr 12, 2005 at 01:39:59PM -0500, Walter Goulet wrote: > I can't use Test::Simple, I have to use Test.pm for this module for > backwards compatibility reasons. Try Test::Legacy, it gives you an upgrade path away from Test.pm. http://search.cpan.org/dist/Test-Legacy/ It almost perfectly em

Re: Testing for NULL return values in test scripts

2005-04-12 Thread Walter Goulet
I can't use Test::Simple, I have to use Test.pm for this module for backwards compatibility reasons. I'm trying to replace this function call with an ok() call: $ctx = Net::SSLeay::SSL_CTX_new() or die ("Unable to create SSL context"); Hard to tell what $ctx is if SSL_CTX_new() fails; I know it

Re: Testing for NULL return values in test scripts

2005-04-12 Thread Steve Peters
On Tue, Apr 12, 2005 at 12:49:30PM -0500, Walter Goulet wrote: > Hi, > > I was wondering if there is a way to use the ok() function in Test.pm > to check for a null return value. It looks like the 3 arg form of ok() > I'm using only tests the first 2 args to see if they're equal. > > I'm consider