146
146
Bazaar can optionally produce output in the machine-readable subunit_
147
format, so that test output can be post-processed by various tools.
147
format, so that test output can be post-processed by various tools. To
148
generate a subunit test stream::
150
$ ./bzr selftest --subunit
152
Processing such a stream can be done using a variety of tools including:
154
* The builtin ``subunit2pyunit``, ``subunit-filter``, ``subunit-ls``,
155
``subunit2junitxml`` from the subunit project.
157
* tribunal_, a GUI for showing test results.
159
* testrepository_, a tool for gathering and managing test runs.
149
161
.. _subunit: https://launchpad.net/subunit/
162
.. _tribunal: https://launchpad.net/tribunal/
168
Bazaar ships with a config file for testrepository_. This can be very
169
useful for keeping track of failing tests and doing general workflow
170
support. To run tests using testrepository::
174
To run only failing tests::
176
$ testr run --failing
178
To run only some tests, without plugins::
180
$ test run test_selftest -- --no-plugins
182
See the testrepository documentation for more details.
184
.. _testrepository: https://launchpad.net/testrepository
187
Babune continuous integration
188
-----------------------------
190
We have a Hudson continuous-integration system that automatically runs
191
tests across various platforms. In the future we plan to add more
192
combinations including testing plugins. See
193
<http://babune.ladeuil.net:24842/>. (Babune = Bazaar Buildbot Network.)
196
Running tests in parallel
197
-------------------------
199
Bazaar can use subunit to spawn multiple test processes. There is
200
slightly more chance you will hit ordering or timing-dependent bugs but
203
$ ./bzr selftest --parallel=fork
205
Note that you will need the Subunit library
206
<https://launchpad.net/subunit/> to use this, which is in
207
``python-subunit`` on Ubuntu.
210
Running tests from a ramdisk
211
----------------------------
213
The tests create and delete a lot of temporary files. In some cases you
214
can make the test suite run much faster by running it on a ramdisk. For
218
$ sudo mount -t tmpfs none /ram
219
$ TMPDIR=/ram ./bzr selftest ...
221
You could also change ``/tmp`` in ``/etc/fstab`` to have type ``tmpfs``,
222
if you don't mind possibly losing other files in there when the machine
223
restarts. Add this line (if there is none for ``/tmp`` already)::
225
none /tmp tmpfs defaults 0 0
227
With a 6-core machine and ``--parallel=fork`` using a tmpfs doubles the
228
test execution speed.
352
430
The actual use of ScriptRunner within a TestCase looks something like
355
def test_unshelve_keep(self):
358
sr.run_script(self, '''
360
$ bzr shelve --all -m Foo
363
$ bzr unshelve --keep
433
from bzrlib.tests import script
435
def test_unshelve_keep(self):
437
script.run_script(self, '''
439
$ bzr shelve --all -m Foo
442
$ bzr unshelve --keep
449
You can also test commands that read user interaction::
451
def test_confirm_action(self):
452
"""You can write tests that demonstrate user confirmation"""
453
commands.builtin_command_registry.register(cmd_test_confirm)
454
self.addCleanup(commands.builtin_command_registry.remove, 'test-confirm')
457
2>Really do it? [y/n]:
371
462
Import tariff tests
372
463
-------------------
422
513
unless there is a good reason
516
Testing locking behaviour
517
-------------------------
519
In order to test the locking behaviour of commands, it is possible to install
520
a hook that is called when a write lock is: acquired, released or broken.
521
(Read locks also exist, they cannot be discovered in this way.)
523
A hook can be installed by calling bzrlib.lock.Lock.hooks.install_named_hook.
524
The three valid hooks are: `lock_acquired`, `lock_released` and `lock_broken`.
531
lock.Lock.hooks.install_named_hook('lock_acquired',
532
locks_acquired.append, None)
533
lock.Lock.hooks.install_named_hook('lock_released',
534
locks_released.append, None)
536
`locks_acquired` will now receive a LockResult instance for all locks acquired
537
since the time the hook is installed.
539
The last part of the `lock_url` allows you to identify the type of object that is locked.
541
- BzrDir: `/branch-lock`
542
- Working tree: `/checkout/lock`
543
- Branch: `/branch/lock`
544
- Repository: `/repository/lock`
546
To test if a lock is a write lock on a working tree, one can do the following::
548
self.assertEndsWith(locks_acquired[0].lock_url, "/checkout/lock")
550
See bzrlib/tests/commands/test_revert.py for an example of how to use this for
699
832
A base TestCase that extends the Python standard library's
700
TestCase in several ways. It adds more assertion methods (e.g.
701
``assertContainsRe``), ``addCleanup``, and other features (see its API
702
docs for details). It also has a ``setUp`` that makes sure that
703
global state like registered hooks and loggers won't interfere with
704
your test. All tests should use this base class (whether directly or
833
TestCase in several ways. TestCase is build on
834
``testtools.TestCase``, which gives it support for more assertion
835
methods (e.g. ``assertContainsRe``), ``addCleanup``, and other
836
features (see its API docs for details). It also has a ``setUp`` that
837
makes sure that global state like registered hooks and loggers won't
838
interfere with your test. All tests should use this base class
839
(whether directly or via a subclass). Note that we are trying not to
840
add more assertions at this point, and instead to build up a library
841
of ``bzrlib.tests.matchers``.
707
843
TestCaseWithMemoryTransport
708
844
Extends TestCase and adds methods like ``get_transport``,
781
917
Please see bzrlib.treebuilder for more details.
920
Temporarily changing state
921
~~~~~~~~~~~~~~~~~~~~~~~~~~
923
If your test needs to temporarily mutate some global state, and you need
924
it restored at the end, you can say for example::
926
self.overrideAttr(osutils, '_cached_user_encoding', 'latin-1')
931
Our base ``TestCase`` class provides an ``addCleanup`` method, which
932
should be used instead of ``tearDown``. All the cleanups are run when the
933
test finishes, regardless of whether it passes or fails. If one cleanup
934
fails, later cleanups are still run.
936
(The same facility is available outside of tests through
943
Generally we prefer automated testing but sometimes a manual test is the
944
right thing, especially for performance tests that want to measure elapsed
945
time rather than effort.
947
Simulating slow networks
948
------------------------
950
To get realistically slow network performance for manually measuring
951
performance, we can simulate 500ms latency (thus 1000ms round trips)::
953
$ sudo tc qdisc add dev lo root netem delay 500ms
955
Normal system behaviour is restored with ::
957
$ sudo tc qdisc del dev lo root
959
A more precise version that only filters traffic to port 4155 is::
961
tc qdisc add dev lo root handle 1: prio
962
tc qdisc add dev lo parent 1:3 handle 30: netem delay 500ms
963
tc qdisc add dev lo parent 30:1 handle 40: prio
964
tc filter add dev lo protocol ip parent 1:0 prio 3 u32 match ip dport 4155 0xffff flowid 1:3 handle 800::800
965
tc filter add dev lo protocol ip parent 1:0 prio 3 u32 match ip sport 4155 0xffff flowid 1:3 handle 800::801
969
tc filter del dev lo protocol ip parent 1: pref 3 u32
970
tc qdisc del dev lo root handle 1:
972
You can use similar code to add additional delay to a real network
973
interface, perhaps only when talking to a particular server or pointing at
974
a VM. For more information see <http://lartc.org/>.
784
977
.. |--| unicode:: U+2014
980
vim: ft=rst tw=74 ai et sw=4
added
removed
doc/developers/testing.txt
