Proposal: Nest screenshot path based on spec path by default
See original GitHub issueInstead of saving screenshots all directly in the screenshots directory, nest them based on where the spec file is relative to the integration directory. So if running
cypress/integration/app/login/user_spec.js
a screenshot will be saved as
cypress/screenshots/app/login/user_spec.js -- login -- users -- can log in.png
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Set screenshot path from default project location to different ...
Show activity on this post. There's quite a few ways to change the screenshots default directory. One way is to set the screenshot_root_ ......
Read more >How to Change Where Screenshots are Saved on a Mac
The Command + Shift + 5 method will open the full-screen capture panel on your Mac. This defaults to a large capture window...
Read more >screenshot - Cypress Documentation
The screenshot will be stored in the cypress/screenshots folder by default. You can change the directory where screenshots are saved in the Cypress ......
Read more >Blog - Layouts RFC | Next.js
We plan to introduce defaults and conventions that allow you to easily adopt ... A route is a single path of nested folders,...
Read more >Defining Tomcat context paths - Octopus Deploy
A nested context path like myapp/v1 means the web app can be accessed from ... By default, when you deploy a WAR file...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Definitely don’t take into account the
unit
vsintegration
stuff.It is a good point, but I don’t think we can factor that in right now.
@phryneas Sorry for the inconvenience. There has been a new section added to the screenshots docs on “Naming conventions”, hopefully this helps.