view tests/test-identify @ 10300:c437745f50ec

run-tests: split tests/blacklist in tests/blacklists/*

Following discussions with Gilles Morris [1], it seems that it is preferable to
use several blacklist files in a blacklists/ directory. It is easier to add an
unversioned file for experiments than modifying a tracked file.

Also fall back to a simpler syntax, giving up ConfigParser, now that section
names are not needed anymore.

And allow --blacklist parameter to be a complete path, instead of only one
of the filenames contained in tests/blacklists/


[1] http://www.selenic.com/pipermail/mercurial-devel/2009-December/017317.html

#!/bin/sh

"$TESTDIR/hghave" no-outer-repo || exit 80

echo % no repo
hg id

echo % create repo
hg init test
cd test
echo a > a
hg ci -Ama

echo % basic id usage
hg id
hg id --debug
hg id -q
hg id -v

echo % with options
hg id -r.
hg id -n
hg id -t
hg id -b
hg id -i
hg id -n -t -b -i

echo % with modifications
echo b > a
hg id -n -t -b -i

echo % other local repo
cd ..
hg -R test id
hg id test

echo % with remote http repo
cd test
hg serve -p $HGPORT1 -d --pid-file=hg.pid
cat hg.pid >> $DAEMON_PIDS
hg id http://localhost:$HGPORT1/

echo % remote with tags?
hg id -t http://localhost:$HGPORT1/

true # ends with util.Abort -> returns 255