blocks|key|410255|text|我不认为nose可以直接控制这一点:当发出警告时，警告模块不会引发异常。warnings模块允许您控制应将哪些警告作为异常引发。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|410256|entityMap^0|10|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I don't think nose can directly control this: the warnings module doesn't raise an exception when the warning is issued. The <code>warnings</code> module gives you control over which warnings should be raised as exceptions.

blocks|key|3466734|text|nosetests是一个小的Python脚本。使用编辑器打开它，并在第一行的末尾添加-W+error。这将告诉Python解释器将警告转换为异常。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3466735|更简单的方法是使用Python环境变量注入“视警告为错误”标志：|3466736|PYTHONWARNINGS=error+nosetests+test/test_*.py+--pdb|code-block|syntax|javascript|3466737|entityMap^0|0|9|16|8|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

<code>nosetests</code> is a small Python script. Open it with an editor, and add <code>-W error</code> at the end of the first line. This tells the Python interpreter to convert warnings into exceptions.

Even simpler is to use Python environment variable to inject "treat warnings as errors" flag:

<pre><code>PYTHONWARNINGS=error nosetests test/test_*.py --pdb
</code></pre>

blocks|key|3253820|text|@khinsen的回答很有帮助，但如果在测试发现过程中发出以下警告(否则用户看不到)，则会使nosetest的执行停止："ImportWarning:不导入目录'XXX'：缺少__init__.py|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3253821|此外，在导入模块期间引发的警告(与在测试期间引发的警告相反)不应被视为错误。|3253822|我遵循@dbw的建议编写了一个插件，可以在github上找到：https://github.com/Bernhard10/WarnAsError|3253823|一个鼻部插件WarnAsError|3253824|在configure和options函数旁边，插件实现了prepareTestRunner，其中它用一个具有不同run方法的类替换了默认的TestRunner：|3253825|def+prepareTestRunner(self,+runner):
++++return+WaETestRunner(runner)|code-block|syntax|javascript|3253826|该类存储原始的TestRunner，它的run-Method使用不同的warnings.simplefilter调用原始的TestRunner的run方法。|3253827|class+WaETestRunner(object):
++++def+__init__(self,+runner):
++++++++self.runner=runner
++++def+run(self,+test):
++++++++with+warnings.catch_warnings():
++++++++++++warnings.simplefilter("error")
++++++++++++return+self.runner.run(test)|3253828|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Bernhard10/WarnAsError^0|2G|B|0|0|V|15|0|0|0|1|9|B|7|S|H|0|0|K|3|Z|L|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|J|3|K|5|6|7|1C|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|N|3|O|5|P|7|1K|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|U|3|V|5|P|7|1Q|8|@]|D|@]|E|$Q|R]]|$1|W|3|-4|5|6|7|1R|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]]]

The answer by @khinsen helps a lot, but makes the execution of nosetests stop, if it issues the following warning during test discovery (which is otherwise not visible to the user): "ImportWarning: Not importing directory 'XXX': missing <code>__init__.py</code>

Furthermore, warnings raised during the import of a module (as opposed to warnings raised during a test) should not be treated as errors.

I followed @dbw's advice in writing a plugin, which can be found a github: <a href="https://github.com/Bernhard10/WarnAsError" rel="noreferrer">https://github.com/Bernhard10/WarnAsError</a>

<h1>A nose plugin WarnAsError</h1>

Next to the <code>configure</code> and <code>options</code> functions, the plugin implements <code>prepareTestRunner</code>, where it replaces the default TestRunner by a class which has a different run method:

<pre><code>def prepareTestRunner(self, runner):
 return WaETestRunner(runner)
</code></pre>

This class stores the original TestRunner and its <code>run</code>-Method calls the original TestRunner's run method with a different <code>warnings.simplefilter</code>.

<pre><code>class WaETestRunner(object):
 def __init__(self, runner):
 self.runner=runner
 def run(self, test):
 with warnings.catch_warnings():
 warnings.simplefilter("error")
 return self.runner.run(test)
</code></pre>

When running <code>nosetests</code> from the command line, how do you specify that 'non-ignored' warnings should be treated as errors?

By default, warnings are printed, but not counted as failures:

<pre><code>[snip]/service/accounts/database.py:151: SADeprecationWarning: Use session.add()
 self.session.save(state)
[snip]/service/accounts/database.py:97: SADeprecationWarning: Use session.add()
 self.session.save(user)
............
----------------------------------------------------------------------
Ran 12 tests in 0.085s

OK
</code></pre>

As we don't want our code to generate warnings, I don't want this situation to be <code>OK</code>.

Thanks!

Edit:
Ideally what I'd like is a nosetests command line option that issues a <code>warnings.simplefilter('error')</code> prior to each test (and cleans it out afterwards).

Any solution that involves using the <code>warnings</code> module in the test code seems to defeat the point. I don't want to manually edit each test module to transform warnings into errors. Plus I don't want the author of each test module to be able to forget to 'turn on' warning errors.

Run nosetests with warnings as errors?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

从命令行运行nosetests时，如何指定将“非忽略”警告视为错误？默认情况下，将打印警告，但不会将其计入失败：[snip]/service/accounts/database.py:151: SADeprecationWarning: Use session.add()  self.session.save(stat...

问是否将nosetests和警告作为错误运行？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否将nosetests和警告作为错误运行？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否将nosetests和警告作为错误运行？
EN