Google API for authentication is so complicated that it is easy to use Sign in form to authenticate a test user.
When you try to log in through Playwright or Puppeteer, Google can detect authentication by «robot», but you can prevent detection by using «stealth» plugin.
A basic set of packages for UI testing with Google authnetication:
- Playwright — testing framework;
- Playwright-extra — modular plugin framework for Playwright;
- Puppeteer-extra-plugin-stealth — «stealth» plugin to prevent detection.
Example website for testing: CERN (used as default URL).
- Clone repository
- Install dependencies:
npm install - Install dependencies for testing framework:
npm run test:install-deps - Run tests for the first time:
USER_LOGIN='{[email protected]}' USER_PASS='{password}' npm run test
- Run tests by reusing signed in the state (skipping authentication step):
SKIP_AUTH=true npm run test
-
The authentication process by Playwright with «stealth» plugin is done before tests will start. It is regulated by
playwright.config.tsthrough globalSetup option. Authentication script is located atlib/global-setup.tsand requires user's login and password; -
When authentication is done, the signed in state saves at
setup/storage-state.json; -
When authentication is done, the tests start and reuse signed in state;
-
To speed up subsequent test runs (for example, for debugging), you may skip authentication process by
SKIP_AUTH=trueCLI option (it will work if you already have a file of a signed in state).
Read the full article about this implementation: Google Authentication with Playwright.
UPDATE: In recent changes to the Playwright documentation, the recommended authentication concept has been changed, but the presented implementation still works.