Change the way "Run All Specs" are run in Interactive Mode (from the GUI)
This comes from this epic... https://github.com/cypress-io/cypress/issues/681 All other stories were complete except this section... ## Interactive Mode - Continue enabling users to "Run all Tests" - Enable clicking folders to automatically run a subset of specs - Instead of killing the renderer process between specs the browser will simply be "navigated" to the next spec URL. - This will isolate each spec, and be much faster and less abrupt than killing the renderer like we will for the CLI. However this makes sense considering Cypress already has the code for swapping the URL and rehydrating the state of the reporter. We already do this when swapping domains in a cy.visit. - Isolating specs will help with memory exhaustion, but its still possible to blow out on a very long and intense spec file. - To solve this we'll begin purging snapshots by reducing the default minimum of 50, down to 5. - Purged snapshots will only affect passing tests and we will not purge data for failing tests. This will enable users to review the commands and output for failed tests - as they likely don't care about the data for passing tests anyway. - We'll need to add a good user experience / messaging around why snapshots were purged - When running multiple specs we'll add the spec file as part of the command log which will give you a shortcut for focusing in on a spec file. @jennifer-shehane we'll need you to comp some UI changes related to communicating to the users about running too many te
Posted by brian-mann on Apr 15, 2018, 3:23 AM
Tags
Related issues
- [BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
- Feature Request: Auto-resume CLI session when usage limit resets
- Please deobfuscate the Python
- [Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
- # 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
- [FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
reliability (Software)
[BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
Feature Request: Auto-resume CLI session when usage limit resets
Please deobfuscate the Python
[Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
# 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
[FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Admin Materials and Surfaces
AMD Support
Change the way "Run All Specs" are run in Interactive Mode (from the GUI)
This comes from this epic... https://github.com/cypress-io/cypress/issues/681 All other stories were complete except this section... ## Interactive Mode - Continue enabling users to "Run all Tests" - Enable clicking folders to automatically run a subset of specs - Instead of killing the renderer process between specs the browser will simply be "navigated" to the next spec URL. - This will isolate each spec, and be much faster and less abrupt than killing the renderer like we will for the CLI. However this makes sense considering Cypress already has the code for swapping the URL and rehydrating the state of the reporter. We already do this when swapping domains in a cy.visit. - Isolating specs will help with memory exhaustion, but its still possible to blow out on a very long and intense spec file. - To solve this we'll begin purging snapshots by reducing the default minimum of 50, down to 5. - Purged snapshots will only affect passing tests and we will not purge data for failing tests. This will enable users to review the commands and output for failed tests - as they likely don't care about the data for passing tests anyway. - We'll need to add a good user experience / messaging around why snapshots were purged - When running multiple specs we'll add the spec file as part of the command log which will give you a shortcut for focusing in on a spec file. @jennifer-shehane we'll need you to comp some UI changes related to communicating to the users about running too many te
Comments (0)
No comments yet. Start the discussion.