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

Cannot print error details on tests with .only #6744

Closed
kuceb opened this issue Mar 16, 2020 · 3 comments · Fixed by Flygsand/site#83
Closed

Cannot print error details on tests with .only #6744

kuceb opened this issue Mar 16, 2020 · 3 comments · Fixed by Flygsand/site#83
Labels
type: regression A bug that didn't appear until a specific Cy version release v4.0.0 🐛 Issue present since 4.0.0

Comments

@kuceb
Copy link
Contributor

kuceb commented Mar 16, 2020

Bug (regression - 4.0.0)

In open mode, if you put an .only on a failing test
and click on the error,

the error is not printed to console;
instead it fails with

No error found for test id [testid]

image

this is due to changes with handling mocha .only tests made for 4.0

@kuceb kuceb added v4.0.0 🐛 Issue present since 4.0.0 type: regression A bug that didn't appear until a specific Cy version release labels Mar 16, 2020
@kuceb kuceb self-assigned this Mar 16, 2020
@jennifer-shehane
Copy link
Member

jennifer-shehane commented Mar 17, 2020

I would not really broadly apply this to any failing test with a .only. I can reproduce from example below:

it.only('failing spec', () => {
  throw(new Error())
})

But many other failing spec examples work fine with logging on click of the error, so it's something specific to the way the test fails.

This is fixed from #6724 though, which has put a lot of tests and thought around these situations.

Screen Shot 2020-03-17 at 1 36 36 PM

@bkucera Can you double check that your failing example logs correctly in develop branch now?

The code for this is done in #6724, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

@kuceb
Copy link
Contributor Author

kuceb commented Mar 17, 2020

it does appear to be fixed now, great

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Mar 30, 2020

Released in 4.3.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v4.3.0, please open a new issue.

@cypress-bot cypress-bot bot locked as resolved and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: regression A bug that didn't appear until a specific Cy version release v4.0.0 🐛 Issue present since 4.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants