Update our tests so they fail when an uncaught error or unhandled rejection happens in the browser.[^1]
Why
Some tests may have their assertions pass, but an error being displayed in the console because of something breaking but not affecting the assertion. We should get aware of that so we can fix things.
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
[ ] Tests fail if an uncaught error or unhandled rejection happens in the browser.
[^1]: We may have to take the matter in our own hands there, as I couldn't find anything similar to the Puppeteer's pageerror event for Webdriver.io. Suspecting this is because Webdriver has to handle both Chrome (locally) and Sauce Labs. We might be able to spot errors by tracking the errors ourselves inside the browser through the error and unhandledrejection events, and checking in an afterEach block (or potentially through hooks)
What
Update our tests so they fail when an uncaught error or unhandled rejection happens in the browser.[^1]
Why
Some tests may have their assertions pass, but an error being displayed in the console because of something breaking but not affecting the assertion. We should get aware of that so we can fix things.
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
[^1]: We may have to take the matter in our own hands there, as I couldn't find anything similar to the Puppeteer's
pageerrorevent for Webdriver.io. Suspecting this is because Webdriver has to handle both Chrome (locally) and Sauce Labs. We might be able to spot errors by tracking the errors ourselves inside the browser through theerrorandunhandledrejectionevents, and checking in anafterEachblock (or potentially through hooks)