visual regression test

Open
#12,944 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
playwright
Domain
frontend, testing

Research direction

Start by reviewing the referenced pull requests to understand the existing visual regression approach. Then identify how the project starts its stack and how Playwright can run against it; done means visual regression coverage for the insight editor runs successfully after the stack starts.

Written by the indexing model from the issue text.

Description

Goal:

It is impossible to break the insight editor

What do we think

  • move to playwright
    • initially only for visual regression
  • need to be able to start the stack before running the visual regression tests
    • once it is up we run playwright against it

reference:

https://github.com/PostHog/posthog/pull/11825
https://github.com/PostHog/posthog/pull/11771

Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PostHog/posthog

All issues in PostHog/posthog

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.