[PATCH] testing: allow Hypothesis tests to disable extensions

[David MacIver]

I do, but I don't think it would simplify this patch.

The major reason for keeping track of config ourselves is that making the
relevant changes to the hgrc from within the generated .t file ended up
being really annoying, and this simplifies it significantly.

On 26 February 2016 at 18:51, Martin von Zweigbergk <martinvonz at google.com>
wrote:

> On Fri, Feb 26, 2016 at 9:16 AM, David R. MacIver <david at drmaciver.com>
> wrote:
> > # HG changeset patch
> > # User David R. MacIver <david at drmaciver.com>
> > # Date 1456506949 0
> > #      Fri Feb 26 17:15:49 2016 +0000
> > # Node ID 9a28035d39f02fc7e03d0d376ce66998628a6877
> > # Parent  18680fed30581e7286a72b93af97de980a178d96
> > testing: allow Hypothesis tests to disable extensions
> >
> > Doing this required the introduction of a mechanism for keeping
> > track of more general config in the test. At present this is only
> > used for extensions but it could be used more widely (e.g. to
> > control specific extension behaviour)
>
> Do you know that you can disable extensions with "--config
> extensions.foo=!"? I don't know if that would simplify this patch or
> if there are other reasons to keep track of config ourselves, but I
> wanted to check before I review it in detail.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20160227/1b92381b/attachment-0002.html>