view tests/README @ 1907:7718885070b1

let commands that show changesets use templates.
mechanism is same as hgweb templates.

old show_changeset code is still used for now if no template given,
because it is faster than template code when verbose or debug.

simple template can be given on command line using -t, --template.

example:

  hg log -t '{author|person}\n'

complex template can be put in template map file, given on command line
using --map-file.

we give two example map files:
map-log.compact prints 3 lines of output for every change.
map-log.verbose prints exact same output as default "hg log -v".

map files are searched where user says, then in template path as backup.

example:

  hg log --map-file map-log.compact

defaults can be set in hgrc with ui.logtemplate and ui.logmap.

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 -m "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 -m "test" -u test -d "0 0"

- diff will show the current time

  use hg diff | sed "s/\(\(---\|+++\) [a-zA-Z0-9_/.-]*\).*/\1/" to strip
  dates