How prevent error message when catching expected exception in test?
I have some code that I expect to throw an exception in a unit test (using Jest). I'm able to get the test to pass/fail as it should, but I get a nasty error message in my Jest watch. That message makes me think something bad happened, when in reality, it was the expected exception.
To explain why: the production code (not shown) makes a request using fetch
. I have a previous test that mocks fetch out, and this test was to prove that I reset the state correctly.
Test code:
it('should not keep on mocking fetch', (done) => {
try {
wrapper.find('button#submit').simulate('click');
done.fail("Expected fetch to not be defined");
} catch (error) {
done();
}
});
How can I get rid of the error message for this test without affecting other tests?
I've tried reassigning global.console.error
, which works, but that would be very bad if I forgot to reassign the real global.console.error
back at the end of the test.
I've also tried using expect(...).toThrow()
, but I still get the nasty error message.
javascript jestjs
add a comment |
I have some code that I expect to throw an exception in a unit test (using Jest). I'm able to get the test to pass/fail as it should, but I get a nasty error message in my Jest watch. That message makes me think something bad happened, when in reality, it was the expected exception.
To explain why: the production code (not shown) makes a request using fetch
. I have a previous test that mocks fetch out, and this test was to prove that I reset the state correctly.
Test code:
it('should not keep on mocking fetch', (done) => {
try {
wrapper.find('button#submit').simulate('click');
done.fail("Expected fetch to not be defined");
} catch (error) {
done();
}
});
How can I get rid of the error message for this test without affecting other tests?
I've tried reassigning global.console.error
, which works, but that would be very bad if I forgot to reassign the real global.console.error
back at the end of the test.
I've also tried using expect(...).toThrow()
, but I still get the nasty error message.
javascript jestjs
add a comment |
I have some code that I expect to throw an exception in a unit test (using Jest). I'm able to get the test to pass/fail as it should, but I get a nasty error message in my Jest watch. That message makes me think something bad happened, when in reality, it was the expected exception.
To explain why: the production code (not shown) makes a request using fetch
. I have a previous test that mocks fetch out, and this test was to prove that I reset the state correctly.
Test code:
it('should not keep on mocking fetch', (done) => {
try {
wrapper.find('button#submit').simulate('click');
done.fail("Expected fetch to not be defined");
} catch (error) {
done();
}
});
How can I get rid of the error message for this test without affecting other tests?
I've tried reassigning global.console.error
, which works, but that would be very bad if I forgot to reassign the real global.console.error
back at the end of the test.
I've also tried using expect(...).toThrow()
, but I still get the nasty error message.
javascript jestjs
I have some code that I expect to throw an exception in a unit test (using Jest). I'm able to get the test to pass/fail as it should, but I get a nasty error message in my Jest watch. That message makes me think something bad happened, when in reality, it was the expected exception.
To explain why: the production code (not shown) makes a request using fetch
. I have a previous test that mocks fetch out, and this test was to prove that I reset the state correctly.
Test code:
it('should not keep on mocking fetch', (done) => {
try {
wrapper.find('button#submit').simulate('click');
done.fail("Expected fetch to not be defined");
} catch (error) {
done();
}
});
How can I get rid of the error message for this test without affecting other tests?
I've tried reassigning global.console.error
, which works, but that would be very bad if I forgot to reassign the real global.console.error
back at the end of the test.
I've also tried using expect(...).toThrow()
, but I still get the nasty error message.
javascript jestjs
javascript jestjs
asked Jan 2 at 3:37
Anthony ElliottAnthony Elliott
1,94922133
1,94922133
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54000941%2fhow-prevent-error-message-when-catching-expected-exception-in-test%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54000941%2fhow-prevent-error-message-when-catching-expected-exception-in-test%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown