Specs named with spaces have malformed stacks and no code frames for errors

[chrisbreiding]

Current behavior:

If a test fails or there is an error in a spec that has a space in its name, the following issues occur:

• The error stack does not point to the user code as it should
  • This also makes it impossible to open in IDE
• The stack line has undefined:NaN instead of <line>:<column> (edit (7/9/20): only happens in develop)
• The code frame does not display

Desired behavior:

Errors should display properly regardless of file naming conventions.

Test code to reproduce

• Create a spec file with a space in its name (e.g. cypress/integration/with space_spec.js)
• Make it fail

it('fails', () => {
  expect('actual').to.equal('expected')
})

Versions

Cypress 4.6.0+

[jennifer-shehane]

@chrisbreiding I'm not able to reproduce this exactly. The stack trace still isn't pointing to my spec file, but I don't see the undefined like you do. What am I missing 🤔

4.5.0

4.6.0+

[chrisbreiding]

The difference is I was running the develop branch and not production Cypress. I suppose the undefined part wouldn't really be seen by users, but they'd see the other issues.

[cypress-bot]

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

[bahmutov]

Released in v6.2.0