Properly testing components passed in as props
In the example below I have a component named <BigList /> which accepts a component as props called toggleComponent. I then pass down that component into the render method, this is setup so I can have multiple different types of toggle components. The problem I'm running into is how to properly test the prop methods on the component I'm passing into <BigList />. My code coverage decreases because of it and I'm not really sure how I can mock the onChange handler here.
<BigList
title="Some Props"
toggleComponent={
<Checkboxt
onChange={() =>
someMethod()
}
/>
}
>
<Checkbox
onChange={() =>
anotherMethod()
}
/>
</BigList>
Using Enzyme and Sinon I've attempted to do something like this, but to no avail. I end up with errors relating to the props being inaccessible. I just want to make sure that the onChange handler gets fired on a change event for the toggleComponent props.
const component = shallow(
<ParentComponent />
);
const event = {target: {name: "event", value: "event value"}};
const toggleComponent = component.find('BigList').at(1).props().toggleComponent;
toggleComponent.props().onChange = stub();
toggleComponent.simulate('change', event);
t.equal(
toggleComponent.onChange.callCount,
1,
'Should call onChange'
);
reactjs sinon enzyme
asked Nov 20 '18 at 16:52
James IvesJames Ives
1,3881332
add a comment |
In the example below I have a component named <BigList /> which accepts a component as props called toggleComponent. I then pass down that component into the render method, this is setup so I can have multiple different types of toggle components. The problem I'm running into is how to properly test the prop methods on the component I'm passing into <BigList />. My code coverage decreases because of it and I'm not really sure how I can mock the onChange handler here.
<BigList
title="Some Props"
toggleComponent={
<Checkboxt
onChange={() =>
someMethod()
}
/>
}
>
<Checkbox
onChange={() =>
anotherMethod()
}
/>
</BigList>
Using Enzyme and Sinon I've attempted to do something like this, but to no avail. I end up with errors relating to the props being inaccessible. I just want to make sure that the onChange handler gets fired on a change event for the toggleComponent props.
const component = shallow(
<ParentComponent />
);
const event = {target: {name: "event", value: "event value"}};
const toggleComponent = component.find('BigList').at(1).props().toggleComponent;
toggleComponent.props().onChange = stub();
toggleComponent.simulate('change', event);
t.equal(
toggleComponent.onChange.callCount,
1,
'Should call onChange'
);
reactjs sinon enzyme
asked Nov 20 '18 at 16:52
James IvesJames Ives
1,3881332
add a comment |
In the example below I have a component named <BigList /> which accepts a component as props called toggleComponent. I then pass down that component into the render method, this is setup so I can have multiple different types of toggle components. The problem I'm running into is how to properly test the prop methods on the component I'm passing into <BigList />. My code coverage decreases because of it and I'm not really sure how I can mock the onChange handler here.
<BigList
title="Some Props"
toggleComponent={
<Checkboxt
onChange={() =>
someMethod()
}
/>
}
>
<Checkbox
onChange={() =>
anotherMethod()
}
/>
</BigList>
Using Enzyme and Sinon I've attempted to do something like this, but to no avail. I end up with errors relating to the props being inaccessible. I just want to make sure that the onChange handler gets fired on a change event for the toggleComponent props.
const component = shallow(
<ParentComponent />
);
const event = {target: {name: "event", value: "event value"}};
const toggleComponent = component.find('BigList').at(1).props().toggleComponent;
toggleComponent.props().onChange = stub();
toggleComponent.simulate('change', event);
t.equal(
toggleComponent.onChange.callCount,
1,
'Should call onChange'
);
reactjs sinon enzyme
asked Nov 20 '18 at 16:52
James IvesJames Ives
1,3881332
In the example below I have a component named <BigList /> which accepts a component as props called toggleComponent. I then pass down that component into the render method, this is setup so I can have multiple different types of toggle components. The problem I'm running into is how to properly test the prop methods on the component I'm passing into <BigList />. My code coverage decreases because of it and I'm not really sure how I can mock the onChange handler here.
<BigList
title="Some Props"
toggleComponent={
<Checkboxt
onChange={() =>
someMethod()
}
/>
}
>
<Checkbox
onChange={() =>
anotherMethod()
}
/>
</BigList>
Using Enzyme and Sinon I've attempted to do something like this, but to no avail. I end up with errors relating to the props being inaccessible. I just want to make sure that the onChange handler gets fired on a change event for the toggleComponent props.
const component = shallow(
<ParentComponent />
);
const event = {target: {name: "event", value: "event value"}};
const toggleComponent = component.find('BigList').at(1).props().toggleComponent;
toggleComponent.props().onChange = stub();
toggleComponent.simulate('change', event);
t.equal(
toggleComponent.onChange.callCount,
1,
'Should call onChange'
);
reactjs sinon enzyme
reactjs sinon enzyme
asked Nov 20 '18 at 16:52
James IvesJames Ives
1,3881332
asked Nov 20 '18 at 16:52
James IvesJames Ives
1,3881332
asked Nov 20 '18 at 16:52
James IvesJames Ives
1,3881332
asked Nov 20 '18 at 16:52
James IvesJames Ives
1,3881332
asked Nov 20 '18 at 16:52
James IvesJames Ives
1,3881332
1,3881332
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%2f53397815%2fproperly-testing-components-passed-in-as-props%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%2f53397815%2fproperly-testing-components-passed-in-as-props%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
