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

Custom commands don't show up as a step in the UI #1729

Closed
amitzur opened this issue May 17, 2018 · 2 comments
Closed

Custom commands don't show up as a step in the UI #1729

amitzur opened this issue May 17, 2018 · 2 comments

Comments

@amitzur
Copy link

amitzur commented May 17, 2018

For custom commands, it makes sense that their name will show up as a step in the script.
Right now they don't, and it seems like the only workaround is to use cy.log() inside the command, but that's not a great experience.

screen shot 2018-05-17 at 10 30 40 am

@jennifer-shehane
Copy link
Member

You can control how a custom command displays in the Command Log, see this note in the docs: https://on.cypress.io/custom-commands#Command-Logging

Granted, the Cypress.Log docs need a lot of improvements and I can see how this is not obvious.

The simplest use case should be to add this inside your custom command:

Cypress.log({
  name: 'MySpecialCommand'
})

@amitzur
Copy link
Author

amitzur commented May 18, 2018

10x!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants