delta/bash-completion.git/test/config, branch sudo

(testuite) Fix tests to run with autotools' make distcheck

2010-11-12T22:35:36+00:00

File locations are prefixed with `$::srcdir' so that `make distcheck' can
execute the test suite using a relative path.

The current working directory is removed from the test-suite-bash-prompt.

Furthermore, no more dynamic creation of files in dir $::srcdir/fixtures since
this dir is read-only during `make distcheck'.  Instead create dynamic files in
$TESTDIR/tmp

The test suite uses these "directory" variables

   tcl            bash          description
   ------------   -----------   ------------------------------------
   $::srcdir      $SRCDIR       where `fixtures' reside, relative
   $::srcdirabs   $SRCDIRABS    where `fixtures' reside, absolute
   $::TESTDIR     $TESTDIR      where `runtest' is invoked, absolute

(testsuite) Moved tool_start() code to tool_init()

2010-11-05T20:11:57+00:00

${tool}_start was called from within `config/default_exp', but this
proves to be error-prone, because DejaGnu isn't fully initialized at
that point, causing an error when calling one of the DejaGnu methods
pass/fail/unsupported/xfail/unresolved/untested:

    can't read "multipass_name": no such variable

The right way seems to be calling ${tool}_start() from
${tool}_init().

(testsuite) Fix eof/timeout message when unknown level

2010-10-23T18:49:02+00:00

(testsuite) Drop ending block comments

2010-06-18T15:21:38+00:00

Instead of writing `}; # if', write just `}' as was discussed here:

    http://www.mail-archive.com/bash-completion-devel@lists.alioth.debian.org/msg01815.html

(testsuite) Expand PATH with 'sbin' directories

2010-04-22T20:22:50+00:00

This allows for testing completions of system administrator commands,
which are installed via the same PATH expansion in
`bash_completion.have()'

(testsuite) Set TERM=dummy only for non-cron

2009-11-18T22:45:16+00:00

Err, TERM=linux also causes errors when tests are run via cron.
Reset TERM=dummy.
Workaround is to do a CRON=running from within the cron job and only set
TERM=dummy when not run via cron.

(testsuite) Set TERM=linux

2009-11-15T20:51:46+00:00

The TERM=dummy setting causes backspaces (^H) to appear in stdout when running
from cron.  Changing to TERM=linux should fix the ^H's in stdout AND the bug of
`meta_on' or `meta_off' escape sequences in stdout, caused by a bug in
supposedly libreadline5:

http://old.nabble.com/-PATCH-:-fix-libreadline5-linked-applications-sending-meta_on-or-meta_off-to-stdout-td25557585.html

Steps to reproduce output of ^H with TERM=dummy:

    $ batch
    warning: commands will be executed using /bin/sh
    at> ./runUnit _known_hosts_real.exp --debug < /dev/tty40
    at> ^D

NOTE: You need to connect a terminal (< /dev/tty..) to the test suite
      when running from cron.  See also doc/testing.txt, "Running tests via
      cron".

Testsuite: avoid readline escape junk at beginning of line.

2009-11-10T18:45:59+00:00

See e.g. http://bugs.gentoo.org/246091

new indentation policy

2009-10-04T17:42:50+00:00

Tell *Emacs to indent comments (sh-indent-comment: t).

2009-10-01T17:54:51+00:00

Also move indentation settings to end of files and expand *Emacs ones to
local variables block to avoid overflowing 80 char lines.