6
6
The Importance of Testing
7
7
=========================
9
Reliability is a critical success factor for any Version Control System.
9
Reliability is a critical success factor for any version control system.
10
10
We want Bazaar to be highly reliable across multiple platforms while
11
11
evolving over time to meet the needs of its community.
184
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.
385
436
The actual use of ScriptRunner within a TestCase looks something like
388
def test_unshelve_keep(self):
391
sr.run_script(self, '''
393
$ bzr shelve --all -m Foo
396
$ bzr unshelve --keep
439
from bzrlib.tests import script
441
def test_unshelve_keep(self):
443
script.run_script(self, '''
445
$ bzr shelve --all -m Foo
448
$ bzr unshelve --keep
455
You can also test commands that read user interaction::
457
def test_confirm_action(self):
458
"""You can write tests that demonstrate user confirmation"""
459
commands.builtin_command_registry.register(cmd_test_confirm)
460
self.addCleanup(commands.builtin_command_registry.remove, 'test-confirm')
463
2>Really do it? [y/n]:
404
468
Import tariff tests
405
469
-------------------
420
484
dependencies and only needed for particular cases. If they're loaded in
421
485
other cases then bzr may break for people who don't have those modules.
423
`test_import_tarrif` allows us to check that removal of imports doesn't
487
`test_import_tariff` allows us to check that removal of imports doesn't
426
490
This is done by running the command in a subprocess with
653
717
_test_needs_features = [features.apport]
720
Testing deprecated code
721
-----------------------
723
When code is deprecated, it is still supported for some length of time,
724
usually until the next major version. The ``applyDeprecated`` helper
725
wraps calls to deprecated code to verify that it is correctly issuing the
726
deprecation warning, and also prevents the warnings from being printed
729
Typically patches that apply the ``@deprecated_function`` decorator should
730
update the accompanying tests to use the ``applyDeprecated`` wrapper.
732
``applyDeprecated`` is defined in ``bzrlib.tests.TestCase``. See the API
733
docs for more details.
656
736
Testing exceptions and errors
657
737
-----------------------------
731
811
whether a test should be added for that particular implementation,
732
812
or for all implementations of the interface.
734
The multiplication of tests for different implementations is normally
735
accomplished by overriding the ``load_tests`` function used to load tests
736
from a module. This function typically loads all the tests, then applies
737
a TestProviderAdapter to them, which generates a longer suite containing
738
all the test variations.
740
814
See also `Per-implementation tests`_ (above).
817
Test scenarios and variations
818
-----------------------------
746
820
Some utilities are provided for generating variations of tests. This can
747
821
be used for per-implementation tests, or other cases where the same test
752
826
values to which the test should be applied. The test suite should then
753
827
also provide a list of scenarios in which to run the tests.
755
Typically ``multiply_tests_from_modules`` should be called from the test
756
module's ``load_tests`` function.
829
A single *scenario* is defined by a `(name, parameter_dict)` tuple. The
830
short string name is combined with the name of the test method to form the
831
test instance name. The parameter dict is merged into the instance's
836
load_tests = load_tests_apply_scenarios
838
class TestCheckout(TestCase):
840
variations = multiply_scenarios(
841
VaryByRepositoryFormat(),
845
The `load_tests` declaration or definition should be near the top of the
846
file so its effect can be seen.
859
949
Please see bzrlib.treebuilder for more details.
952
Temporarily changing state
953
~~~~~~~~~~~~~~~~~~~~~~~~~~
955
If your test needs to temporarily mutate some global state, and you need
956
it restored at the end, you can say for example::
958
self.overrideAttr(osutils, '_cached_user_encoding', 'latin-1')
963
Our base ``TestCase`` class provides an ``addCleanup`` method, which
964
should be used instead of ``tearDown``. All the cleanups are run when the
965
test finishes, regardless of whether it passes or fails. If one cleanup
966
fails, later cleanups are still run.
968
(The same facility is available outside of tests through
975
Generally we prefer automated testing but sometimes a manual test is the
976
right thing, especially for performance tests that want to measure elapsed
977
time rather than effort.
979
Simulating slow networks
980
------------------------
982
To get realistically slow network performance for manually measuring
983
performance, we can simulate 500ms latency (thus 1000ms round trips)::
985
$ sudo tc qdisc add dev lo root netem delay 500ms
987
Normal system behaviour is restored with ::
989
$ sudo tc qdisc del dev lo root
991
A more precise version that only filters traffic to port 4155 is::
993
tc qdisc add dev lo root handle 1: prio
994
tc qdisc add dev lo parent 1:3 handle 30: netem delay 500ms
995
tc qdisc add dev lo parent 30:1 handle 40: prio
996
tc filter add dev lo protocol ip parent 1:0 prio 3 u32 match ip dport 4155 0xffff flowid 1:3 handle 800::800
997
tc filter add dev lo protocol ip parent 1:0 prio 3 u32 match ip sport 4155 0xffff flowid 1:3 handle 800::801
1001
tc filter del dev lo protocol ip parent 1: pref 3 u32
1002
tc qdisc del dev lo root handle 1:
1004
You can use similar code to add additional delay to a real network
1005
interface, perhaps only when talking to a particular server or pointing at
1006
a VM. For more information see <http://lartc.org/>.
862
1009
.. |--| unicode:: U+2014
1012
vim: ft=rst tw=74 ai et sw=4
added
removed
doc/developers/testing.txt
