screenshot() omits specName in `cypress open`
See original GitHub issueCurrent behavior
When taking a screenshot("name")
, the image is expected to be in directory {screenshotsFolder}/{adjustedSpecPath}/{name}.png
Using cypress run
this works fine (as in v9).
Using cypress open
, the {adjustedSpecPath}
is omitted.
Additionally, the after:screenshot
event won’t contain a specName
.
Desired behavior
cypress run
andcypress open
should show the same behaviour.after:screenshot
event should provide aspecName
Test code to reproduce
Repo to reproduce: https://github.com/joergplewe/cypress_screenshot_bug
Cypress Version
10.1.0
Other
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:6 (2 by maintainers)
Top Results From Across the Web
screenshot - Cypress Documentation
Take a screenshot of the application under test and, optionally, the Cypress Command Log. Syntax Usage Correct Usage Arguments fileName (String) A name....
Read more >Cypress 5.0 full page screenshot auto mode - Stack Overflow
Cypress by default captures only a viewport. In order to screenshot the whole page you need to configure the screenshot first: Cypress.
Read more >cli/types/cypress.d.ts - Fossies
the Fresh Open Source Software Archive ... 1873 * cy.screenshot() 1874 * cy.get(".post").screenshot() 1875 */ 1876 screenshot(options?:
Read more >Change log for 4.7.60
cluster-baremetal-operator git f73e5fcb sha256:3a6de25ed487f538f1f3039a82d08e2bed7bfd6bc1f09bd2d8b7479d7d5d5eb8 · csi-snapshot-validation-webhook ...
Read more >Using and Porting the GNU Compiler Collection - GCC, the GNU ...
ously crashes after main() has completed, you may have an object that is being ... The C++ standard allows an implementation to omit...
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
@joergplewe thank you for the tiny test! Confirmed this is a buggo 🐛
May I ask, what is the further process? Will it get fixed? When?
Just for my planning, for we have to wait for that before updating to v10.
Thanks alot.