Track Frontend JavaScript errors with Playwright fixtures

Learn in this video how you can leverage Playwright's fixture to track Frontend JavaScript exceptions and fail your tests when there are errors in a page.
Fixture explainer video: • Reuse Playwright Code...
Checkly docs: • Reuse Playwright Code...
Checkly community: www.checklyhq.com/slack/
#playwright

[@user-ki8ij8xi9c]

Thanks a lot! You produce useful content. Brief and to the point. Exactly what is needed!

[@ChecklyHQ]

Thanks for the kind word. Glad the videos are helpful!

[@gruttewibe76]

Great use and demonstration of the fixture concept!

[@ChecklyHQ]

Thanks! Happy you find it valuable! 💙

[@EdwinDeliz]

Very useful love your content

[@ChecklyHQ]

Happy to hear that! 💙

[@Wakkyguy]

Why is failOnJSError initialised as an array when it's supposed to be a boolean?

[@ChecklyHQ]

This is how Playwright wants us to define fixture options. You can read more here: playwright.dev/docs/test-fixtures#fixtures-options

[@Wakkyguy]

@@ChecklyHQ 👍🏻👍🏻

[@Wakkyguy]

I am working on enterprise app where authentication happens using Okta signin with redirect. Credentials are picked up from the user's system and then they are redirected back to the app with Okta credentials set in local storage. Okta react and okta authjs packages are being used to establish the user auth flow with the Okta server. How can I use playwright in this instance as on load the the user is redirected to another and then redirected back after a bunch in things happens in the background?