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. 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.
147
format, so that test output can be post-processed by various tools.
161
149
.. _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
455
422
unless there is a good reason
458
Testing locking behaviour
459
-------------------------
461
In order to test the locking behaviour of commands, it is possible to install
462
a hook that is called when a write lock is: acquired, released or broken.
463
(Read locks also exist, they cannot be discovered in this way.)
465
A hook can be installed by calling bzrlib.lock.Lock.hooks.install_named_hook.
466
The three valid hooks are: `lock_acquired`, `lock_released` and `lock_broken`.
473
lock.Lock.hooks.install_named_hook('lock_acquired',
474
locks_acquired.append, None)
475
lock.Lock.hooks.install_named_hook('lock_released',
476
locks_released.append, None)
478
`locks_acquired` will now receive a LockResult instance for all locks acquired
479
since the time the hook is installed.
481
The last part of the `lock_url` allows you to identify the type of object that is locked.
483
- BzrDir: `/branch-lock`
484
- Working tree: `/checkout/lock`
485
- Branch: `/branch/lock`
486
- Repository: `/repository/lock`
488
To test if a lock is a write lock on a working tree, one can do the following::
490
self.assertEndsWith(locks_acquired[0].lock_url, "/checkout/lock")
492
See bzrlib/tests/commands/test_revert.py for an example of how to use this for
614
543
- UnicodeFilenameFeature
615
544
- FTPServerFeature
616
545
- CaseInsensitiveFilesystemFeature.
617
- chown_feature: The test can rely on OS being POSIX and python
619
- posix_permissions_feature: The test can use POSIX-style
620
user/group/other permission bits.
623
548
Defining a new feature that tests can require
774
699
A base TestCase that extends the Python standard library's
775
TestCase in several ways. TestCase is build on
776
``testtools.TestCase``, which gives it support for more assertion
777
methods (e.g. ``assertContainsRe``), ``addCleanup``, and other
778
features (see its API docs for details). It also has a ``setUp`` that
779
makes sure that global state like registered hooks and loggers won't
780
interfere with your test. All tests should use this base class
781
(whether directly or via a subclass). Note that we are trying not to
782
add more assertions at this point, and instead to build up a library
783
of ``bzrlib.tests.matchers``.
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
785
707
TestCaseWithMemoryTransport
786
708
Extends TestCase and adds methods like ``get_transport``,
added
removed
doc/developers/testing.txt
