Mailing-List: contact test-cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: test-dev@httpd.apache.org
Date: 24 Dec 2001 05:46:52 -0000
Message-ID: <20011224054652.6475.qmail@icarus.apache.org>
From: stas@apache.org
To: httpd-test-cvs@apache.org
Subject: cvs commit: httpd-test/perl-framework/Apache-Test/lib/Apache Test.pm

stas        01/12/23 21:46:51

  Modified:    perl-framework/Apache-Test/lib/Apache Test.pm
  Log:
  - improve skip_unless docs
  
  Revision  Changes    Path
  1.42      +6 -5      httpd-test/perl-framework/Apache-Test/lib/Apache/Test.pm
  
  Index: Test.pm
  ===================================================================
  RCS file: /home/cvs/httpd-test/perl-framework/Apache-Test/lib/Apache/Test.pm,v
  retrieving revision 1.41
  retrieving revision 1.42
  diff -u -r1.41 -r1.42
  --- Test.pm	2001/12/23 15:29:43	1.41
  +++ Test.pm	2001/12/24 05:46:51	1.42
  @@ -395,11 +395,12 @@
   whole test or not. plan() won't be reached if skip_unless decides to skip
   the test.
   
  -skip_unless's argument is a list of things to test. The list can include
  -scalars, which are passed to have_module(), and hash references. The
  -hash references have condition code ref as a key and the reason for
  -failure as a value. The condition code is run and if it fails the
  -reason is used to explain the failure.
  +skip_unless()'s argument is a list of things to test. The list can
  +include scalars, which are passed to have_module(), and hash
  +references. The hash references have a condition code reference as a
  +key and a reason for failure as a value. The condition code is run and
  +if it fails the provided reason is used to tell user why the test was
  +skipped.
   
   Also see plan().