front: log and make E2E tests fail on uncaught exceptions

[emersion]

Description and goal

Right now when an E2E test fails we don't have lots of details. When it trips on an exception we instead get a timeout and no details.

See:

• https://playwright.dev/docs/api/class-testconfig#test-config-global-setup
• https://playwright.dev/docs/api/class-test#test-extend
• https://playwright.dev/docs/api/class-page/#page-event-page-error
• [Question] Fail on unhandled exception? microsoft/playwright#16355 (comment)
• [Feature]: Add config setting to fail if the app writes to the console. microsoft/playwright#27277 (comment)
• [Question] Is there a way to capture console error logs ? microsoft/playwright#5546 (comment)

Acceptance criteria

.

[Maymanaf]

It's true that we currently lack detailed logs when an E2E test fails, but for now, we can review the screen recordings and trace files available in the CI artifacts.

Planned Solution: We will implement a new reporter (Allure Report) and integrate custom logs for each test.

⚠️ This task is not prioritized at the moment

[emersion]

I don't think changing the reporter would help. Even if it reports uncaught exceptions (does it?), tests triggering uncaught exceptions would still succeed (but we want these to fail).

[Maymanaf]

As you mentioned in the ticket, we can use pageerror to handle uncaught exceptions. However, these need to be customized and clearly defined, which is why we're considering a different reporting approach.
That said, I can add a non-optimized solution to fail the tests. Did you notice many uncaught exceptions not failing the tests?

[emersion]

Has this been closed by mistake? The PR hasn't been merged yet.