httpd-test-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-test/perl-framework/Apache-Test/lib/Apache
Date Tue, 28 Sep 2004 23:25:21 GMT
stas        2004/09/28 16:25:21

  Modified:    perl-framework/Apache-Test/lib/Apache
  explain why one needs to use need c1, c2, c3 and not c1 && c2 && c3 in the
  skip rule
  Revision  Changes    Path
  1.102     +21 -0     httpd-test/perl-framework/Apache-Test/lib/Apache/
  RCS file: /home/cvs/httpd-test/perl-framework/Apache-Test/lib/Apache/,v
  retrieving revision 1.101
  retrieving revision 1.102
  diff -u -u -r1.101 -r1.102
  ---	15 Sep 2004 13:15:25 -0000	1.101
  +++	28 Sep 2004 23:25:21 -0000	1.102
  @@ -769,6 +769,27 @@
   It's possible to put more than one requirement into a single hash
   reference, but be careful that the keys will be different.
  +It's also important to mention to avoid using:
  +  plan tests => 1, requirement1 && requirement2;
  +technique. While test-wise that technique is equivalent to:
  +  plan tests => 1, need requirement1, requirement2;
  +since the test will be skipped, unless all the rules are satisfied,
  +it's not equivalent for the end users. The second technique, deploying
  +C<need()> and a list of requirements, always runs all the requirement
  +checks and reports all the missing requirements. In the case of the
  +first technique, if the first requirement fails, the second is not
  +run, and the missing requirement is not reported. So let's say all the
  +requirements are missing Apache modules, and a user wants to satisfy
  +all of these and run the test suite again. If all the unsatisfied
  +requirements are reported at once, she will need to rebuild Apache
  +once. If only one requirement is reported at a time, she will have to
  +rebuild Apache as many times as there are elements in the C<&&>
   Also see plan().
   =item under_construction

View raw message