kc3-lang/automake/t/tap-test-number-0.sh

• Show log

  Commit

• Hash : ffd4ecc9
  Author :
  Date : 2013-05-20T11:23:01
  

  tests: better idiom to override make macro defs on the cmdline
  
  We now do so with a new wrapper shell function 'run_make()', which
  relies on the use of AM_MAKEFLAGS, avoiding the use of the '-e' make
  option.  The use of that option (that causes the environment variables
  to take precedence over the macro definitions in the Makefile) has
  proved to be quite brittle in the past, causing annoying and sometimes
  problematic spurious failures.  This has worsened in some still
  unpublished work going on in development branches.  It's time to solve
  the issue once and for all.
  
  Note that we do not convert all uses of $MAKE in the testsuite right
  away; we might do so in follow-up changes, with leisure, to avoid a
  "patch bomb" effect (this commit is already too much of a bomb itself).
  What we do in this commit is to get rid of all "$MAKE -e" invocations.
  
  We admit that the implementation and feature-set of 'run_make()' are
  far from perfect, but good enough for our current purposes.  We'll
  improve 'run_make()' if and when the need arises.
  
  * syntax-checks.mk (sc_tests_no_make_e): New syntax check, guard against
  the use of "$MAKE -e".
  (syntax_check_rules): Add it.
  (sc_tests_overriding_macros_on_cmdline): Adjust.
  (lint): New, alias for 'maintainer-check', for lazy typists.  Idea
  backported from the 'maint' branch (Automake 1.13a).
  * t/ax/am-test-lib.sh (run_make): New function.  Run $MAKE with the
  given command-line arguments, handling command-line override of variable
  definitions in a smart way (using AM_MAKEFLAGS if a non-GNU make
  implementation is detected to be in use).
  (useless_vpath_rebuild): Adjust to use 'run_make', to avoid a spurious
  maintainer check failure.
  (yl_distcheck): Use 'run_make' rather than bare '$MAKE'.
  (single_quote, append_single_quoted, is_valid_varname): New auxiliary
  function, used, directly or indirectly, by it.
  * Many tests: Adjust to avoid the use of "$MAKE -e", and prefer the
  use of 'run_make' in few other contexts as well, where it makes sense.
  Other minor fixlets while at it.
  
  Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
  

Download

• t/tap-test-number-0.sh

• #! /bin/sh
  # Copyright (C) 2011-2013 Free Software Foundation, Inc.
  #
  # This program is free software; you can redistribute it and/or modify
  # it under the terms of the GNU General Public License as published by
  # the Free Software Foundation; either version 2, or (at your option)
  # any later version.
  #
  # This program is distributed in the hope that it will be useful,
  # but WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  # GNU General Public License for more details.
  #
  # You should have received a copy of the GNU General Public License
  # along with this program.  If not, see <http://www.gnu.org/licenses/>.
  
  # TAP support:
  #  - a test result numbered as 0 is to be considered out-of-order
  # This is consistent with the behaviour of the 'prove' utility.
  
  . test-init.sh
  
  if test $am_tap_implementation = perl; then
    $PERL -MTAP::Parser -e 1 \
      || skip_ "cannot import TAP::Parser perl module"
    if $PERL -w -e '
      use warnings FATAL => "all"; use strict;
      use TAP::Parser;
      my $parser = TAP::Parser->new({tap => "1..1\n" . "ok 0\n"});
      my $result = $parser->next;
      $result->is_plan or die "first line is not TAP plan";
      $result = $parser->next;
      $result->is_test or die "second line is not TAP test result";
      my $testno = $result->number;
      $parser->next and die "unexpected further TAP stream";
      exit ($testno == 0 ? 0 : 77);
    '; then
      : # Nothing to do.
    elif test $? -eq 77; then
      skip_ 'TAP::Parser bug: test number 0 gets relabelled as 1'
    else
      fatal_ "error analyzing TAP::Parser module for bugs"
    fi
  fi
  
  . tap-setup.sh
  
  cat > a.test <<END
  1..1
  ok 0
  END
  
  cat > b.test <<END
  1..1
  not ok 0
  END
  
  cat > c.test <<END
  1..1
  ok 0 foo # SKIP
  END
  
  cat > d.test <<END
  1..1
  not ok 0 bar # TODO
  END
  
  cat > e.test <<END
  1..1
  ok 0 # TODO
  END
  
  run_make TESTS='a.test b.test c.test d.test e.test' check >stdout \
    && { cat stdout; exit 1; }
  cat stdout
  
  count_test_results total=5 pass=0 fail=0 xpass=0 xfail=0 skip=0 error=5
  
  grep '^ERROR: a\.test 0 # OUT-OF-ORDER (expecting 1)$' stdout
  grep '^ERROR: b\.test 0 # OUT-OF-ORDER (expecting 1)$' stdout
  grep '^ERROR: c\.test 0 foo # OUT-OF-ORDER (expecting 1)$' stdout
  grep '^ERROR: d\.test 0 bar # OUT-OF-ORDER (expecting 1)$' stdout
  grep '^ERROR: e\.test 0 # OUT-OF-ORDER (expecting 1)$' stdout
  
  :
  

Download