- Oct 13, 2021
-
-
Georges Racinet authored
At least on Python3.7, coverage 6.0 (and/or pytest-cov 3.0.0) break the build with `ModuleNotFoundError: No module named 'hgext3rd.heptapod'`
-
- Dec 02, 2020
-
-
Raphaël Gomès authored
-
- Nov 22, 2020
-
-
Georges Racinet authored
These testhelpers have been externalized as the `mercurial_testhelpers` package. The latter being meant to be identical to a future `mercurial.testhelpers` in Mercurial core, they don't have facilities for topics nor evolve specific commands. But the commit options extensibility can be used to specify topics in `commit_file`. As for the `prune` helper method, it can be implemented by direct subclassing. This is what `hg-evolve` could later do, if that project were to adopt those test helpers. Downstream extensions of evolve and topic could then just use a base class provided by evolve. Also, the `RepoWrapper` from `mercurial_testhelpers` has two different method names, that we remap directly to make the whole test suite pass.
-
- Jul 31, 2020
-
-
Georges Racinet authored
Besides, it can create conflicts with the version already listed in install requirements.
-
- Jan 10, 2020
-
-
Georges Racinet authored
Not merely installing install-requirements from the .gitlab-ci.yml because that would also install Mercurial, which is either a no-op or a costly ignored step.
-
- Dec 15, 2019
-
-
Georges Racinet authored
that means actually testing that it's properly passed to `hgweb_mod`, the one doing the job
-
Georges Racinet authored
This will be help bootsrapping developer environments. Apparently it's now deprecated to run tests with `setup.py test`, so we don't bother listing it in setup.py.
-