Open Bug 1227531 Opened 9 years ago Updated 9 years ago

Rewite mozhginfo tests

Categories

(Developer Services :: Mercurial: Pushlog, defect)

Product:
Developer Services
Component:
Mercurial: Pushlog
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

People

(Reporter: armenzg, Assigned: sabergeass)

Details

In bug 1203621 we're going to land a pushlog_client which came with its own sets of integration tests. We should follow up with tests ala vcs-tools style to be consistent and have proper coverage.

From gps:
We try not to use mocks in version-control-tools because they get out of sync with reality. Instead, our tests start actual Mercurial servers configured like hg.mozilla.org and tests hit them. See e.g. https://hg.mozilla.org/hgcustom/version-control-tools/file/tip/hgext/pushlog-legacy/tests/test-hgweb.t. https://www.mercurial-scm.org/wiki/WritingTests describes the test format. You can even write inline Python doctest-style tests. So you can e.g. start a server in the shell then have some boilerplate python query the server.
Assignee: nobody → sabergeass
You need to log in before you can comment on or make changes to this bug.