Log in once and reuse the saved browser state. Playwright's recommended approach is a setup project that authenticates, saves the storage state to a file, and lets every test project start already signed in. Keep that file out of version control, because it can contain cookies that let someone impersonate the test account, and delete it when it expires. Use one shared account only when tests do not modify server-side state; otherwise use one account per worker. If your app supports it, logging in through an API request is faster than driving the login form, and you can keep a separate saved state per role.

Sources: Playwright authentication