CYPRESS_PLAYBACK_MODE=passthrough

[pixelpax]

Is your feature request related to a problem? Please describe.
When play-testing and tweaking an API change (fullstack app), sometimes devs on my team might overwrite tests recordings during experiment, move onto something else, then not notice that they changed fixtures unintentionally.

Describe the solution you'd like
it'd be nice to have a CYPRESS_PLAYBACK_MODE=passthrough, to avoid intercepting, but not actually do recording until we're explicitly ready.

Describe alternatives you've considered
For now, we just run on recording mode when we "thru-test" locally and delete fixtures manually. I'd prefer to only commit changes to fixtures through a separate, deliberate process.

[DigTheDoug]

Sorry about the late response, I missed this issue alert.

Just to make sure I understand what your use case is, you would want an option that essentially turns off the actual functionality while you're developing, so it neither intercepts and responds with the fixture nor records new results, because you are making and testing changes to the actual API response? So basically a main off switch so you don't have to either delete fixtures or comment out the playback() calls?