Mercurial > hg
view tests/.balto.toml @ 42926:34ed651ba7e4
cleanup: fix leakage of dirstate._map to client code
We already had proper accessors for most of the behavior of
dirstate._map that callers cared about exposed in the actual dirstate
class as public methods. Sigh.
There are two remaining privacy violations in the codebase after this change:
1) In the perf extension, which I suspect has to stick around because
it's really testing the dirstate implementation directly
2) In largefiles, where we deal with standins and mutating status. Looking at
this, I _strongly_ suspect a formal dirstate interface would allow
this to work via composition instead of inheritance and
monkeypatching. Fortunately, such wins are a part of my motivation
for this work. I anticipate we'll come back to this in due time.
Differential Revision: https://phab.mercurial-scm.org/D6837
author | Augie Fackler <augie@google.com> |
---|---|
date | Tue, 10 Sep 2019 09:41:58 -0400 |
parents | 337a38995336 |
children |
line wrap: on
line source
# Balto (https://bitbucket.org/lothiraldan/balto/src) is a test orchestrator # which is compatible with all test runner that can emit the LITF # (https://github.com/lothiraldan/litf) test format. # The plugin for the Mercurial test runner is mercurial-litf # (https://pypi.org/project/mercurial-litf/). Make sure to follow the # instruction and configuration instructions here: # https://bitbucket.org/lothiraldan/mercurial_litf/src/default/ # You can launch Balto with `balto /path/to/mercurial/tests/` name = "Mercurial Test Suite" tool = "mercurial"