Mercurial > hg
view tests/README @ 2700:de8dc25a3eeb
Backed out changeset 2ab464771b7d15c60014996d2853efc92cdb8465
- it always runs chmod
- uses chmod in an unsafe way
- if somebody does a clone of a repo, runs 'make tests', everything is fine,
so he can assume the original repo is fine, too, but it is not.
author | Thomas Arendsen Hein <thomas@intevation.de> |
---|---|
date | Thu, 27 Jul 2006 18:53:10 +0200 |
parents | e506c14382fd |
children | 1c66aad252f9 |
line wrap: on
line source
A simple testing framework To run the tests, do: cd tests/ python run-tests.py 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 merge want user interaction for commit use -m "text" for hg merge, 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 "1000000 0" - diff will show the current time use hg diff | sed "s/\(\(---\|+++\) [a-zA-Z0-9_/.-]*\).*/\1/" to strip dates