bzr's doctests are not isolated (branchbuilder doctests check global gpg configuration)
Bug #321320 reported by
Andrew Bennetts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
Vincent Ladeuil |
Bug Description
There's a doctest in bzrlib.
Related branches
lp:~vila/bzr/321320-isolate-doc-tests
- Andrew Bennetts: Needs Fixing
-
Diff: 395 lines (+244/-63)4 files modifiedbzrlib/tests/__init__.py (+110/-58)
bzrlib/tests/test_selftest.py (+122/-3)
doc/developers/testing.txt (+5/-2)
doc/en/release-notes/bzr-2.3.txt (+7/-0)
Changed in bzr: | |
assignee: | nobody → Vincent Ladeuil (vila) |
status: | Confirmed → In Progress |
Changed in bzr: | |
milestone: | none → 2.3b5 |
status: | In Progress → Fix Released |
To post a comment you must log in.
A good fix would probably be to change the way we construct DocTestSuite. We could pass setUp and tearDown params to its constructor to do the same sort of setUp and tearDown as we do in normal TestCases. In particular do the isolation of the test environment from the user's normal day-to-day environment.
(It might be neat to also provide an addCleanup facility in the globs param, too, but that's a separate issue.)