Ungh Google OAuth is kind of frustrating - the major reason is that websites are pretty good at blocking pages that are coming from automation - and you get all sorts of issues and problems (not to mention if a company like Google (not the real example) uses you to test their platform and then SafeSearch picks up their staging login as a phishing site and blocks you ^_^).
I warmly recommend _not_ testing Google OAuth and instead passing a token and bypassing it on your server's side.
The way automation can work around it (in Testim.io for example) is "mock network" which is supported in our codeless solution but also available in most test infrastructure (like Playwright which is FOSS). You would mock out the parts that leave the user with a token they can use to authenticate.
I warmly recommend _not_ testing Google OAuth and instead passing a token and bypassing it on your server's side.
The way automation can work around it (in Testim.io for example) is "mock network" which is supported in our codeless solution but also available in most test infrastructure (like Playwright which is FOSS). You would mock out the parts that leave the user with a token they can use to authenticate.