blocks|key|3528788|text|@aftab，您需要添加log-level，请参阅下面。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3528789|./odoo.py+-d+<dbname>+--test-enable+--log-level=test|code-block|syntax|javascript|3528790|对于您的问题，如果您正在更改已安装的模块并需要重新测试所有测试用例，那么您需要使用上面的命令使用-u+<module_name>或-u+all(对于所有模块)简单地重新启动服务器。|3528791|entityMap^0|C|9|0|0|1C|G|1T|6|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

@aftab You need add <code>log-level</code> please see below.

<pre><code>./odoo.py -d &lt;dbname&gt; --test-enable --log-level=test
</code></pre>

and regarding you question, If you are making changes to installed modules and need to re test all test cases then you need to simple restart you server with <code>-u &lt;module_name&gt;</code> or <code>-u all</code>(for all modules) with the above command.

blocks|key|3528774|text|这对于运行odoo测试用例很有用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3528775|./odoo.py+-i/-u+module_being_tested+-d+being_used_to_test+--test-enable|code-block|syntax|javascript|3528776|共同选择：|3528777|+-i+INIT,+--init=INIT
+++++++install+one+or+more+modules+(comma-separated+list,+use+"all"+for+all+modules),+requires+-d

-u+UPDATE,+--update=UPDATE
+++++++update+one+or+more+modules+(comma-separated+list,+use+"all"+for+all+modules).+Requires+-d.|3528778|与数据库有关的备选方案：|3528779|-d+DB_NAME,+--database=DB_NAME
+++++++specify+the+database+name|3528780|测试配置：|3528781|+--test-enable:++Enable+YAML+and+unit+tests.|3528782|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

This useful For Run odoo test case:

<pre><code>./odoo.py -i/-u module_being_tested -d being_used_to_test --test-enable
</code></pre>

Common options:

<pre><code> -i INIT, --init=INIT
 install one or more modules (comma-separated list, use "all" for all modules), requires -d

-u UPDATE, --update=UPDATE
 update one or more modules (comma-separated list, use "all" for all modules). Requires -d.
</code></pre>

Database related options:

<pre><code>-d DB_NAME, --database=DB_NAME
 specify the database name
</code></pre>

Testing Configuration:

<pre><code> --test-enable: Enable YAML and unit tests.
</code></pre>

blocks|key|1750077|text|下面是一个非常好的插件，可以直接使用pytest运行单元odoo测试：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1750078|https://github.com/camptocamp/pytest-odoo|offset|length|1750079|下面是一个结果示例：|1750080|​|1750081|📷|atomic|1750082|1750083|entityMap|0|LINK|mutability|MUTABLE|url|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/37df7490170371d4738f0fed7d1c71e1.png|imageAlt^0|0|0|15|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|M|3|I|5|6|7|1B|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|C]]|U|$5|V|R|W|A|$X|Y|Z|-4]]]]

Here is a REALLY nice plugin to run unit odoo tests directly with pytest:

<a href="https://github.com/camptocamp/pytest-odoo" rel="nofollow noreferrer">https://github.com/camptocamp/pytest-odoo</a>

Here's a result example:

<a href="https://i.stack.imgur.com/YOt6B.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/YOt6B.png" alt="enter image description here"></a>

blocks|key|1659883|text|为了实现这一点，我使用了docker+%2B+pytest-odoo+%2Bpy魅力(使用远程解释器)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659884|首先，设置如下的Dockerfile：|1659885|FROM+odoo:14
USER+root
RUN+apt-get+update+&&+\
++++apt-get+install+-y+--no-install-recommends+\
++++++++python3-pip
RUN+pip3+install+pytest-odoo+coverage+pytest-html
USER+odoo|code-block|syntax|javascript|1659886|一个像这样的码头工人：|1659887|version:+'2'

services:
++web:
++++container_name:+plusteam-odoo-web
++++build:
++++++context:+.
++++++dockerfile:+Dockerfile
++++image:+odoo:14
++++depends_on:
++++++-+db
++++ports:
++++++-+"8069:8069"
++++volumes:
++++++-+odoo-web-data:/var/lib/odoo
++++++-+./config:/etc/odoo
++++++-+./addons:/mnt/extra-addons
++++command:+--dev+all
++db:
++++container_name:+plusteam-odoo-db
++++image:+postgres:13
++++ports:
++++++-+"5432:5432"
++++environment:
++++++-+POSTGRES_DB=postgres
++++++-+POSTGRES_PASSWORD=odoo
++++++-+POSTGRES_USER=odoo
++++++-+PGDATA=/var/lib/postgresql/data/pgdata
++++volumes:
++++++-+odoo-db-data:/var/lib/postgresql/data/pgdata
volumes:
++odoo-web-data:
++odoo-db-data:|1659888|因此，我们用包扩展odoo映像，以生成覆盖报告和pytest-odoo。|offset|length|style|CODE|1659889|一旦您这样做了，您可以运行docker-compose+up+-d来使odoo实例运行，odoo容器将安装pytest-odoo，下一部分是告诉py魅力使用带有odoo修改的映像(包括pyest-odoo包)的远程解释器：|1659890|​|1659891|📷|atomic|1659892|1659893|现在，每当您以py魅力运行脚本时，它们都会根据您提供的映像启动一个新容器。|1659894|在检查了由py魅力启动的容器之后，我意识到它们将项目的目录绑定到容器内的/opt/project/目录，这很有用，因为在运行测试时需要修改odoo.conf文件。|1659895|1659896|1659897|您可以为自定义测试db自定义数据库连接，重要的是您需要将addons_path选项映射到/opt/project/addons，或者可以使用您的自定义加载项的容器中的最终路径。|1659898|有了这个，您就可以为pytest创建如下所示的pycharm脚本：|1659899|1659900|1659901|1659902|请注意，我们是如何为odoo配置提供路径的，并对其进行了修改以进行测试，这样，由py魅力启动的容器中可用的odoo就可以知道您的自定义addon代码位于何处。|1659903|现在，我们可以运行脚本，甚至调试它，一切都将如预期的那样工作。|1659904|1659905|1659906|1659907|在一篇中型文章中，我进一步讨论了这个问题(我的特定解决方案)，我甚至用一个工作演示编写了一个存储库，这样您就可以尝试一下，希望这会有所帮助：|1659908|https://medium.com/plusteam/how-to-run-odoo-tests-with-pycharm-51e4823bdc59+https://github.com/JSilversun/odoo-testing-example|1659909|请注意，使用远程解释器，您只需确保odoo二进制文件能够正确找到addons文件夹，您就可以设置:)此外，使用Dockerfile扩展映像有助于加快开发速度。|1659910|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/9e832e1a998a15c1b3576aa103688e8c.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/9d8487434e0b3f657117fe420bb29452.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/fac4d38a7bfcac800d0413402c2a82b1.png|3|https://developer.qcloudimg.com/http-save/yehe-900000/c9a918cf2cbc56cb132caeddf69ee63d.png|4|LINK|MUTABLE|url|https://medium.com/plusteam/how-to-run-odoo-tests-with-pycharm-51e4823bdc59|5|https://github.com/JSilversun/odoo-testing-example^0|0|0|0|0|0|O|B|0|D|K|1H|B|2K|A|0|0|0|1|0|0|0|0|10|D|1X|9|0|0|1|1|0|0|S|B|18|J|0|0|0|0|1|2|0|0|0|0|0|0|1|3|0|0|0|0|23|4|24|1E|5|0|0^^$0|@$1|2|3|4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2D|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|2E|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|2F|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|2G|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|2H|8|@$O|2I|P|2J|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|2K|8|@$O|2L|P|2M|Q|R]|$O|2N|P|2O|Q|R]|$O|2P|P|2Q|Q|R]]|9|@]|A|$]]|$1|U|3|V|5|6|7|2R|8|@]|9|@]|A|$]]|$1|W|3|X|5|Y|7|2S|8|@]|9|@$O|2T|P|2U|1|2V]]|A|$]]|$1|Z|3|V|5|6|7|2W|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2X|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|2Y|8|@$O|2Z|P|30|Q|R]|$O|31|P|32|Q|R]]|9|@]|A|$]]|$1|14|3|X|5|Y|7|33|8|@]|9|@$O|34|P|35|1|36]]|A|$]]|$1|15|3|V|5|6|7|37|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|38|8|@$O|39|P|3A|Q|R]|$O|3B|P|3C|Q|R]]|9|@]|A|$]]|$1|18|3|19|5|6|7|3D|8|@]|9|@]|A|$]]|$1|1A|3|V|5|6|7|3E|8|@]|9|@]|A|$]]|$1|1B|3|X|5|Y|7|3F|8|@]|9|@$O|3G|P|3H|1|3I]]|A|$]]|$1|1C|3|V|5|6|7|3J|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|3K|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|3L|8|@]|9|@]|A|$]]|$1|1H|3|V|5|6|7|3M|8|@]|9|@]|A|$]]|$1|1I|3|X|5|Y|7|3N|8|@]|9|@$O|3O|P|3P|1|3Q]]|A|$]]|$1|1J|3|V|5|6|7|3R|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|3S|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|3T|8|@]|9|@$O|3U|P|3V|1|3W]|$O|3X|P|3Y|1|3Z]]|A|$]]|$1|1O|3|1P|5|6|7|40|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|41|8|@]|9|@]|A|$]]]|1R|$1S|$5|1T|1U|1V|A|$1W|1X|1Y|-4]]|1Z|$5|1T|1U|1V|A|$1W|20|1Y|-4]]|21|$5|1T|1U|1V|A|$1W|22|1Y|-4]]|23|$5|1T|1U|1V|A|$1W|24|1Y|-4]]|25|$5|26|1U|27|A|$28|29]]|2A|$5|26|1U|27|A|$28|2B]]]]

I was able to run odoo's tests using pycharm, to achieve this I used docker + pytest-odoo + pycharm (using remote interpreters).
First you setup a Dockerfile like this:
<pre><code>FROM odoo:14
USER root
RUN apt-get update &amp;&amp; \
 apt-get install -y --no-install-recommends \
 python3-pip
RUN pip3 install pytest-odoo coverage pytest-html
USER odoo
</code></pre>
And a docker-compose.yml like this:
<pre><code>version: '2'

services:
 web:
 container_name: plusteam-odoo-web
 build:
 context: .
 dockerfile: Dockerfile
 image: odoo:14
 depends_on:
 - db
 ports:
 - &quot;8069:8069&quot;
 volumes:
 - odoo-web-data:/var/lib/odoo
 - ./config:/etc/odoo
 - ./addons:/mnt/extra-addons
 command: --dev all
 db:
 container_name: plusteam-odoo-db
 image: postgres:13
 ports:
 - &quot;5432:5432&quot;
 environment:
 - POSTGRES_DB=postgres
 - POSTGRES_PASSWORD=odoo
 - POSTGRES_USER=odoo
 - PGDATA=/var/lib/postgresql/data/pgdata
 volumes:
 - odoo-db-data:/var/lib/postgresql/data/pgdata
volumes:
 odoo-web-data:
 odoo-db-data:
</code></pre>
So we extend an odoo image with packages to generate coverage reports and <code>pytest-odoo</code>
Once you have this, you can run <code>docker-compose up -d</code> to get your odoo instance running, the odoo container will have <code>pytest-odoo</code> installed, the next part is to tell pycharm to use a remote interpreter with the odoo modified image including the <code>pyest-odoo</code> package:
<a href="https://i.stack.imgur.com/vTWaf.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/vTWaf.png" alt="enter image description here" /></a>
Now every time you run a script in pycharm they will launch a new container based on the image you provided.
After examining the containers launched by pycharm I realized they bind the project's directory to the <code>/opt/project/</code> directory inside the container, this is useful because you will need to modify the <code>odoo.conf</code> file when you run your tests.
<a href="https://i.stack.imgur.com/Ik2md.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Ik2md.png" alt="enter image description here" /></a>
You can customize the database connection for a custom testing db which you should do, and the important part is that you need to map the <code>addons_path</code> option to <code>/opt/project/addons</code> or the final path inside the containers launched by pycharm where your custom addons are available.
With this you can create a pycharm script for pytest like this:
<a href="https://i.stack.imgur.com/XuyTh.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/XuyTh.png" alt="enter image description here" /></a>
Notice how we provided the path for the odoo config with modifications for testing, this way the odoo available in the container launched by pycharm will know where your custom addon's code is located.
Now we can run the script and even debug it and everything will work as expected.
<a href="https://i.stack.imgur.com/h9zfi.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/h9zfi.png" alt="enter image description here" /></a>
I go further in this matter (my particular solution) in a medium article, I even wrote a repository with a working demo so you can try it out, hope this helps:
<a href="https://medium.com/plusteam/how-to-run-odoo-tests-with-pycharm-51e4823bdc59" rel="nofollow noreferrer">https://medium.com/plusteam/how-to-run-odoo-tests-with-pycharm-51e4823bdc59</a> <a href="https://github.com/JSilversun/odoo-testing-example" rel="nofollow noreferrer">https://github.com/JSilversun/odoo-testing-example</a>
Be aware that using remote interpreters you just need to make sure the odoo binary can find the addons folder properly and you will be all set :) besides using a Dockerfile to extend an image helps to speed up development.

I tried running odoo tests using --test-enable, but it won't work. I have a couple of questions.

According to the documentation Tests can only be run during module installation, what happens when we add functionality and then want to run tests? 

Is it possible to run tests from IDE like Pycharm ?

How to run Odoo tests unittest2?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我试着用--启用测试--运行odoo测试，但是它不能工作。我有几个问题要问。根据文档测试只能在模块安装期间运行，当我们添加功能然后要运行测试时会发生什么？可以像Pycharm这样的IDE运行测试吗？

问如何运行Odoo测试unittest2？
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何运行Odoo测试unittest2？EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何运行Odoo测试unittest2？
EN