diff options
| author | Martin Trigaux <mat@odoo.com> | 2016-10-11 11:11:52 +0200 |
|---|---|---|
| committer | Martin Trigaux <mat@odoo.com> | 2016-10-11 12:09:27 +0200 |
| commit | 95280245367da42fead8be9892079a5795171fd0 (patch) | |
| tree | 072b5191d1ee1e30e8b5fa1cf23f8e5353a3c06e /doc/reference/testing.rst | |
| parent | acaf0f1e190326775e5bcd93daf4146e320e27e5 (diff) | |
[FIX] doc: building correctly autoclass references
Diffstat (limited to 'doc/reference/testing.rst')
| -rw-r--r-- | doc/reference/testing.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/reference/testing.rst b/doc/reference/testing.rst index 53690426103..5d3a2d93f9b 100644 --- a/doc/reference/testing.rst +++ b/doc/reference/testing.rst @@ -42,22 +42,22 @@ The test runner will simply run any test case, as described in the official `unittest documentation`_, but Odoo provides a number of utilities and helpers related to testing Odoo content (modules, mainly): -.. autoclass:: openerp.tests.common.TransactionCase +.. autoclass:: odoo.tests.common.TransactionCase :members: browse_ref, ref -.. autoclass:: openerp.tests.common.SingleTransactionCase +.. autoclass:: odoo.tests.common.SingleTransactionCase :members: browse_ref, ref By default, tests are run once right after the corresponding module has been installed. Test cases can also be configured to run after all modules have been installed, and not run right after the module installation: -.. autofunction:: openerp.tests.common.at_install +.. autofunction:: odoo.tests.common.at_install -.. autofunction:: openerp.tests.common.post_install +.. autofunction:: odoo.tests.common.post_install The most common situation is to use -:class:`~openerp.tests.common.TransactionCase` and test a property of a model +:class:`~odoo.tests.common.TransactionCase` and test a property of a model in each method:: class TestModelA(common.TransactionCase): |