[PATCH 2 of 4] run-tests: allow to put conditions and comments in expected output
mads at kiilerich.com
Tue Feb 4 09:42:10 CST 2014
On 02/04/2014 01:14 AM, Simon Heimberg wrote:
> # HG changeset patch
> # User Simon Heimberg <simohe at besonet.ch>
> # Date 1391470011 -3600
> # Tue Feb 04 00:26:51 2014 +0100
> # Branch stable
> # Node ID 94c2bb6ad0656684bdc90bb52a1a205a5ad151e3
> # Parent ab6f4d067f28326dfdd5c352491c92148f0ee160
> run-tests: allow to put conditions and comments in expected output
> It must be written like this:
> $ echo output; false
> #if true
> something else
What will happen when using -i ?
Currently the command and its output is obvious, and -i should just do
the right thing in the "code" path that is tested.
How will it work with this new conditional style?
If "not so well": Is the increased complexity and maintenance overhead
For the file://drive/path handling: Wouldn't it be simpler to add a
replacement hack to run-tests?
More information about the Mercurial-devel