tests/README
author mpm@selenic.com
Sat, 25 Jun 2005 16:31:43 -0800
changeset 473 5914e27dc717
parent 350 b4e0e20646bb
child 761 0fb498458905
permissions -rw-r--r--
[PATCH] Get run-tests working on 64-bit machines. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [PATCH] Get run-tests working on 64-bit machines. From: Bryan O'Sullivan <bos@serpentine.com> manifest hash: 3704997be1744478414cddcd79c7bea5ccd6a1b1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCvfdvywK+sNU5EO8RAm5iAJ9mWxI4o2j7IM7Mko7IjfKfNtWJqwCcDekn 6GDlcDo/Q3nv8ybFzykwQjY= =tS2i -----END PGP SIGNATURE-----

A simple testing framework

To run the tests, do:

cd tests/
./run-tests

This finds all scripts in the test directory named test-* and executes
them. The scripts can be either shell scripts or Python. Each test is
run in a temporary directory that is removed when the test is complete.

A test-<x> succeeds if the script returns success and its output
matches test-<x>.out. If the new output doesn't match, it is stored in
test-<x>.err.

There are some tricky points here that you should be aware of when
writing tests:

- hg commit and hg up -m want user interaction

  for commit use -t "text"
  for hg up -m, set HGMERGE to something noninteractive (like true or merge)

- changeset hashes will change based on user and date which make
  things like hg history output change

  use commit -t "test" -u test -d "0 0"

- diff will show the current time

  use hg diff | sed "s/\(\(---\|+++\).*\)\t.*/\1/" to strip dates

- set -x and pipelines don't generate stable output

  turn off set -x or break pipelines into pieces