How do I diagnose test errors?

Dirkjan Ochtman dirkjan at ochtman.nl
Thu Jun 5 02:50:19 CDT 2008


On Thu, Jun 5, 2008 at 9:26 AM, Paul Moore <p.f.moore at gmail.com> wrote:
> That's what I thought... I hadn't thought of adding echo lines like
> this. I'm a little scared of this type of "exact output match" test
> approach, it seems too easy to break so I avoid touching things (it's
> irrational I know...) I'll try that.

It may break easily, but it's also very easy to understand.

> By the way, is there a way to run a single test on its own (under
> Windows, I guess on Unix you can just run the script manually), so
> that I don't have to wait the 2-3 hours for the test suite to run?

On Linux, you can run python run-tests.py test-name... That should
work on Windows just as well, I guess? You can also pass two or more
test names.

> OK, I'll think about this. I also have ideas on how I can change some
> of the tests to use doctest or unittest (without altering the
> whole-operation testing approach, just to make it easier to run them
> on Windows without special support), I might look at the whole area of
> testing next, once the case folding changes are OK. But I won't mess
> with anything without discussing it.

We already have a few doctests, I think. Not sure what Matt would
think about using unittests.

Cheers,

Dirkjan


More information about the Mercurial-devel mailing list