Do not keep tests in memory to avoid possible Chromium renderer crashes and
reduce overall cypress tests execution time.
Keeping tests in memory is only useful when using the cypress GUI.
This should fix this kind of errors that appears sometimes:
11:06:30 We detected that the Chromium Renderer process just crashed. 11:06:30 11:06:30 This is the equivalent to seeing the 'sad face' when Chrome dies. 11:06:30 11:06:30 This can happen for a number of different reasons: 11:06:30 11:06:30 - You wrote an endless loop and you must fix your own code 11:06:30 - There is a memory leak in Cypress (unlikely but possible) 11:06:30 - You are running Docker (there is an easy fix for this: see link below) 11:06:30 - You are running lots of tests on a memory intense application 11:06:30 - You are running in a memory starved VM environment 11:06:30 - There are problems with your GPU / GPU drivers 11:06:30 - There are browser bugs in Chromium 11:06:30 11:06:30 You can learn more including how to fix Docker here: 11:06:30 11:06:30 https://on.cypress.io/renderer-process-crashed 11:06:30 11:06:30 We detected that the Chromium Renderer process just crashed. 11:06:30 11:06:30 This is the equivalent to seeing the 'sad face' when Chrome dies. 11:06:30 11:06:30 This can happen for a number of different reasons: 11:06:30 11:06:30 - You wrote an endless loop and you must fix your own code 11:06:30 - There is a memory leak in Cypress (unlikely but possible) 11:06:30 - You are running Docker (there is an easy fix for this: see link below) 11:06:30 - You are running lots of tests on a memory intense application 11:06:30 - You are running in a memory starved VM environment 11:06:30 - There are problems with your GPU / GPU drivers 11:06:30 - There are browser bugs in Chromium 11:06:30 11:06:30 You can learn more including how to fix Docker here: 11:06:30 11:06:30 https://on.cypress.io/renderer-process-crashed