blocks|key|2179923|text|我最近使用v19.0.0中引入的jest.spyOn实现了这一点，以模拟console的warn方法(它是通过global上下文/对象访问的)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2179924|然后，可以expect表示模拟的warn没有被调用，如下所示。|2179925|describe('A+function+that+does+something',+()+=>+{
++it('Should+not+trigger+a+warning',+()+=>+{
++++var+warn+=+jest.spyOn(global.console,+'warn');

++++//+Do+something+that+may+trigger+warning+via+`console.warn`
++++doSomething();

++++//+...+i.e.
++++console.warn('stuff');

++++//+Check+that+warn+was+not+called+(fail+on+warning)
++++expect(warn).not.toHaveBeenCalled();

++++//+Cleanup
++++warn.mockReset();
++++warn.mockRestore();
++});
});|code-block|syntax|javascript|2179926|entityMap|0|LINK|mutability|MUTABLE|url|http://facebook.github.io/jest/docs/en/jest-object.html#jestspyonobject-methodname^0|5|7|G|A|10|7|18|4|1J|6|G|A|0|0|5|6|G|4|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1D|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

I implemented this recently using <a href="http://facebook.github.io/jest/docs/en/jest-object.html#jestspyonobject-methodname" rel="nofollow noreferrer"><code>jest.spyOn</code></a> introduced in <code>v19.0.0</code> to mock the <code>warn</code> method of <code>console</code> (which is accesses via the <code>global</code> context / object).

Can then <code>expect</code> that the mocked <code>warn</code> was not called, as shown below.

<pre><code>describe('A function that does something', () =&gt; {
 it('Should not trigger a warning', () =&gt; {
 var warn = jest.spyOn(global.console, 'warn');

 // Do something that may trigger warning via `console.warn`
 doSomething();

 // ... i.e.
 console.warn('stuff');

 // Check that warn was not called (fail on warning)
 expect(warn).not.toHaveBeenCalled();

 // Cleanup
 warn.mockReset();
 warn.mockRestore();
 });
});
</code></pre>

blocks|key|273376|text|您可以使用这个简单的覆盖：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|273377|let+error+=+console.error

console.error+=+function+(message)+{
++error.apply(console,+arguments)+//+keep+default+behaviour
++throw+(message+instanceof+Error+?+message+:+new+Error(message))
}|code-block|syntax|javascript|273378|您可以使用Jest+setupFiles使其在所有测试中都可用。|273379|在package.json中：|offset|length|style|CODE|273380|"jest":+{
++++"setupFiles":+[
++++++"./tests/jest.overrides.js"
++++]
}|273381|然后将代码片段放入jest.overrides.js|273382|entityMap^0|0|0|0|1|C|0|0|9|H|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|6|7|X|8|@$K|Y|L|Z|M|N]]|9|@]|A|$]]|$1|O|3|P|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|11|8|@$K|12|L|13|M|N]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

You can use this simple override :

<pre><code>let error = console.error

console.error = function (message) {
 error.apply(console, arguments) // keep default behaviour
 throw (message instanceof Error ? message : new Error(message))
}
</code></pre>

You can make it available across all tests using Jest setupFiles.

In <code>package.json</code> : 

<pre><code>"jest": {
 "setupFiles": [
 "./tests/jest.overrides.js"
 ]
}
</code></pre>

Then put the snippet into <code>jest.overrides.js</code>

blocks|key|2186375|text|对于那些使用create-react-app而不想运行npm+run+eject的用户，可以在./src/setupTests.js中添加以下代码|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2186376|global.console.warn+=+(message)+=>+{
++throw+message
}

global.console.error+=+(message)+=>+{
++throw+message
}|code-block|syntax|javascript|2186377|现在，当消息传递到console.warn或console.error时，jest将失败。|2186378|create-react-app+Docs+-+Initializing+Test+Environment|2186379|entityMap|0|LINK|mutability|MUTABLE|url|https://facebook.github.io/create-react-app/docs/running-tests#initializing-test-environment^0|R|D|1B|J|0|0|9|C|M|D|0|0|1H|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|O|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

For those using create-react-app, not wanting to run <code>npm run eject</code>, you can add the following code to <code>./src/setupTests.js</code>:

<pre><code>global.console.warn = (message) =&gt; {
 throw message
}

global.console.error = (message) =&gt; {
 throw message
}
</code></pre>

Now, jest will fail when messages are passed to <code>console.warn</code> or <code>console.error</code>.

<a href="https://facebook.github.io/create-react-app/docs/running-tests#initializing-test-environment" rel="nofollow noreferrer">create-react-app Docs - Initializing Test Environment</a>

blocks|key|271860|text|我决定发布一个基于user1823021+answer的完整示例|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|271861|describe('#perform',+()+=>+{
++var+api
++//+the+global.fetch+is+set+to+jest.fn()+object+globally
++global.fetch+=+jest.fn()
++var+warn+=+jest.spyOn(global.console,+'warn');
++beforeEach(function()+{
++++//+before+every+test,+all+mocks+need+to+be+resetted
++++api+=+new+Api()
++++global.fetch.mockReset()
++++warn.mockReset()
++});

++it('triggers+an+console.warn+if+fetch+fails',+function()+{
++++//+In+this+test+fetch+mock+throws+an+error
++++global.fetch.mockImplementationOnce(()+=>+{
++++++throw+'error+triggered'
++++})
++++//+I+run+the+test
++++api.perform()
++++//+I+verify+that+the+warn+spy+has+been+triggered
++++expect(warn).toHaveBeenCalledTimes(1);
++++expect(warn).toBeCalledWith("api+call+failed+with+error:+",+"error+triggered")
++});

++it('calls+fetch+function',+function()+{
++++//+I+create+2+more+mock+objects+to+verify+the+fetch+parameters
++++const+url+=+jest.fn()
++++const+config+=+jest.fn()
++++api.url+=+url
++++api.config+=+config
++++//+I+run+the+test
++++api.perform()
++++//+I+verify+that+fetch+has+been+called+with+url+and+config+mocks
++++expect(global.fetch).toHaveBeenCalledTimes(1)
++++expect(global.fetch).toBeCalledWith(url,+config)
++++expect(warn).toHaveBeenCalledTimes(0)
++});
})|code-block|syntax|javascript|271862|我正在测试的#perform方法|style|CODE|271863|class+Api+{
++constructor(auth)+{
++++this._credentials+=+auth
++}

++perform+=+async+()+=>+{
++++try+{
++++++return+await+fetch(this.url,+this.config)
++++}+catch(error)+{
++++++console.warn('api+call+failed+with+error:+',+error)
++++}
++}
}|271864|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/46678632/7295772^0|9|I|0|0|0|6|8|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|11|8|@$A|12|B|13|K|L]]|9|@]|C|$]]|$1|M|3|N|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

I decided to post a full example based on <a href="https://stackoverflow.com/a/46678632/7295772">user1823021 answer</a>

<pre class="lang-js prettyprint-override"><code>describe('#perform', () =&gt; {
 var api
 // the global.fetch is set to jest.fn() object globally
 global.fetch = jest.fn()
 var warn = jest.spyOn(global.console, 'warn');
 beforeEach(function() {
 // before every test, all mocks need to be resetted
 api = new Api()
 global.fetch.mockReset()
 warn.mockReset()
 });

 it('triggers an console.warn if fetch fails', function() {
 // In this test fetch mock throws an error
 global.fetch.mockImplementationOnce(() =&gt; {
 throw 'error triggered'
 })
 // I run the test
 api.perform()
 // I verify that the warn spy has been triggered
 expect(warn).toHaveBeenCalledTimes(1);
 expect(warn).toBeCalledWith("api call failed with error: ", "error triggered")
 });

 it('calls fetch function', function() {
 // I create 2 more mock objects to verify the fetch parameters
 const url = jest.fn()
 const config = jest.fn()
 api.url = url
 api.config = config
 // I run the test
 api.perform()
 // I verify that fetch has been called with url and config mocks
 expect(global.fetch).toHaveBeenCalledTimes(1)
 expect(global.fetch).toBeCalledWith(url, config)
 expect(warn).toHaveBeenCalledTimes(0)
 });
})
</code></pre>

the <code>#perform</code> method I am testing

<pre class="lang-js prettyprint-override"><code>class Api {
 constructor(auth) {
 this._credentials = auth
 }

 perform = async () =&gt; {
 try {
 return await fetch(this.url, this.config)
 } catch(error) {
 console.warn('api call failed with error: ', error)
 }
 }
}
</code></pre>

blocks|key|271871|text|您可以在运行jest之前设置环境变量CI=true，这将导致它在出现警告和错误的情况下测试失败。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|271872|运行test文件夹中所有测试文件的示例：|271873|CI=true+jest+./test|code-block|syntax|javascript|271874|自动化的CI/CD管道，如Github操作，默认情况下将CI设置为true，这可能是单元测试在抛出警告时在本地机器上通过，但在管道中失败的原因之一。|271875|(这里是关于默认环境变量的Github操作文档：https://docs.github.com/en/actions/learn-github-actions/environment-variables#default-environment-variables)|271876|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.github.com/en/actions/learn-github-actions/environment-variables#default-environment-variables^0|6|4|I|7|0|2|4|0|0|S|2|X|4|0|O|2Z|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1C|8|@]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

You can set the environment variable <code>CI=true</code> before running <code>jest</code> which will cause it to fail tests on warnings in addition to errors.
Example which runs all test files in the <code>test</code> folder:
<pre class="lang-sh prettyprint-override"><code>CI=true jest ./test
</code></pre>
Automated CI/CD pipelines such as Github Actions set <code>CI</code> to <code>true</code> by default, which can be one reason why a unit test will pass on your local machine when warnings are thrown, but fail in the pipeline.
(Here is the Github Actions documentation on default environment variables: <a href="https://docs.github.com/en/actions/learn-github-actions/environment-variables#default-environment-variables" rel="nofollow noreferrer">https://docs.github.com/en/actions/learn-github-actions/environment-variables#default-environment-variables</a>)

blocks|key|5242734|text|有一个有用的npm包可以帮助你做到这一点：jest-fail-on-console。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5242735|它很容易配置。|5242736|安装：|5242737|npm+i+-D+jest-fail-on-console|code-block|syntax|javascript|5242738|配置：|5242739|在Jest的setupFilesAfterEnv选项中使用的文件中，添加以下代码：|5242740|import+failOnConsole+from+'jest-fail-on-console'

failOnConsole()

//+or+with+options:
failOnConsole({+shouldFailOnWarn:+false+})|5242741|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ricardo-ch/jest-fail-on-console|1|https://jestjs.io/docs/configuration#setupfilesafterenv-array^0|L|K|0|0|0|0|0|0|6|I|1|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|18|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|Q|3|R|5|J|7|1E|8|@]|9|@]|C|$K|L]]|$1|S|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]]]

There is a useful npm package that helps you to achieve that: <a href="https://github.com/ricardo-ch/jest-fail-on-console" rel="nofollow noreferrer">jest-fail-on-console</a>
It's easily configurable.
<h4>Install:</h4>
<pre><code>npm i -D jest-fail-on-console
</code></pre>
<h4>Configure:</h4>
In a file used in the <a href="https://jestjs.io/docs/configuration#setupfilesafterenv-array" rel="nofollow noreferrer">setupFilesAfterEnv</a> option of Jest, add this code:
<pre><code>import failOnConsole from 'jest-fail-on-console'

failOnConsole()

// or with options:
failOnConsole({ shouldFailOnWarn: false })
</code></pre>

How do I configure jest tests to fail on warnings?

<pre><code>console.warn('stuff');
// fail test
</code></pre>

Is there a jest config that will fail tests on console.warn?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

如何将jest测试配置为在出现警告时失败？console.warn('stuff');// fail test

问有没有在console.warn上测试失败的jest配置？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有在console.warn上测试失败的jest配置？EN