Henry Filosa

The issue lies in `const outFile = path.resolve(output, relFile)` in index.js. Because `output === relFile` you get a nonsense path of `cwd/path/to/file.js/path/to/file.js`. You get similar nonsense if you specify an...

I created a PR to advance discussion on a possible implementation of this. I'd also advocate for possibly removing the cache clearing behavior from _run_ mode as it can be...

@romankhomitskyi You'll probably addressing this question at the Cypress team, but I'd like to answer as someone who's excited about this development. It brings local storage and cookies in line...

Those are questions that are really only answerable by you and your unique application. However, a "bunch of it() to check only one page" is probably not [following best practices](https://docs.cypress.io/guides/references/best-practices#Creating-tiny-tests-with-a-single-assertion)....

In future versions [the behavior of Cypress in open mode will match that of run mode.](https://github.com/cypress-io/cypress/issues/1586). It seems this desired behavior is out of line with where the API is...

The response on the PR: > Does your solution work when running tests in parallel across several machines? If not, then this will introduce non-determinism when running tests in parallel...

You could do that in your plugin file and then access the information from the environmental variables. Getting that to work in a parallelized setup would be another matter however.

@emilyrohrbough If I may ask, does this work with test parallelization? `this.Cypress.backend('save:session', { ...data, setup: data.setup.toString(), validate: data.validate?.toString() }).catch(console.error)` seems to be what is saving the sessions state between states,...