Mercurial > hg > mercurial-crew-with-dirclash
view tests/README @ 635:85e2209d401c
Protocol switch from using generators to stream-like objects.
This allows the the pull side to precisely control how much data is
read so that another encapsulation layer is not needed.
An http client gets a response with a finite size. Because ssh clients
need to keep the stream open, we must not read more data than is sent
in a response. But due to the streaming nature of the changegroup
scheme, only the piece that's parsing the data knows how far it's
allowed to read.
This means the generator scheme isn't fine-grained enough. Instead we
need file-like objects with a read(x) method. This switches everything
for push/pull over to using file-like objects rather than generators.
author | Matt Mackall <mpm@selenic.com> |
---|---|
date | Wed, 06 Jul 2005 22:20:12 -0800 |
parents | b4e0e20646bb |
children | 0fb498458905 |
line wrap: on
line source
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