diff options
| author | Vo Minh Thu <vmt@openerp.com> | 2012-10-30 12:37:37 +0100 |
|---|---|---|
| committer | Vo Minh Thu <vmt@openerp.com> | 2012-10-30 12:37:37 +0100 |
| commit | c902eb4539fae8035a243dd54e2f60f95c8484a8 (patch) | |
| tree | 7e8be67fd80d0b6d6c8a0565b918dc9d09298621 /doc | |
| parent | 71b2765bd7ab64b7a363eb9a49afc3c2c66b7c80 (diff) | |
[DOC] openerp.tests.common: now included in the test-framework page.
bzr revid: vmt@openerp.com-20121030113737-10h045k368pbrldq
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/test-framework.rst | 12 |
1 files changed, 9 insertions, 3 deletions
diff --git a/doc/test-framework.rst b/doc/test-framework.rst index 56951b1a8e1..f53d15ae0da 100644 --- a/doc/test-framework.rst +++ b/doc/test-framework.rst @@ -87,9 +87,9 @@ In addition to the above possibilities, when invoked with a non-existing module sub-modules. Depending on the unittest2_ class that is used to write the tests (see -``openerp.tests.common`` for some helper classes that you can re-use), a database -may be created before the test is run, and the module providing the test will -be installed on that database. +:mod:`openerp.tests.common` for some helper classes that you can re-use), a +database may be created before the test is run, and the module providing the +test will be installed on that database. Because creating a database, installing modules, and then dropping it is expensive, it is possible to interleave the run of the ``fast_suite`` tests @@ -98,3 +98,9 @@ each requested module is installed, its fast_suite tests are run. The database is thus created and dropped (and the modules installed) only once. .. _unittest2: http://pypi.python.org/pypi/unittest2 + +TestCase subclasses +------------------- + +.. automodule:: openerp.tests.common + :members: |
