Cypress: Avoid failing tests due to page reload conditions causing exceptions

[juliusknorr]

This should hopefully avoid failures like in https://github.com/nextcloud/text/runs/3961812279 where the page navigation in the after all hook caused an exception that is thrown which then marks a test as failed. Instead we just ignore that since the page is navigating away.

[azul]

Looks good to me.

I don't think there are any exceptions during these steps that we would miss.
We need to make sure to check the actual test is done before running the after step. So tests should end with an assertion that checks if the last step has really completed and succeeded. But i think that's something we want independently of this change.

[azul]

removed duplicate

[azul]

So I had a look at the tests to check if they actually check things are done. All tests follow the share link to test it and make sure the editor renders fine. So that's cool.

But turns out that one test logs out already in order to test the public share link. This seems to be the only test that blows up in the after function. I suspect that's because we attempt to logout twice.

Catching the exception created by the duplicate logout attempt does not seem like the right approach to me. I think we should refactor the test instead to only loggout when needed.

[azul]

Ah... i was confused. it is a different test that does the logout. so that's not what's failing here. Sorry for the noise.