jest enzyme | testing Promise in component function passes but throws an error











up vote
0
down vote

favorite












I have a container where I have a function which makes an API request using fetch:



updateBooks = books => this.setState({ books });

getBooks = keyword => fetch(`${googleBooksSearchAPI}${keyword}`)
.then(response => response.json())
.then(myJson => this.updateBooks(myJson.items))
.catch(error => console.log('error', error));


I'm trying to write tests for it using fetch-mock:



it('getBooks works', () => {
const wrapper = shallow(<BookContainer />);
const mockData = { items: bookListObj };
fetchMock.get(googleBooksSearchAPI, mockData);

wrapper.instance().getBooks('dun');
expect(wrapper.state().books).toEqual(bookListObj);

fetchMock.restore();
});


All tests show as passed, but still, I can see this error:



console.log app/components/BookContainer.js:20
error FetchError {
name: 'FetchError',
message: 'invalid json response body at undefined reason: Unexpected end of JSON input',
type: 'invalid-json' }


if I remove catch from fetch it shows the message like this:



(node:5094) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at undefined reason: Unexpected end of JSON input
(node:5094) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:5094) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.


How to remove it?










share|improve this question






















  • What is fetchMock? Where is getBooks called? Please, provide stackoverflow.com/help/mcve
    – estus
    Nov 11 at 18:20










  • fetchMock is, as written, - fetch-mock. getBooks is called in componentDidUpdate, I don't think it is important from this test point of view. I'm testing just this function
    – Kania
    Nov 12 at 2:12






  • 1




    MCVE is required by SO rules to avoid long negotiations about what should be posted and what shouldn't. I suppose the problem here is that getBooks is called before fetch is mocked or it's not mocked for some other reason, but I cannot confirm this without seeing the component.
    – estus
    Nov 12 at 6:52










  • Perhaps, you need to apply keyword to fetch mock fetchMock.get(${googleBooksSearchAPI}dyn, mockData)
    – Alex
    Nov 13 at 0:07

















up vote
0
down vote

favorite












I have a container where I have a function which makes an API request using fetch:



updateBooks = books => this.setState({ books });

getBooks = keyword => fetch(`${googleBooksSearchAPI}${keyword}`)
.then(response => response.json())
.then(myJson => this.updateBooks(myJson.items))
.catch(error => console.log('error', error));


I'm trying to write tests for it using fetch-mock:



it('getBooks works', () => {
const wrapper = shallow(<BookContainer />);
const mockData = { items: bookListObj };
fetchMock.get(googleBooksSearchAPI, mockData);

wrapper.instance().getBooks('dun');
expect(wrapper.state().books).toEqual(bookListObj);

fetchMock.restore();
});


All tests show as passed, but still, I can see this error:



console.log app/components/BookContainer.js:20
error FetchError {
name: 'FetchError',
message: 'invalid json response body at undefined reason: Unexpected end of JSON input',
type: 'invalid-json' }


if I remove catch from fetch it shows the message like this:



(node:5094) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at undefined reason: Unexpected end of JSON input
(node:5094) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:5094) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.


How to remove it?










share|improve this question






















  • What is fetchMock? Where is getBooks called? Please, provide stackoverflow.com/help/mcve
    – estus
    Nov 11 at 18:20










  • fetchMock is, as written, - fetch-mock. getBooks is called in componentDidUpdate, I don't think it is important from this test point of view. I'm testing just this function
    – Kania
    Nov 12 at 2:12






  • 1




    MCVE is required by SO rules to avoid long negotiations about what should be posted and what shouldn't. I suppose the problem here is that getBooks is called before fetch is mocked or it's not mocked for some other reason, but I cannot confirm this without seeing the component.
    – estus
    Nov 12 at 6:52










  • Perhaps, you need to apply keyword to fetch mock fetchMock.get(${googleBooksSearchAPI}dyn, mockData)
    – Alex
    Nov 13 at 0:07















up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a container where I have a function which makes an API request using fetch:



updateBooks = books => this.setState({ books });

getBooks = keyword => fetch(`${googleBooksSearchAPI}${keyword}`)
.then(response => response.json())
.then(myJson => this.updateBooks(myJson.items))
.catch(error => console.log('error', error));


I'm trying to write tests for it using fetch-mock:



it('getBooks works', () => {
const wrapper = shallow(<BookContainer />);
const mockData = { items: bookListObj };
fetchMock.get(googleBooksSearchAPI, mockData);

wrapper.instance().getBooks('dun');
expect(wrapper.state().books).toEqual(bookListObj);

fetchMock.restore();
});


All tests show as passed, but still, I can see this error:



console.log app/components/BookContainer.js:20
error FetchError {
name: 'FetchError',
message: 'invalid json response body at undefined reason: Unexpected end of JSON input',
type: 'invalid-json' }


if I remove catch from fetch it shows the message like this:



(node:5094) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at undefined reason: Unexpected end of JSON input
(node:5094) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:5094) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.


How to remove it?










share|improve this question













I have a container where I have a function which makes an API request using fetch:



updateBooks = books => this.setState({ books });

getBooks = keyword => fetch(`${googleBooksSearchAPI}${keyword}`)
.then(response => response.json())
.then(myJson => this.updateBooks(myJson.items))
.catch(error => console.log('error', error));


I'm trying to write tests for it using fetch-mock:



it('getBooks works', () => {
const wrapper = shallow(<BookContainer />);
const mockData = { items: bookListObj };
fetchMock.get(googleBooksSearchAPI, mockData);

wrapper.instance().getBooks('dun');
expect(wrapper.state().books).toEqual(bookListObj);

fetchMock.restore();
});


All tests show as passed, but still, I can see this error:



console.log app/components/BookContainer.js:20
error FetchError {
name: 'FetchError',
message: 'invalid json response body at undefined reason: Unexpected end of JSON input',
type: 'invalid-json' }


if I remove catch from fetch it shows the message like this:



(node:5094) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at undefined reason: Unexpected end of JSON input
(node:5094) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:5094) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.


How to remove it?







reactjs promise jestjs






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 11 at 17:58









Kania

1,04611828




1,04611828












  • What is fetchMock? Where is getBooks called? Please, provide stackoverflow.com/help/mcve
    – estus
    Nov 11 at 18:20










  • fetchMock is, as written, - fetch-mock. getBooks is called in componentDidUpdate, I don't think it is important from this test point of view. I'm testing just this function
    – Kania
    Nov 12 at 2:12






  • 1




    MCVE is required by SO rules to avoid long negotiations about what should be posted and what shouldn't. I suppose the problem here is that getBooks is called before fetch is mocked or it's not mocked for some other reason, but I cannot confirm this without seeing the component.
    – estus
    Nov 12 at 6:52










  • Perhaps, you need to apply keyword to fetch mock fetchMock.get(${googleBooksSearchAPI}dyn, mockData)
    – Alex
    Nov 13 at 0:07




















  • What is fetchMock? Where is getBooks called? Please, provide stackoverflow.com/help/mcve
    – estus
    Nov 11 at 18:20










  • fetchMock is, as written, - fetch-mock. getBooks is called in componentDidUpdate, I don't think it is important from this test point of view. I'm testing just this function
    – Kania
    Nov 12 at 2:12






  • 1




    MCVE is required by SO rules to avoid long negotiations about what should be posted and what shouldn't. I suppose the problem here is that getBooks is called before fetch is mocked or it's not mocked for some other reason, but I cannot confirm this without seeing the component.
    – estus
    Nov 12 at 6:52










  • Perhaps, you need to apply keyword to fetch mock fetchMock.get(${googleBooksSearchAPI}dyn, mockData)
    – Alex
    Nov 13 at 0:07


















What is fetchMock? Where is getBooks called? Please, provide stackoverflow.com/help/mcve
– estus
Nov 11 at 18:20




What is fetchMock? Where is getBooks called? Please, provide stackoverflow.com/help/mcve
– estus
Nov 11 at 18:20












fetchMock is, as written, - fetch-mock. getBooks is called in componentDidUpdate, I don't think it is important from this test point of view. I'm testing just this function
– Kania
Nov 12 at 2:12




fetchMock is, as written, - fetch-mock. getBooks is called in componentDidUpdate, I don't think it is important from this test point of view. I'm testing just this function
– Kania
Nov 12 at 2:12




1




1




MCVE is required by SO rules to avoid long negotiations about what should be posted and what shouldn't. I suppose the problem here is that getBooks is called before fetch is mocked or it's not mocked for some other reason, but I cannot confirm this without seeing the component.
– estus
Nov 12 at 6:52




MCVE is required by SO rules to avoid long negotiations about what should be posted and what shouldn't. I suppose the problem here is that getBooks is called before fetch is mocked or it's not mocked for some other reason, but I cannot confirm this without seeing the component.
– estus
Nov 12 at 6:52












Perhaps, you need to apply keyword to fetch mock fetchMock.get(${googleBooksSearchAPI}dyn, mockData)
– Alex
Nov 13 at 0:07






Perhaps, you need to apply keyword to fetch mock fetchMock.get(${googleBooksSearchAPI}dyn, mockData)
– Alex
Nov 13 at 0:07



















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',
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53251580%2fjest-enzyme-testing-promise-in-component-function-passes-but-throws-an-error%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53251580%2fjest-enzyme-testing-promise-in-component-function-passes-but-throws-an-error%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Florida Star v. B. J. F.

Danny Elfman

Retrieve a Users Dashboard in Tumblr with R and TumblR. Oauth Issues