0
0
mirror of https://github.com/PostHog/posthog.git synced 2024-11-24 09:14:46 +01:00
posthog/playwright/e2e-vrt/README.md
Thomas Obermüller 4a30e78b22
chore: use pnpm to manage dependencies (closes #12635) (#13190)
* chore: use pnpm to manage dependencies

* Fix CI errors

* Don't report Docker image size for external PRs

* Fix pnpm-lock.yaml formatting

* Fix module versions

* Ignore pnpm-lock.yaml

* Upgrade Cypress action for pnpm support

* Set up node and pnpm before Cypress

* Fix typescript issues

* Include patches directory in Dockerfile

* Fix Jest tests in CI

* Update lockfile

* Update lockfile

* Clean up Dockerfile

* Update pnpm-lock.yaml to reflect current package.json files

* remove yarn-error.log from .gitignore

* formatting

* update data exploration readme

* type jest.config.ts

* fix @react-hook issues for jest

* fix react-syntax-highlighter issues for jest

* fix jest issues from query-selector-shadow-dom

* fix transform ignore patterns and undo previous fixes

* add missing storybook peer dependencies

* fix nullish coalescing operator for storybook

* reorder storybook plugins

* update editor-update-tsd warning to new npm script

* use legacy ssl for chromatic / node 18 compatibility

* use pnpm for visual regression testing workflow

* use node 16 for chromatic

* add @babel/plugin-proposal-nullish-coalescing-operator as direct dependency

* try fix for plugin-server

* cleanup

* fix comment and warning

* update more comments

* update playwright dockerfile

* update plugin source types

* conditional image size reporting

* revert react-native instructions

* less restrictive pnpm verions

* use ref component name in line with style guide

Co-authored-by: Jacob Gillespie <jacobwgillespie@gmail.com>
2022-12-12 10:28:06 +01:00

2.6 KiB

Visual Regression Tests

We're using Playwright to run visual regression tests against Storybook. To create reference images that are consistent between development and CI we run Playwright in an Ubuntu docker container.

Workflow

Writing or updating a test

  1. Use fixtures

    tbd

  2. Perform the actions to get to the state

    • Get inspiration from one of the existing tests. Lemon Button and Insights scene are good examples.

    • Use Playwright's codegen feature to record user interactions interactively e.g. yarn playwright codegen http://localhost:6006/iframe.html?args=&id=scenes-app-insights--trends-line&viewMode=story.

    • Use Playwright's debug mode to inspect an existing test in a headed browser e.g. yarn playwright test --debug e2e-vrt/scenes-app/mytest.spec.ts:17:5. Sprinkle in await page.pause() in your test to stop at specific lines.

  3. Add screenshot expectations:

    • Capture the whole page (we rarely use this):

      await expect(page).toHaveScreenshot({ fullPage: true })
      
    • Capture content within a container element:

      const locator = page.locator('#root')
      await expect(locator).toHaveScreenshot()
      
    • Suggested Storybook container elements:

      • #root for components and
      • .main-app-content for scenes
  4. Generate the reference images with (you need to have Storybook running locally, i.e. on the Docker host machine):

    docker compose -f docker-compose.playwright.yml run -it -e STORYBOOK_URL=http://host.docker.internal:6006 playwright pnpm dlx playwright test -u
    

Open the generated report locally with pnpm dlx playwright show-report to see test results (they are mounted local in docker volume)

Renaming or deleting tests

When deleting or renaming a test, (re-)move the respective reference images as well or delete rm -rf playwright/**/*.png and re-create (see above) them.

Troubleshooting

The CI run on GitHub fails for any reason

Troubleshoot by viewing the Playwright report: Click on "Details" next to the failing workflow, click on "Summary" and download the artifact file. Extract this file and navigate to it in a terminal to then run pnpm dlx playwright show-report.

Your locally generated images, don't verify CI checks

GitHub is running tests against a temporary merge commit (to ensure tests still pass after being merged), meaning any changes currently in master will be present in the images generated in the CI run. If you suspect this is the case, merge master into your branch and push again.