Automated testing of Lightning Web Components?
up vote
5
down vote
favorite
Personally, I struggled to get value out of the Lightning Testing Service and felt it was very limited compared to e.g. Angular Testing. Working for an ISV, automated testing is key to keeping components working for both old and new customers.
Does anyone have information about testability of the Lightning Web Components?
unit-test lightning-web-components
add a comment |
up vote
5
down vote
favorite
Personally, I struggled to get value out of the Lightning Testing Service and felt it was very limited compared to e.g. Angular Testing. Working for an ISV, automated testing is key to keeping components working for both old and new customers.
Does anyone have information about testability of the Lightning Web Components?
unit-test lightning-web-components
add a comment |
up vote
5
down vote
favorite
up vote
5
down vote
favorite
Personally, I struggled to get value out of the Lightning Testing Service and felt it was very limited compared to e.g. Angular Testing. Working for an ISV, automated testing is key to keeping components working for both old and new customers.
Does anyone have information about testability of the Lightning Web Components?
unit-test lightning-web-components
Personally, I struggled to get value out of the Lightning Testing Service and felt it was very limited compared to e.g. Angular Testing. Working for an ISV, automated testing is key to keeping components working for both old and new customers.
Does anyone have information about testability of the Lightning Web Components?
unit-test lightning-web-components
unit-test lightning-web-components
asked 16 hours ago
Keith C
93.8k1088199
93.8k1088199
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
4
down vote
accepted
Testing for LWC is implemented in Jest. These can be run locally to your org, or even enabled to run in "watch" mode to give you instant feedback while you code.
From the docs, LWC testing enables you to
- Test a component in isolation
- Test a component's public API
- Test basic user interaction with a component
- Verify the DOM output of a component
- Verify that events fire when expected
There are a number of tests implemented in the e-bikes sample app in the sample app gallery.
You can also read about it in the developer guide. Until it is updated for prerelease, you'll have to login to a pre-release org, and then go to the url:
https://[your.org.domain]/docs/component-library/documentation/lwc/lwc.testing
Thanks Peter. Interesting to see the package.json there too.
– Keith C
14 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fsalesforce.stackexchange.com%2fquestions%2f242613%2fautomated-testing-of-lightning-web-components%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
Testing for LWC is implemented in Jest. These can be run locally to your org, or even enabled to run in "watch" mode to give you instant feedback while you code.
From the docs, LWC testing enables you to
- Test a component in isolation
- Test a component's public API
- Test basic user interaction with a component
- Verify the DOM output of a component
- Verify that events fire when expected
There are a number of tests implemented in the e-bikes sample app in the sample app gallery.
You can also read about it in the developer guide. Until it is updated for prerelease, you'll have to login to a pre-release org, and then go to the url:
https://[your.org.domain]/docs/component-library/documentation/lwc/lwc.testing
Thanks Peter. Interesting to see the package.json there too.
– Keith C
14 hours ago
add a comment |
up vote
4
down vote
accepted
Testing for LWC is implemented in Jest. These can be run locally to your org, or even enabled to run in "watch" mode to give you instant feedback while you code.
From the docs, LWC testing enables you to
- Test a component in isolation
- Test a component's public API
- Test basic user interaction with a component
- Verify the DOM output of a component
- Verify that events fire when expected
There are a number of tests implemented in the e-bikes sample app in the sample app gallery.
You can also read about it in the developer guide. Until it is updated for prerelease, you'll have to login to a pre-release org, and then go to the url:
https://[your.org.domain]/docs/component-library/documentation/lwc/lwc.testing
Thanks Peter. Interesting to see the package.json there too.
– Keith C
14 hours ago
add a comment |
up vote
4
down vote
accepted
up vote
4
down vote
accepted
Testing for LWC is implemented in Jest. These can be run locally to your org, or even enabled to run in "watch" mode to give you instant feedback while you code.
From the docs, LWC testing enables you to
- Test a component in isolation
- Test a component's public API
- Test basic user interaction with a component
- Verify the DOM output of a component
- Verify that events fire when expected
There are a number of tests implemented in the e-bikes sample app in the sample app gallery.
You can also read about it in the developer guide. Until it is updated for prerelease, you'll have to login to a pre-release org, and then go to the url:
https://[your.org.domain]/docs/component-library/documentation/lwc/lwc.testing
Testing for LWC is implemented in Jest. These can be run locally to your org, or even enabled to run in "watch" mode to give you instant feedback while you code.
From the docs, LWC testing enables you to
- Test a component in isolation
- Test a component's public API
- Test basic user interaction with a component
- Verify the DOM output of a component
- Verify that events fire when expected
There are a number of tests implemented in the e-bikes sample app in the sample app gallery.
You can also read about it in the developer guide. Until it is updated for prerelease, you'll have to login to a pre-release org, and then go to the url:
https://[your.org.domain]/docs/component-library/documentation/lwc/lwc.testing
answered 16 hours ago
pchittum
14.4k33477
14.4k33477
Thanks Peter. Interesting to see the package.json there too.
– Keith C
14 hours ago
add a comment |
Thanks Peter. Interesting to see the package.json there too.
– Keith C
14 hours ago
Thanks Peter. Interesting to see the package.json there too.
– Keith C
14 hours ago
Thanks Peter. Interesting to see the package.json there too.
– Keith C
14 hours ago
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- 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.
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%2fsalesforce.stackexchange.com%2fquestions%2f242613%2fautomated-testing-of-lightning-web-components%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