Component testing "Open in IDE" link broken

[sync-by-unito]

Mirror of #17272

Current behavior

When trying to open my test on the right line, using the "Open in IDE" link, nothing happens.

This is what I see:

!125167656-488ccc00-e167-11eb-917f-eca13426d666.mov|width=100%!

NOTE: It does not depend on Webpack or Vite, both link fail the same way.

Desired behavior

I would like to be taken to my test on the correct line

Test code to reproduce

• checkout https://github.com/elevatebart/calc-vite
• open the spec named Container.tsx
• hover on the test
• Click on the Open in IDE link
• nothing happens

Versions

Cypress 9.1.1

┆Issue is synchronized with this Jira Bug by Unito
┆Attachments: 125167656-488ccc00-e167-11eb-917f-eca13426d666.mov
┆author: Bart Ledoux
┆epic: CT Post Unification Release
┆friendlyId: UNIFY-655
┆priority: Low
┆sprint: Unification Release Backlog
┆taskType: Bug

[sync-by-unito]

➤ Mark Noonan commented:

Bart Ledoux I think our resolution is to remove this button for now right?

[sync-by-unito]

➤ Bart Ledoux commented:

It is sad but we don’t have a choice.

The option would probably be more useful in ct than in e2e.

[sync-by-unito]

➤ Zach Bloomquist commented:

This is also broken in e2e with the unified runner. Why is there not a choice for removing it?

[sync-by-unito]

➤ Bart Ledoux commented:

Zach Bloomquist solution is to remove it in 10.0 without option to turn it on

[sync-by-unito]

➤ Zach Bloomquist commented:

Bart Ledoux Is there a technical blocker? You said “we don’t have a choice”, I’m not sure what this is referring to, this worked before right?

[sync-by-unito]

➤ Bart Ledoux commented:

It is using a big ol’ hack from how chromium presents stack traces in iframes. Unfortunately this option is not really available in CT as we are missing one context frame for the driver.

[sync-by-unito]

➤ Bart Ledoux commented:

The way I would implement this is :

• in open mode
• use babel to parse the current spec file
• add a parameter to each describe/it/context to give cypress the exact line and column where to focus
• Use this context parameter instead of the stack trace to open the ide

[sync-by-unito]

➤ Bart Ledoux commented:

For reference here is the line where I believe this links target is calculated in 9.0

https://github.com/cypress-io/cypress/blob/develop/packages/driver/src/cypress/mocha.ts#L361 ( https://github.com/cypress-io/cypress/blob/develop/packages/driver/src/cypress/mocha.ts#L361|smart-link )

[sync-by-unito]

➤ Mark Noonan commented:

Chris Baus talk with Brian, he may have a better way of doing this so we can keep it

[sync-by-unito]

➤ Chris Baus commented:

Chris Baus High impact of unknown scope

[sync-by-unito]

➤ Brian Mann commented:

I’m working on this FYI

[sync-by-unito]

➤ Chris Baus commented:

Brian Mann Is this still being worked on? It has been in progress for awhile. We are trying to clear out everything in progress

[sync-by-unito]

➤ Lachlan Miller commented:

I’d like to pick this up, I’ll see where Brian Mann is at.

[sync-by-unito]

➤ Brian Mann commented:

Lachlan Miller this is due to CT stack traces - its the same issue and is referenced above. Once stack traces works, this will automatically work. It’s just another “issue” cropping up from the root cause.

[sync-by-unito]

➤ Brian Mann commented:

Before anyone picks up this issue - please come talk to me. The root/parent issue is CT Stack Traces - once that is fixed all the subsequent issues go away.

[sync-by-unito]

➤ Lachlan Miller commented:

Right, gotcha Brian Mann . For some reason I thought this was just about going to the spec, not the specific line, since the ticket said “I would like to be taken to my test on the first line”. I’m going to change this to the “correct line”.

[rmmanseau]

the open in IDE button is still broken in 10.10.0 for me, is this issue being prioritized? Accurate stack traces & the ability to jump to the failing assert are pretty essential features for a testing framework

[lmiller1990]

@rmmanseau This is working for me now -- I think fixed in #23916. I tested and this works on all my machines (windows/macos/linux) on Cy 11 and 12.

If you are still having an issue, it might be worth creating a new one and sharing

1. cypress version
2. os
3. anything else relevant

Thanks!