sapling/tests/README
Pierre-Yves David 3cafa7d1f2 test: backout e221a52 (remove run-tests.py once again)
Shipping your own `run-tests.py` is a bad practice as the custom version will
slowly diverge from important fixes and upgrade from the upstream one. Using the
core one is simple and we should use it.

I'm not convinced by the arguments used in the re-installation (e221a52),

- It is easy to run the test against any version of Mercurial including the
  installed one using `--with-hg=`,

- If you have people contributing to this level of extensions, having them
  clone Mercurial is fairly cheap. If this is really seen a blocker, completing
  the Mercurial's upstream plan to have run-tests.py installable as a developer
  tools seems a cheap way to move forward instead,

- If you own a complex installation with multiple Mercurial related dependencies,
  you already have a way to handle version dependency in this context and your
  contributor can use this very same infrastructure to make sure they run at the
  right version. And they probably should use it already anyway to make sure
  they are testing the stack properly.

This changesets also install a README explaining how to obtains the test runner
and runs it against various Mercurial version.
2015-12-16 16:42:17 +00:00

30 lines
948 B
Plaintext

How to run Facebook experimental extensions tests
=================================================
Running the tests
-----------------
To run the tests, `cd` into this directory (./tests/) and run the `run-tests.py`
script from the core Mercurial repository (tests directory too).
For example if you have a 'hg-crew' repository checked out next to this one,
use:
../../hg-crew/tests/run-tests.py
Obtaining the test runners
--------------------------
If you do not already have a copy of the Mercurial repository, you can obtains
one with:
$ hg clone http://selenic.com/hg/
Running against various Mercurial versions
------------------------------------------
By default, the test runners will run against the version of Mercurial in the
repository it lives in. you can run againts other version of Mercurial using
the --with-hg=PATH flag. For example to run against the installed version of
Mercurial you can use --with-hg=`which hg`