108
105
For further information, see http://bazaar-vcs.org/BzrDevelopment.
113
Preparing a Sandbox for Making Changes to Bazaar
114
================================================
116
Bazaar supports many ways of organising your work. See
117
http://bazaar-vcs.org/SharedRepositoryLayouts for a summary of the
118
popular alternatives.
120
Of course, the best choice for you will depend on numerous factors:
121
the number of changes you may be making, the complexity of the changes, etc.
122
As a starting suggestion though:
124
* create a local copy of the main development branch (bzr.dev) by using
127
bzr branch http://bazaar-vcs.org/bzr/bzr.dev/ bzr.dev
129
* keep your copy of bzr.dev prestine (by not developing in it) and keep
130
it up to date (by using bzr pull)
132
* create a new branch off your local bzr.dev copy for each issue
133
(bug or feature) you are working on.
135
This approach makes it easy to go back and make any required changes
136
after a code review. Resubmitting the change is then simple with no
137
risk of accidentially including edits related to other issues you may
138
be working on. After the changes for an issue are accepted and merged,
139
the associated branch can be deleted or archived as you wish.
142
Navigating the Code Base
143
========================
145
.. Was at <http://bazaar-vcs.org/NewDeveloperIntroduction>
147
Some of the key files in this directory are:
150
The command you run to start Bazaar itself. This script is pretty
151
short and just does some checks then jumps into bzrlib.
154
This file covers a brief introduction to Bazaar and lists some of its
158
Summary of changes in each Bazaar release that can affect users or
162
Installs Bazaar system-wide or to your home directory. To perform
163
development work on Bazaar it is not required to run this file - you
164
can simply run the bzr command from the top level directory of your
165
development copy. Note: That if you run setup.py this will create a
166
'build' directory in your development branch. There's nothing wrong
167
with this but don't be confused by it. The build process puts a copy
168
of the main code base into this build directory, along with some other
169
files. You don't need to go in here for anything discussed in this
173
Possibly the most exciting folder of all, bzrlib holds the main code
174
base. This is where you will go to edit python files and contribute to
178
Holds documentation on a whole range of things on Bazaar from the
179
origination of ideas within the project to information on Bazaar
180
features and use cases. Within this directory there is a subdirectory
181
for each translation into a human language. All the documentation
182
is in the ReStructuredText markup language.
185
Documentation specifically targetted at Bazaar and plugin developers.
186
(Including this document.)
190
Automatically-generated API reference information is available at
191
<http://starship.python.net/crew/mwh/bzrlibapi/>.
192
(There is an experimental editable version at
193
<http://starship.python.net/crew/mwh/bzrlibapi-oe/>.)
195
See also the `Bazaar Architectural Overview <../../developers/overview.html>`_.
198
The Code Review Process
199
#######################
201
All code changes coming in to Bazaar are reviewed by someone else.
202
Normally changes by core contributors are reviewed by one other core
203
developer, and changes from other people are reviewed by two core
204
developers. Use intelligent discretion if the patch is trivial.
206
Good reviews do take time. They also regularly require a solid
207
understanding of the overall code base. In practice, this means a small
208
number of people often have a large review burden - with knowledge comes
209
responsibility. No one like their merge requests sitting in a queue going
210
nowhere, so reviewing sooner rather than later is strongly encouraged.
214
Sending patches for review
215
==========================
108
A Closer Look at the Merge & Review Process
109
===========================================
217
111
If you'd like to propose a change, please post to the
218
112
bazaar@lists.canonical.com list with a bundle, patch, or link to a
219
branch. Put ``[PATCH]`` or ``[MERGE]`` in the subject so Bundle Buggy
113
branch. Put '[PATCH]' or '[MERGE]' in the subject so Bundle Buggy
220
114
can pick it out, and explain the change in the email message text.
221
115
Remember to update the NEWS file as part of your change if it makes any
222
116
changes visible to users or plugin developers. Please include a diff
223
117
against mainline if you're giving a link to a branch.
225
You can generate a merge request like this::
119
You can generate a bundle like this::
227
bzr send -o bug-1234.patch
121
bzr bundle > mybundle.patch
229
A ``.patch`` extension is recommended instead of .bundle as many mail clients
230
will send the latter as a binary file.
232
``bzr send`` can also send mail directly if you prefer; see the help.
123
A .patch extension is recommended instead of .bundle as many mail clients
124
will send the latter as a binary file. If a bundle would be too long or your
125
mailer mangles whitespace (e.g. implicitly converts Unix newlines to DOS
126
newlines), use the merge-directive command instead like this::
128
bzr merge-directive http://bazaar-vcs.org http://example.org/my_branch > my_directive.patch
130
See the help for details on the arguments to merge-directive.
234
132
Please do **NOT** put [PATCH] or [MERGE] in the subject line if you don't
235
133
want it to be merged. If you want comments from developers rather than
236
to be merged, you can put ``[RFC]`` in the subject line.
238
If this change addresses a bug, please put the bug number in the subject
239
line too, in the form ``[#1]`` so that Bundle Buggy can recognize it.
241
If the change is intended for a particular release mark that in the
242
subject too, e.g. ``[1.6]``.
248
Please put a "cover letter" on your merge request explaining:
250
* the reason **why** you're making this change
252
* **how** this change acheives this purpose
254
* anything else you may have fixed in passing
256
* anything significant that you thought of doing, such as a more
257
extensive fix or a different approach, but didn't or couldn't do now
259
A good cover letter makes reviewers' lives easier because they can decide
260
from the letter whether they agree with the purpose and approach, and then
261
assess whether the patch actually does what the cover letter says.
262
Explaining any "drive-by fixes" or roads not taken may also avoid queries
263
from the reviewer. All in all this should give faster and better reviews.
264
Sometimes writing the cover letter helps the submitter realize something
265
else they need to do. The size of the cover letter should be proportional
266
to the size and complexity of the patch.
269
Reviewing proposed changes
270
==========================
272
Anyone is welcome to review code, and reply to the thread with their
275
The simplest way to review a proposed change is to just read the patch on
276
the list or in Bundle Buggy. For more complex changes it may be useful
277
to make a new working tree or branch from trunk, and merge the proposed
278
change into it, so you can experiment with the code or look at a wider
281
There are three main requirements for code to get in:
283
* Doesn't reduce test coverage: if it adds new methods or commands,
284
there should be tests for them. There is a good test framework
285
and plenty of examples to crib from, but if you are having trouble
286
working out how to test something feel free to post a draft patch
289
* Doesn't reduce design clarity, such as by entangling objects
290
we're trying to separate. This is mostly something the more
291
experienced reviewers need to help check.
293
* Improves bugs, features, speed, or code simplicity.
295
Code that goes in should not degrade any of these aspects. Patches are
296
welcome that only cleanup the code without changing the external
297
behaviour. The core developers take care to keep the code quality high
298
and understandable while recognising that perfect is sometimes the enemy
301
It is easy for reviews to make people notice other things which should be
302
fixed but those things should not hold up the original fix being accepted.
303
New things can easily be recorded in the Bug Tracker instead.
305
It's normally much easier to review several smaller patches than one large
306
one. You might want to use ``bzr-loom`` to maintain threads of related
307
work, or submit a preparatory patch that will make your "real" change
311
Checklist for reviewers
312
=======================
314
* Do you understand what the code's doing and why?
316
* Will it perform reasonably for large inputs, both in memory size and
317
run time? Are there some scenarios where performance should be
320
* Is it tested, and are the tests at the right level? Are there both
321
blackbox (command-line level) and API-oriented tests?
323
* If this change will be visible to end users or API users, is it
324
appropriately documented in NEWS?
326
* Does it meet the coding standards below?
328
* If it changes the user-visible behaviour, does it update the help
329
strings and user documentation?
331
* If it adds a new major concept or standard practice, does it update the
332
developer documentation?
334
* (your ideas here...)
337
Bundle Buggy and review outcomes
338
================================
340
Anyone can "vote" on the mailing list by expressing an opinion. Core
341
developers can also vote using Bundle Buggy. Here are the voting codes and
134
to be merged, you can put '[RFC]' in the subject line.
136
Anyone is welcome to review code. There are broadly three gates for
139
* Doesn't reduce test coverage: if it adds new methods or commands,
140
there should be tests for them. There is a good test framework
141
and plenty of examples to crib from, but if you are having trouble
142
working out how to test something feel free to post a draft patch
145
* Doesn't reduce design clarity, such as by entangling objects
146
we're trying to separate. This is mostly something the more
147
experienced reviewers need to help check.
149
* Improves bugs, features, speed, or code simplicity.
151
Code that goes in should pass all three. The core developers take care
152
to keep the code quality high and understandable while recognising that
153
perfect is sometimes the enemy of good. (It is easy for reviews to make
154
people notice other things which should be fixed but those things should
155
not hold up the original fix being accepted. New things can easily be
156
recorded in the Bug Tracker instead.)
158
Anyone can "vote" on the mailing list. Core developers can also vote using
159
Bundle Buggy. Here are the voting codes and their explanations.
344
161
:approve: Reviewer wants this submission merged.
345
162
:tweak: Reviewer wants this submission merged with small changes. (No
362
179
outstanding merge requests together with an explanation of the columns.
363
180
Bundle Buggy will also mail you a link to track just your change.
183
Preparing a Sandbox for Making Changes to Bazaar
184
================================================
186
Bazaar supports many ways of organising your work. See
187
http://bazaar-vcs.org/SharedRepositoryLayouts for a summary of the
188
popular alternatives.
190
Of course, the best choice for you will depend on numerous factors:
191
the number of changes you may be making, the complexity of the changes, etc.
192
As a starting suggestion though:
194
* create a local copy of the main development branch (bzr.dev) by using
197
bzr branch http://bazaar-vcs.org/bzr/bzr.dev/ bzr.dev
199
* keep your copy of bzr.dev prestine (by not developing in it) and keep
200
it up to date (by using bzr pull)
202
* create a new branch off your local bzr.dev copy for each issue
203
(bug or feature) you are working on.
205
This approach makes it easy to go back and make any required changes
206
after a code review. Resubmitting the change is then simple with no
207
risk of accidentially including edits related to other issues you may
208
be working on. After the changes for an issue are accepted and merged,
209
the associated branch can be deleted or archived as you wish.
212
Navigating the Code Base
213
========================
215
TODO: List and describe in one line the purpose of each directory
216
inside an installation of bzr.
218
TODO: Refer to a central location holding an up to date copy of the API
219
documentation generated by epydoc, e.g. something like
220
http://starship.python.net/crew/mwh/bzrlibapi/bzrlib.html.
226
The Importance of Testing
227
=========================
229
Reliability is a critical success factor for any Version Control System.
230
We want Bazaar to be highly reliable across multiple platforms while
231
evolving over time to meet the needs of its community.
233
In a nutshell, this is want we expect and encourage:
235
* New functionality should have test cases. Preferably write the
236
test before writing the code.
238
In general, you can test at either the command-line level or the
239
internal API level. See Writing tests below for more detail.
241
* Try to practice Test-Driven Development: before fixing a bug, write a
242
test case so that it does not regress. Similarly for adding a new
243
feature: write a test case for a small version of the new feature before
244
starting on the code itself. Check the test fails on the old code, then
245
add the feature or fix and check it passes.
247
By doing these things, the Bazaar team gets increased confidence that
248
changes do what they claim to do, whether provided by the core team or
249
by community members. Equally importantly, we can be surer that changes
250
down the track do not break new features or bug fixes that you are
253
As of May 2008, Bazaar ships with a test suite containing over 12000 tests
254
and growing. We are proud of it and want to remain so. As community
255
members, we all benefit from it. Would you trust version control on
256
your project to a product *without* a test suite like Bazaar has?
259
Running the Test Suite
260
======================
262
Currently, bzr selftest is used to invoke tests.
263
You can provide a pattern argument to run a subset. For example,
264
to run just the blackbox tests, run::
266
./bzr selftest -v blackbox
268
To skip a particular test (or set of tests), use the --exclude option
269
(shorthand -x) like so::
271
./bzr selftest -v -x blackbox
273
To ensure that all tests are being run and succeeding, you can use the
274
--strict option which will fail if there are any missing features or known
277
./bzr selftest --strict
279
To list tests without running them, use the --list-only option like so::
281
./bzr selftest --list-only
283
This option can be combined with other selftest options (like -x) and
284
filter patterns to understand their effect.
286
Once you understand how to create a list of tests, you can use the --load-list
287
option to run only a restricted set of tests that you kept in a file, one test
288
id by line. Keep in mind that this will never be sufficient to validate your
289
modifications, you still need to run the full test suite for that, but using it
290
can help in some cases (like running only the failed tests for some time)::
292
./bzr selftest -- load-list my_failing_tests
294
This option can also be combined with other selftest options, including
295
patterns. It has some drawbacks though, the list can become out of date pretty
296
quick when doing Test Driven Development.
298
To address this concern, there is another way to run a restricted set of tests:
299
the --starting-with option will run only the tests whose name starts with the
300
specified string. It will also avoid loading the other tests and as a
301
consequence starts running your tests quicker::
303
./bzr selftest --starting-with bzrlib.blackbox
305
This option can be combined with all the other selftest options including
306
--load-list. The later is rarely used but allows to run a subset of a list of
307
failing tests for example.
309
Test suite debug flags
310
----------------------
312
Similar to the global ``-Dfoo`` debug options, bzr selftest accepts
313
``-E=foo`` debug flags. These flags are:
315
:allow_debug: do *not* clear the global debug flags when running a test.
316
This can provide useful logging to help debug test failures when used
317
with e.g. ``bzr -Dhpss selftest -E=allow_debug``
323
In general tests should be placed in a file named test_FOO.py where
324
FOO is the logical thing under test. That file should be placed in the
325
tests subdirectory under the package being tested.
327
For example, tests for merge3 in bzrlib belong in bzrlib/tests/test_merge3.py.
328
See bzrlib/tests/test_sampler.py for a template test script.
330
Tests can be written for the UI or for individual areas of the library.
331
Choose whichever is appropriate: if adding a new command, or a new command
332
option, then you should be writing a UI test. If you are both adding UI
333
functionality and library functionality, you will want to write tests for
334
both the UI and the core behaviours. We call UI tests 'blackbox' tests
335
and they are found in ``bzrlib/tests/blackbox/*.py``.
337
When writing blackbox tests please honour the following conventions:
339
1. Place the tests for the command 'name' in
340
bzrlib/tests/blackbox/test_name.py. This makes it easy for developers
341
to locate the test script for a faulty command.
343
2. Use the 'self.run_bzr("name")' utility function to invoke the command
344
rather than running bzr in a subprocess or invoking the
345
cmd_object.run() method directly. This is a lot faster than
346
subprocesses and generates the same logging output as running it in a
347
subprocess (which invoking the method directly does not).
349
3. Only test the one command in a single test script. Use the bzrlib
350
library when setting up tests and when evaluating the side-effects of
351
the command. We do this so that the library api has continual pressure
352
on it to be as functional as the command line in a simple manner, and
353
to isolate knock-on effects throughout the blackbox test suite when a
354
command changes its name or signature. Ideally only the tests for a
355
given command are affected when a given command is changed.
357
4. If you have a test which does actually require running bzr in a
358
subprocess you can use ``run_bzr_subprocess``. By default the spawned
359
process will not load plugins unless ``--allow-plugins`` is supplied.
365
We make selective use of doctests__. In general they should provide
366
*examples* within the API documentation which can incidentally be tested. We
367
don't try to test every important case using doctests -- regular Python
368
tests are generally a better solution.
370
Most of these are in ``bzrlib/doc/api``. More additions are welcome.
372
__ http://docs.python.org/lib/module-doctest.html
375
Skipping tests and test requirements
376
------------------------------------
378
In our enhancements to unittest we allow for some addition results beyond
379
just success or failure.
381
If a test can't be run, it can say that it's skipped. This is typically
382
used in parameterized tests - for example if a transport doesn't support
383
setting permissions, we'll skip the tests that relating to that. ::
386
return self.branch_format.initialize(repo.bzrdir)
387
except errors.UninitializableFormat:
388
raise tests.TestSkipped('Uninitializable branch format')
390
Raising TestSkipped is a good idea when you want to make it clear that the
391
test was not run, rather than just returning which makes it look as if it
394
Several different cases are distinguished:
397
Generic skip; the only type that was present up to bzr 0.18.
400
The test doesn't apply to the parameters with which it was run.
401
This is typically used when the test is being applied to all
402
implementations of an interface, but some aspects of the interface
403
are optional and not present in particular concrete
404
implementations. (Some tests that should raise this currently
405
either silently return or raise TestSkipped.) Another option is
406
to use more precise parameterization to avoid generating the test
410
**(Not implemented yet)**
411
The test can't be run because of an inherent limitation of the
412
environment, such as not having symlinks or not supporting
416
The test can't be run because a dependency (typically a Python
417
library) is not available in the test environment. These
418
are in general things that the person running the test could fix
419
by installing the library. It's OK if some of these occur when
420
an end user runs the tests or if we're specifically testing in a
421
limited environment, but a full test should never see them.
424
The test exists but is known to fail, for example because the
425
code to fix it hasn't been run yet. Raising this allows
426
you to distinguish these failures from the ones that are not
427
expected to fail. This could be conditionally raised if something
428
is broken on some platforms but not on others.
430
We plan to support three modes for running the test suite to control the
431
interpretation of these results. Strict mode is for use in situations
432
like merges to the mainline and releases where we want to make sure that
433
everything that can be tested has been tested. Lax mode is for use by
434
developers who want to temporarily tolerate some known failures. The
435
default behaviour is obtained by ``bzr selftest`` with no options, and
436
also (if possible) by running under another unittest harness.
438
======================= ======= ======= ========
439
result strict default lax
440
======================= ======= ======= ========
441
TestSkipped pass pass pass
442
TestNotApplicable pass pass pass
443
TestPlatformLimit pass pass pass
444
TestDependencyMissing fail pass pass
445
KnownFailure fail pass pass
446
======================= ======= ======= ========
449
Test feature dependencies
450
-------------------------
452
Rather than manually checking the environment in each test, a test class
453
can declare its dependence on some test features. The feature objects are
454
checked only once for each run of the whole test suite.
456
For historical reasons, as of May 2007 many cases that should depend on
457
features currently raise TestSkipped.)
461
class TestStrace(TestCaseWithTransport):
463
_test_needs_features = [StraceFeature]
465
This means all tests in this class need the feature. The feature itself
466
should provide a ``_probe`` method which is called once to determine if
469
These should generally be equivalent to either TestDependencyMissing or
470
sometimes TestPlatformLimit.
476
Known failures are when a test exists but we know it currently doesn't
477
work, allowing the test suite to still pass. These should be used with
478
care, we don't want a proliferation of quietly broken tests. It might be
479
appropriate to use them if you've committed a test for a bug but not the
480
fix for it, or if something works on Unix but not on Windows.
483
Testing exceptions and errors
484
-----------------------------
486
It's important to test handling of errors and exceptions. Because this
487
code is often not hit in ad-hoc testing it can often have hidden bugs --
488
it's particularly common to get NameError because the exception code
489
references a variable that has since been renamed.
491
.. TODO: Something about how to provoke errors in the right way?
493
In general we want to test errors at two levels:
495
1. A test in ``test_errors.py`` checking that when the exception object is
496
constructed with known parameters it produces an expected string form.
497
This guards against mistakes in writing the format string, or in the
498
``str`` representations of its parameters. There should be one for
499
each exception class.
501
2. Tests that when an api is called in a particular situation, it raises
502
an error of the expected class. You should typically use
503
``assertRaises``, which in the Bazaar test suite returns the exception
504
object to allow you to examine its parameters.
506
In some cases blackbox tests will also want to check error reporting. But
507
it can be difficult to provoke every error through the commandline
508
interface, so those tests are only done as needed -- eg in response to a
509
particular bug or if the error is reported in an unusual way(?) Blackbox
510
tests should mostly be testing how the command-line interface works, so
511
should only test errors if there is something particular to the cli in how
512
they're displayed or handled.
518
The Python ``warnings`` module is used to indicate a non-fatal code
519
problem. Code that's expected to raise a warning can be tested through
522
The test suite can be run with ``-Werror`` to check no unexpected errors
525
However, warnings should be used with discretion. It's not an appropriate
526
way to give messages to the user, because the warning is normally shown
527
only once per source line that causes the problem. You should also think
528
about whether the warning is serious enought that it should be visible to
529
users who may not be able to fix it.
532
Interface implementation testing and test scenarios
533
---------------------------------------------------
535
There are several cases in Bazaar of multiple implementations of a common
536
conceptual interface. ("Conceptual" because
537
it's not necessary for all the implementations to share a base class,
538
though they often do.) Examples include transports and the working tree,
539
branch and repository classes.
541
In these cases we want to make sure that every implementation correctly
542
fulfils the interface requirements. For example, every Transport should
543
support the ``has()`` and ``get()`` and ``clone()`` methods. We have a
544
sub-suite of tests in ``test_transport_implementations``. (Most
545
per-implementation tests are in submodules of ``bzrlib.tests``, but not
546
the transport tests at the moment.)
548
These tests are repeated for each registered Transport, by generating a
549
new TestCase instance for the cross product of test methods and transport
550
implementations. As each test runs, it has ``transport_class`` and
551
``transport_server`` set to the class it should test. Most tests don't
552
access these directly, but rather use ``self.get_transport`` which returns
553
a transport of the appropriate type.
555
The goal is to run per-implementation only tests that relate to that
556
particular interface. Sometimes we discover a bug elsewhere that happens
557
with only one particular transport. Once it's isolated, we can consider
558
whether a test should be added for that particular implementation,
559
or for all implementations of the interface.
561
The multiplication of tests for different implementations is normally
562
accomplished by overriding the ``test_suite`` function used to load
563
tests from a module. This function typically loads all the tests,
564
then applies a TestProviderAdapter to them, which generates a longer
565
suite containing all the test variations.
571
Some utilities are provided for generating variations of tests. This can
572
be used for per-implementation tests, or other cases where the same test
573
code needs to run several times on different scenarios.
575
The general approach is to define a class that provides test methods,
576
which depend on attributes of the test object being pre-set with the
577
values to which the test should be applied. The test suite should then
578
also provide a list of scenarios in which to run the tests.
580
Typically ``multiply_tests_from_modules`` should be called from the test
581
module's ``test_suite`` function.
584
Essential Domain Classes
585
########################
587
Introducing the Object Model
588
============================
590
The core domain objects within the bazaar model are:
600
Transports are explained below. See http://bazaar-vcs.org/Classes/
601
for an introduction to the other key classes.
606
The ``Transport`` layer handles access to local or remote directories.
607
Each Transport object acts like a logical connection to a particular
608
directory, and it allows various operations on files within it. You can
609
*clone* a transport to get a new Transport connected to a subdirectory or
612
Transports are not used for access to the working tree. At present
613
working trees are always local and they are accessed through the regular
614
Python file io mechanisms.
619
Transports work in URLs. Take note that URLs are by definition only
620
ASCII - the decision of how to encode a Unicode string into a URL must be
621
taken at a higher level, typically in the Store. (Note that Stores also
622
escape filenames which cannot be safely stored on all filesystems, but
623
this is a different level.)
625
The main reason for this is that it's not possible to safely roundtrip a
626
URL into Unicode and then back into the same URL. The URL standard
627
gives a way to represent non-ASCII bytes in ASCII (as %-escapes), but
628
doesn't say how those bytes represent non-ASCII characters. (They're not
629
guaranteed to be UTF-8 -- that is common but doesn't happen everywhere.)
631
For example if the user enters the url ``http://example/%e0`` there's no
632
way to tell whether that character represents "latin small letter a with
633
grave" in iso-8859-1, or "latin small letter r with acute" in iso-8859-2
634
or malformed UTF-8. So we can't convert their URL to Unicode reliably.
636
Equally problematic if we're given a url-like string containing non-ascii
637
characters (such as the accented a) we can't be sure how to convert that
638
to the correct URL, because we don't know what encoding the server expects
639
for those characters. (Although this is not totally reliable we might still
640
accept these and assume they should be put into UTF-8.)
642
A similar edge case is that the url ``http://foo/sweet%2Fsour`` contains
643
one directory component whose name is "sweet/sour". The escaped slash is
644
not a directory separator. If we try to convert URLs to regular Unicode
645
paths this information will be lost.
647
This implies that Transports must natively deal with URLs; for simplicity
648
they *only* deal with URLs and conversion of other strings to URLs is done
649
elsewhere. Information they return, such as from ``list_dir``, is also in
650
the form of URL components.
365
653
Coding Style Guidelines
366
654
#######################
1094
In general tests should be placed in a file named test_FOO.py where
1095
FOO is the logical thing under test. That file should be placed in the
1096
tests subdirectory under the package being tested.
1098
For example, tests for merge3 in bzrlib belong in bzrlib/tests/test_merge3.py.
1099
See bzrlib/tests/test_sampler.py for a template test script.
1101
Tests can be written for the UI or for individual areas of the library.
1102
Choose whichever is appropriate: if adding a new command, or a new command
1103
option, then you should be writing a UI test. If you are both adding UI
1104
functionality and library functionality, you will want to write tests for
1105
both the UI and the core behaviours. We call UI tests 'blackbox' tests
1106
and they are found in ``bzrlib/tests/blackbox/*.py``.
1108
When writing blackbox tests please honour the following conventions:
1110
1. Place the tests for the command 'name' in
1111
bzrlib/tests/blackbox/test_name.py. This makes it easy for developers
1112
to locate the test script for a faulty command.
1114
2. Use the 'self.run_bzr("name")' utility function to invoke the command
1115
rather than running bzr in a subprocess or invoking the
1116
cmd_object.run() method directly. This is a lot faster than
1117
subprocesses and generates the same logging output as running it in a
1118
subprocess (which invoking the method directly does not).
1120
3. Only test the one command in a single test script. Use the bzrlib
1121
library when setting up tests and when evaluating the side-effects of
1122
the command. We do this so that the library api has continual pressure
1123
on it to be as functional as the command line in a simple manner, and
1124
to isolate knock-on effects throughout the blackbox test suite when a
1125
command changes its name or signature. Ideally only the tests for a
1126
given command are affected when a given command is changed.
1128
4. If you have a test which does actually require running bzr in a
1129
subprocess you can use ``run_bzr_subprocess``. By default the spawned
1130
process will not load plugins unless ``--allow-plugins`` is supplied.
1136
We have a rich collection of tools to support writing tests. Please use
1137
them in preference to ad-hoc solutions as they provide portability and
1138
performance benefits.
1143
The ``TreeBuilder`` interface allows the construction of arbitrary trees
1144
with a declarative interface. A sample session might look like::
1146
tree = self.make_branch_and_tree('path')
1147
builder = TreeBuilder()
1148
builder.start_tree(tree)
1149
builder.build(['foo', "bar/", "bar/file"])
1150
tree.commit('commit the tree')
1151
builder.finish_tree()
1153
Please see bzrlib.treebuilder for more details.
1158
The ``BranchBuilder`` interface allows the creation of test branches in a
1159
quick and easy manner. A sample session::
1161
builder = BranchBuilder(self.get_transport().clone('relpath'))
1162
builder.build_commit()
1163
builder.build_commit()
1164
builder.build_commit()
1165
branch = builder.get_branch()
1167
Please see bzrlib.branchbuilder for more details.
1172
We make selective use of doctests__. In general they should provide
1173
*examples* within the API documentation which can incidentally be tested. We
1174
don't try to test every important case using doctests -- regular Python
1175
tests are generally a better solution.
1177
Most of these are in ``bzrlib/doc/api``. More additions are welcome.
1179
__ http://docs.python.org/lib/module-doctest.html
1184
Currently, bzr selftest is used to invoke tests.
1185
You can provide a pattern argument to run a subset. For example,
1186
to run just the blackbox tests, run::
1188
./bzr selftest -v blackbox
1190
To skip a particular test (or set of tests), use the --exclude option
1191
(shorthand -x) like so::
1193
./bzr selftest -v -x blackbox
1195
To list tests without running them, use the --list-only option like so::
1197
./bzr selftest --list-only
1199
This option can be combined with other selftest options (like -x) and
1200
filter patterns to understand their effect.
841
1203
Handling Errors and Exceptions
842
1204
==============================
added
removed
doc/developers/HACKING.txt
