Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR running force:lightning:lwc:test:create: No corresponding HTML file found #1254

Closed
AllanOricil opened this issue Oct 27, 2021 · 5 comments · Fixed by salesforcecli/plugin-lwc-test#39
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. tracked elsewhere The work is being tracked internally by Salesforce

Comments

@AllanOricil
Copy link

AllanOricil commented Oct 27, 2021

Summary

I have a component which does not have .html.
It is a component that extends a Base/Parent component that takes care of the rendering.

Steps To Reproduce:

1 - Create a Base component
2 - Create a Child component that extends the base
3 - Delete the child's html file
4 - run sfdx force:lightning:lwc:test:create or use the vscode command SFDX: Create Lightning Web Component Test to create a test spec for your component
5 - verify you get this error message: ERROR running force:lightning:lwc:test:create: No corresponding HTML file found for
6 - create .html for your component
7 - repeat step 4
8 - verify that the test spec was created and no error message was displayed

Expected result

sfdx force:lightning:lwc:test:create should not care about if there is or not a .html file.

Actual result

sfdx force:lightning:lwc:test:create does not allow us to create test spec because the component does not have .html

System Information

sfdx-cli/7.122.1 win32-x64 node-v14.18.0

@AllanOricil AllanOricil added the investigating We're actively investigating this issue label Oct 27, 2021
@github-actions
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@WillieRuemmele WillieRuemmele added the bug Issue or pull request that identifies or fixes a bug label Oct 27, 2021
@uip-robot-zz
Copy link

This issue has been linked to a new work item: W-10093476

@WillieRuemmele WillieRuemmele added the owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. label Oct 27, 2021
@github-actions
Copy link

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

@AllanOricil
Copy link
Author

@WillieRuemmele why it was labeled with "owned by other team" if it is a sfdx bug?

@WillieRuemmele
Copy link
Member

Hi @AllanOricil the bug has been assigned to the team that owns that command. SFDX is comprised of many teams

@WillieRuemmele WillieRuemmele added the tracked elsewhere The work is being tracked internally by Salesforce label Nov 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. tracked elsewhere The work is being tracked internally by Salesforce
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants