[legacy-framework] Fix RedirectError incorrectly failing Cypress tests

[akbo]

Closes blitz-js/legacy-framework#47

What are the changes and their implications?

In development, if Cypress is detected, the following errors will be hidden from Cypress, so they don't fail E2E tests: RedirectError, AuthenticationError, AuthorizationError, NotFoundError. For all other errors, the Cypress behavior is preserved.

Bug Checklist

This can only be tested with Cypress (test if Cypress fails a test that, e.g., logs in to an app). The auth example app has a Cypress test that covers the RedirectError. Not sure how to proceed here. What do you think?

[akbo]

There is one failing Nextjs integration test.

I looked into the logs: It appears to run the test test/integration/basic/test/index.test.js twice (initial run + retry).

Different tests fail in the two runs:
1st run: Error Recovery > 5x should recover ...
2nd run: should polyfill Node.js modules + Hot Module Reloading > editing a page > should update styles in a stateful component correctly

I ran the tests locally, twice: none fail

cd nextjs && yarn testheadless --testPathPattern "integration/basic"

Not sure, where to go from here. Any suggestion?

[flybayer]

Awesome, thank you!!

And yeah, that was just a flake test.