329
329
We make selective use of doctests__. In general they should provide
330
330
*examples* within the API documentation which can incidentally be tested. We
331
331
don't try to test every important case using doctests |--| regular Python
332
tests are generally a better solution. That is, we just use doctests to
333
make our documentation testable, rather than as a way to make tests.
332
tests are generally a better solution. That is, we just use doctests to make
333
our documentation testable, rather than as a way to make tests. Be aware that
334
doctests are not as well isolated as the unit tests, if you need more
335
isolation, you're likely want to write unit tests anyway if only to get a
336
better control of the test environment.
335
338
Most of these are in ``bzrlib/doc/api``. More additions are welcome.
337
340
__ http://docs.python.org/lib/module-doctest.html
342
There is an `assertDoctestExampleMatches` method in
343
`bzrlib.tests.TestCase` that allows you to match against doctest-style
344
string templates (including ``...`` to skip sections) from regular Python
343
``bzrlib/tests/script.py`` allows users to write tests in a syntax very close to a shell session,
344
using a restricted and limited set of commands that should be enough to mimic
345
most of the behaviours.
351
``bzrlib/tests/script.py`` allows users to write tests in a syntax very
352
close to a shell session, using a restricted and limited set of commands
353
that should be enough to mimic most of the behaviours.
347
355
A script is a set of commands, each command is composed of:
367
375
The execution stops as soon as an expected output or an expected error is not
370
When no output is specified, any ouput from the command is accepted
371
and execution continue.
378
If output occurs and no output is expected, the execution stops and the
379
test fails. If unexpected output occurs on the standard error, then
380
execution stops and the test fails.
373
382
If an error occurs and no expected error is specified, the execution stops.
445
You can run files containing shell-like scripts with::
447
$ bzr test-script <script>
449
where ``<script>`` is the path to the file containing the shell-like script.
430
451
The actual use of ScriptRunner within a TestCase looks something like
435
456
def test_unshelve_keep(self):
436
457
# some setup here
437
458
script.run_script(self, '''
439
$ bzr shelve --all -m Foo
460
$ bzr shelve -q --all -m Foo
440
461
$ bzr shelve --list
442
$ bzr unshelve --keep
463
$ bzr unshelve -q --keep
443
464
$ bzr shelve --list
483
To avoid having to specify "-q" for all commands whose output is
484
irrelevant, the run_script() method may be passed the keyword argument
485
``null_output_matches_anything=True``. For example::
487
def test_ignoring_null_output(self):
490
$ bzr ci -m 'first revision' --unchanged
493
""", null_output_matches_anything=True)
462
496
Import tariff tests
463
497
-------------------
484
518
This is done by running the command in a subprocess with
485
``--profile-imports``. Starting a whole Python interpreter is pretty
486
slow, so we don't want exhaustive testing here, but just enough to guard
487
against distinct fixed problems.
519
``PYTHON_VERBOSE=1``. Starting a whole Python interpreter is pretty slow,
520
so we don't want exhaustive testing here, but just enough to guard against
521
distinct fixed problems.
489
523
Assertions about precisely what is loaded tend to be brittle so we instead
490
524
make assertions that particular things aren't loaded.
711
745
_test_needs_features = [features.apport]
749
-----------------------
751
Translations are disabled by default in tests. If you want to test
752
that code is translated you can use the ``ZzzTranslations`` class from
755
self.overrideAttr(i18n, '_translations', ZzzTranslations())
757
And check the output strings look like ``u"zz\xe5{{output}}"``.
759
To test the gettext setup and usage you override i18n.installed back
760
to self.i18nInstalled and _translations to None, see
761
test_i18n.TestInstall.
714
764
Testing deprecated code
715
765
-----------------------
805
855
whether a test should be added for that particular implementation,
806
856
or for all implementations of the interface.
808
The multiplication of tests for different implementations is normally
809
accomplished by overriding the ``load_tests`` function used to load tests
810
from a module. This function typically loads all the tests, then applies
811
a TestProviderAdapter to them, which generates a longer suite containing
812
all the test variations.
814
858
See also `Per-implementation tests`_ (above).
861
Test scenarios and variations
862
-----------------------------
820
864
Some utilities are provided for generating variations of tests. This can
821
865
be used for per-implementation tests, or other cases where the same test
826
870
values to which the test should be applied. The test suite should then
827
871
also provide a list of scenarios in which to run the tests.
829
Typically ``multiply_tests_from_modules`` should be called from the test
830
module's ``load_tests`` function.
873
A single *scenario* is defined by a `(name, parameter_dict)` tuple. The
874
short string name is combined with the name of the test method to form the
875
test instance name. The parameter dict is merged into the instance's
880
load_tests = load_tests_apply_scenarios
882
class TestCheckout(TestCase):
884
scenarios = multiply_scenarios(
885
VaryByRepositoryFormat(),
889
The `load_tests` declaration or definition should be near the top of the
890
file so its effect can be seen.
933
993
Please see bzrlib.treebuilder for more details.
998
PreviewTrees are based on TreeTransforms. This means they can represent
999
virtually any state that a WorkingTree can have, including unversioned files.
1000
They can be used to test the output of anything that produces TreeTransforms,
1001
such as merge algorithms and revert. They can also be used to test anything
1002
that takes arbitrary Trees as its input.
1006
# Get an empty tree to base the transform on.
1007
b = self.make_branch('.')
1008
empty_tree = b.repository.revision_tree(_mod_revision.NULL_REVISION)
1009
tt = TransformPreview(empty_tree)
1010
self.addCleanup(tt.finalize)
1011
# Empty trees don't have a root, so add it first.
1012
root = tt.new_directory('', ROOT_PARENT, 'tree-root')
1013
# Set the contents of a file.
1014
tt.new_file('new-file', root, 'contents', 'file-id')
1015
preview = tt.get_preview_tree()
1016
# Test the contents.
1017
self.assertEqual('contents', preview.get_file_text('file-id'))
1019
PreviewTrees can stack, with each tree falling back to the previous::
1021
tt2 = TransformPreview(preview)
1022
self.addCleanup(tt2.finalize)
1023
tt2.new_file('new-file2', tt2.root, 'contents2', 'file-id2')
1024
preview2 = tt2.get_preview_tree()
1025
self.assertEqual('contents', preview2.get_file_text('file-id'))
1026
self.assertEqual('contents2', preview2.get_file_text('file-id2'))
936
1029
Temporarily changing state
937
1030
~~~~~~~~~~~~~~~~~~~~~~~~~~
942
1035
self.overrideAttr(osutils, '_cached_user_encoding', 'latin-1')
1037
This should be used with discretion; sometimes it's better to make the
1038
underlying code more testable so that you don't need to rely on monkey
1042
Observing calls to a function
1043
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1045
Sometimes it's useful to observe how a function is called, typically when
1046
calling it has side effects but the side effects are not easy to observe
1047
from a test case. For instance the function may be expensive and we want
1048
to assert it is not called too many times, or it has effects on the
1049
machine that are safe to run during a test but not easy to measure. In
1050
these cases, you can use `recordCalls` which will monkey-patch in a
1051
wrapper that records when the function is called.
1054
Temporarily changing environment variables
1055
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1057
If yout test needs to temporarily change some environment variable value
1058
(which generally means you want it restored at the end), you can use::
1060
self.overrideEnv('BZR_ENV_VAR', 'new_value')
1062
If you want to remove a variable from the environment, you should use the
1063
special ``None`` value::
1065
self.overrideEnv('PATH', None)
1067
If you add a new feature which depends on a new environment variable, make
1068
sure it behaves properly when this variable is not defined (if applicable) and
1069
if you need to enforce a specific default value, check the
1070
``TestCase._cleanEnvironment`` in ``bzrlib.tests.__init__.py`` which defines a
1071
proper set of values for all tests.
977
1106
tc qdisc add dev lo root handle 1: prio
978
1107
tc qdisc add dev lo parent 1:3 handle 30: netem delay 500ms
979
tc qdisc add dev lo parent 30:1 handle 40: prio
980
tc filter add dev lo protocol ip parent 1:0 prio 3 u32 match ip dport 4155 0xffff flowid 1:3 handle 800::800
981
tc filter add dev lo protocol ip parent 1:0 prio 3 u32 match ip sport 4155 0xffff flowid 1:3 handle 800::801
1108
tc filter add dev lo protocol ip parent 1:0 prio 3 u32 match ip dport 4155 0xffff flowid 1:3
1109
tc filter add dev lo protocol ip parent 1:0 prio 3 u32 match ip sport 4155 0xffff flowid 1:3
983
1111
and to remove this::
added
removed
doc/developers/testing.txt
