~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/HACKING.txt

Committer: John Arbash Meinel
Date: 2008-07-29 16:34:09 UTC
mfrom: (3567.4.19 branch_builder) (3567.5.2 use_branch_builder)
mto: (3697.7.4 1.7)
mto: This revision was merged to the branch mainline in revision 3748.
Revision ID: john@arbash-meinel.com-20080729163409-3x3n0ba1xt2gmlvf

Bring in both branch-builder threads.

files modified:
bzrlib/branchbuilder.py

bzrlib/errors.py

bzrlib/tests/test_branchbuilder.py

bzrlib/tests/test_errors.py

bzrlib/tests/test_selftest.py

doc/developers/HACKING.txt

Show diffs side-by-side

added added

removed removed

doc/developers/HACKING.txt

406

subprocess you can use ``run_bzr_subprocess``. By default the spawned

407

process will not load plugins unless ``--allow-plugins`` is supplied.

408

409

When writing library functionality, it is often necessary to set up a

410

branch with a certain history. Most current tests do this by inheriting

411

from ``TestCaseWithTransport`` and using the ``make_branch_and_tree``

412

helper to give them a ``WorkingTree`` that they can commit to. However,

413

there is a newer api available from ``TestCaseWithMemoryTransport`` using

414

the ``make_branch_builder`` helper. This helper is preferred, because it

415

can build the changes in memory, rather than on disk. Tests that are

416

explictly testing how we work with disk objects should, of course, use a

417

real ``WorkingTree``. See ``bzrlib/branch_builder.py`` for how to use the

418

class.

419

409

420

410

421

Doctests

411

422

--------

Older »