Lost Pixel
  • 🖼️What is Lost Pixel?
  • 🤝Lost Pixel Platform | Lost Pixel OSS
  • ⚙️Setup
    • Project Configuration
      • Modes
      • Baseline images
    • Integrating With GitHub Actions
    • ⏯️Lost Pixel Platform
  • 👨‍🏫Guides
    • Getting started
      • Getting started with Storybook
      • Getting started with Ladle
      • Getting started with Next js
    • Testing workflow (GitHub Actions)
    • Updating baseline images
  • 🥘Recipes
    • ⏯️Lost Pixel Platform
      • Working with baseline images
      • Local debugging
      • Integrations
      • Monorepo
      • Automatic baseline updates on selected branches
    • 🖼️lost-pixel(OSS)
      • Failing GitHub Action check
      • Automatic baseline update PR
      • Access test run images
    • 🍝General recipes
      • Thresholds
      • Flakiness
      • Viewport tests
      • Masking page elements
      • Executing arbitrary code before tests runs
      • Programmatically generated pages
  • 💡Examples
    • lost-pixel-example-next-js
    • lost-pixel-example-storybook
    • lost-pixel-example-ladle
  • More
    • Telemetry data
  • ⚙️API reference
    • lost-pixel.config.js|ts
    • PageScreenshotParameter
    • Mask
Powered by GitBook
On this page
  1. Recipes
  2. Lost Pixel Platform

Working with baseline images

Baseline approval flow

  1. On the first run of Lost Pixel, you will always get visual snapshots to be added to the platform as a baseline.

  2. After each new run, you will have a couple of options for the actions to be performed on the images:

    1. Remove image(if it has been deleted from visual tests)

    2. Approve the new baseline of the existing image(if the visual snapshot changed in a way we expected it to change)

    3. Reject the new baseline(this does not affect the baseline and is done for informational purposes to identify for future reviewers that that snapshot is a result of a regression)

  3. After you approve all images for the particular build on the Lost Pixel Platform, we will automatically make the status check on GitHub green.

  4. If they are not introducing changes that affect the front end, your subsequent commits shall be green on the Lost Pixel Platform and GitHub.

  5. When regression has happened, there will be a red status check on GitHub and Lost Pixel Platform - fix it on the side of the product, commit the code, and the new build of Lost Pixel Platform shall be green again.

PreviousLost Pixel PlatformNextLocal debugging

Last updated 1 year ago

🥘
⏯️