Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Screenshot path does not corresponds to the spec path

See original GitHub issue

Current behavior

I have two spec files, each contains a simple test case where I take a screenshot with cy.screenshot(). Both screenshots will be saved directly under scressnshots directory.

Desired behavior

Screenshot from cypress/e2e/deep/deep-example.cy.js to be saved under cypress/screenshots/deep/deep example --passes.png

Test code to reproduce

https://github.com/odai-alali/cypress-screenshot-issue

Cypress Version

10.0.3

Other

No response

Issue Analytics

State:
Created a year ago
Comments:11 (2 by maintainers)

Top GitHub Comments

8reactions

shtiefcommented, Jun 22, 2022

Hello, I understand the idea to get rid of the ancestry folders. But it comes with a big disadvantage, that you can’t be sure the screenshots are in the same place. It depends on which e2e tests you are executing. You can run ALL tests but also only ONE specific test. The directory for the generated files can be different then. This is annoying, especially when you want to test with visual regression and compare snapshots. I will try the ‘after:screenshot’ solution, but I would prefer a configuration to KEEP the directory structure that is defined in the specs directory.

2reactions

marktnoonancommented, Jun 7, 2022

Hi, thanks for reporting this. I believe this is an unavoidable side effect of the change in Cypress 10 from setting an integrationFolder for specs to setting a specPattern . From the changelog for 10.0.0:

Generated screenshots and videos will still be created inside their respective folders (screenshotsFolder, videosFolder). However, the paths of generated files inside those folders will be stripped of any common ancestor paths shared between spec files found by the specPattern option and may no longer be deterministic. Addressed in #19319.