Ship fast.
Don't break things.

Lastest is a visual regression testing tool for teams that ship fast with AI. Record your tests or have AI do it, get them organized, CI runs them - and every release diffs before against after so only the things you intended to change actually change.

No credit card required

30s
Full suite. A sprint of testing, every commit.
3 engines
Pixel · Structural · Perceptual diffs
0 regressions
Reach prod. Visual diffs block merges automatically.
Plugs into
GitHub ActionsGitLab CIPlaywrightNode 22CircleCIVercel PreviewChromium · Firefox · WebKitSelf-hostedGitHub ActionsGitLab CIPlaywrightNode 22CircleCIVercel PreviewChromium · Firefox · WebKitSelf-hosted

The workflow

Record. Test. Ship.

Three steps between you and a UI that never regresses. No test code to write.

REC
1

Record

Click through your app once in the browser. Lastest captures the flow and every screen along the way. No selectors, no scripts.

1.4s
2.1s
+2.1%
1.8s
23/24
2

Test

On every push, Lastest replays the flow in real Chromium, Firefox and WebKit, and diffs every screen against your approved baseline.

All checks passed
Merge pull request
3

Ship

Approve intended changes as the new baseline, and merge with confidence. What you saw is exactly what your users get.

The record page

Just use your app.
Lastest writes the test.

Open the embedded browser and click through a flow. Every action you (or an AI agent) take is copied step by step, its selector is captured, and it lands in the timeline as it happens. When you stop, that timeline becomes the baseline every future run is compared against.

  • Mirrors real clicks, types and selects, from a human or an agent.
  • Captures a resilient selector for every step, so it survives refactors.
  • Builds the timeline that becomes your comparison baseline.
shop.acme.dev/product/atlas-tee
REC
ACME
$48.00
Size
SML
Add to cart
Timeline0 · 0.0s
Interact with
the page to
capture steps

Full-flow coverage

Every screen in the flow, watched.

Lastest doesn't stop at the page you edited - it walks the whole recorded flow, home to checkout, and flags exactly which screens moved. A two-pixel shift on checkout surfaces here before a reviewer ever has to go looking for it.

User flow · storefront2 changed
Home /
Product
Cart
+2.1%
Checkout2 diffs
Confirmed

Beyond pixels

Not just a picture.
The whole snapshot.

Lastest diffs twelve layers of every screen, not only the image. When a change appears, the agent traces it to the real cause: a shifted DOM node, a new network call, a design-token regression, a slower paint. That is how the development loop closes on the underlying issue, not just the symptom.

checkout/price-stepper.spec.ts#248 · chromiumreview_required
← Prev2 / 5Next →Show issue
The price stepper shifted 9px down inside the checkout summary.
CHANGED
1.05%
1.05% pixels changed2 snapshotsDraw FocusDraw Ignore
1+
1+
BeforeAfterChangesHover to compare

Baseline and current are pixel-matched automatically — switch modes to review the way that makes the change clearest to you.

OKNeeds ImprovementReject0 layer decisions on this build

Close the loop

From diff to fix,
without you.

Because Lastest captures the whole snapshot and not just a picture, it files a GitHub issue with everything a fix needs: the changed layers, the failing selector, the network delta and the suspected cause. It assigns your AI engineer, who reads that context, opens a PR, and closes the issue. You review the result, not the investigation.

  • Issues arrive pre-loaded with the snapshot's full evidence trail.
  • Your AI engineer picks it up, opens a PR and re-runs the check.
  • The issue closes itself once the re-run comes back safe_to_merge.
open#247

Visual regression · price stepper shifted 9px in checkout

Auto-filed from snapshot #248 · full context attached
+1.05%
Visual 1.05%Network +1 −17Perf 66 ΔDOM ✓A11y ✓suspected: .price-stepper lost its --space-2 top margin
AssigneeUnassigned
drafting issue from snapshot…

CI-native

Caught in CI,
not in production.

Lastest runs as a required status check on every pull request - against the Vercel or Netlify preview of that exact commit, so what gets tested is what ships. When a screen shifts, the merge is blocked and the diff is one click away, so reviewers see exactly what moved, right inside the PR.

1m 42s
avg. full run
0
flaky reruns
3
real browsers
fix(checkout): align price stepper#482Open
build · passed in 46s
unit tests · 312 passed
Lastest / visual · 2 changes detectedRequired
price-stepper · +2.1%
coupon-banner · +0.4%
Review →
deploy preview · pending

Why it matters

Ship faster because
you trust every deploy.

Manual UI checks are slow and easy to skip, so regressions slip out and cost you a support ticket, a hotfix, and a customer's trust. Lastest turns that whole loop into a green check: you move quickly precisely because you can see nothing broke.

  • Catch regressions in seconds, not tickets

    A shifted layout shows up on the pull request, long before a user ever reaches it.

  • Retire the manual QA pass

    The flow you recorded is your regression suite. It reruns itself on every commit, for free.

  • Merge without the pit in your stomach

    A green Lastest check means the UI is exactly as intended. Reviewers approve what they can see moved, nothing more.

This week on mainsafe_to_merge
41
PRs shipped
6
regressions caught
0
reached users
feat: new nav layout
fix: checkout price stepper caught +2.1%
chore: bump dependencies

Intelligence

AI test generation

Claude writes resilient Playwright code with a 7-layer selector fallback (data-testid → id → role → aria-label → text → CSS → OCR). Survives refactors that break hand-written tests.

Economics

Zero-token replays

AI runs only when you create or fix a test. Every replay is pure Playwright execution. Test a thousand times a day for €0 in tokens. Self-hosted screenshots are unlimited regardless of volume.

Precision

3 diff engines

pixelmatch (pixel-perfect), SSIM (structural similarity), and Butteraugli (human-perception-aligned). Choose the trade-off per test - or run all three for a benchmark verdict.

Automation

Play Agent - 11-step pipeline

Specialized sub-agents (Orchestrator, Planner, Scout, Diver, Generator, Healer) plan, generate, run, and fix tests autonomously. Pause, approve, or skip any step. Resumes where it left off.

Ownership

Self-hosted & open source

FSL-1.1-ALv2 license. Your infra, your network boundary. Screenshots never leave your servers. Full source on GitHub. Or run it on Lastest Cloud and skip ops entirely.

Integration

CI/CD native + Smart Run

Reusable GitHub Action, GitLab MR comments (self-hosted GitLab supported), webhook triggers, scheduled cron runs. Smart Run analyzes git diffs and runs only the tests your change touched.

Explore all features

40+ capabilities, four families, every entry on every plan.

What people are saying

Honest words from the community.

Unedited reactions from Reddit threads, users, and early adopters - including the parts where they told us what to fix.

  • u/Weird-Shake8670Founder · Lastest caught a real bug
    Reddit
    I really appreciate you giving me the heads up on this. My Sentry notification for this just went off 2 hours ago. All fixed. If you find the app useful, here’s a promo as a thank you.
  • u/dyagokabar/indiebiz
    Reddit
    This sounds like a great alternative to the expensive incumbents. Have you thought about how this could be demoed on TikTok? I have a network of tech-focused accounts and would love to help you collab on a viral video to get this in front of more dev teams.
  • u/Quirky_Research_949OP · r/microsaas
    Reddit
    Great idea, and I like that it’s open source. That said, I found the design a bit confusing. It took me more than a couple of minutes to understand what the project does. You might want to rethink the design to make the value clearer.
  • u/Legitimate-Peace-583r/microsaas
    Reddit
    It looks like a great fit for startuplibrary.net! You should submit it for a chance to be featured in our newsletter.
  • u/Deep_Ad1959r/webdev · code-review framing
    Reddit
    my team runs it exactly this way and the code-review framing is what finally made it stick. when tests generate as plain playwright files instead of runtime LLM orchestration, a UI change produces a diff you can actually look at and decide whether it’s a real breakage or an expected update. nobody has to learn a new DSL either, anyone who knows playwright can read or edit the tests.
  • u/Royal_Dream_6246r/softwaretesting · "naked" artifact ask
    Reddit
    What I’m looking for is a produced artifact that is truly "naked" - like raw Selenium code or pure Java/Python scripts. If a tool gives me standard code I can just run independently in any IDE without needing a specific vendor’s CLI, that’s the ultimate "no-lock-in" for me.
  • u/ctenidae8r/AI_Agents
    Reddit
    100%. I try to scope personae so that even ambiguity has some heuristic guidance - make it easier to stay in the valley than hill climb out. Make what you can deterministic, make what’s reasoned easier to get right than wrong.
  • u/Elegant-Display-5228r/nextjs · silent SEO failures
    Reddit
    That staging noindex example is exactly the kind of failure I was trying to understand. Have you found any off-the-shelf tool that catches this reliably, or is it still mostly custom CI checks with Playwright/Puppeteer?
  • u/agentbrowser091r/AI_Agents
    Reddit
    This sounds pretty interesting so these checks can help you understand when it is safe to check the page state - so it can make an approach without a screenshot more reliable?
  • u/Impossible-Celery-87r/Playwright · SnapDrift OP
    Reddit
    Thanks for sharing your real-world setup experience/insights!
  • u/adam_clooneyr/sre
    Reddit
    Yeah this resonates. the "merged config at apply time" point is exactly where it felt off.
  • u/TranslatorRude4917r/Frontend
    Reddit
    Exactly, getting team buy-in on conventions is not easy. I think I did not show/explain the difference between e2e and component tests, it seems like a lot of people do a mix of them and just put the e2e stamp on it.
  • u/Nice_Translator_9233r/QualityAssurance
    Reddit
    Thanks for this perspective. Needed this bit of assurance right now :) I will focus on refining my domain knowledge and API testing skills.
  • u/Full_Pirate_5422r/softwaretesting
    Reddit
    Makes sense :)
  • u/2ERIXr/Playwright
    Reddit
    Cheers 🥂
  • Chaitnaya BhagatTested by
    User
    Love your app, the vibe is really cool and the name is catchy too. you have too many things going on in your project, so focus your attention functionalities more and you have way too many settings options to choose from 😭
    Wed, May 6, 2026 · 06:13 AM
  • u/Asipahior/AssetBuilders
    Reddit
    I like the idea of having one of the agents act on a deterministic outside the model signal. Definitely worth giving it a shot.
  • u/Born-Exercise-29322 points · 18h ago
    Reddit
    Verification being the bottleneck is exactly right, and it’s not going away because the output surface is growing faster than anyone’s ability to review it. The real unlock isn’t better verification tools, it’s narrowing the scope of what you let AI touch until the failure rate is low enough that spot-checking is sufficient.
  • PeerPush reviewerTested by
    User
    Easy, intuitive, clean and fast. I pressed run but I didn’t get any info on the failed test, so I went to debug mode and there I could visualize the issues. I activated the gamification, so when I ran the test successfully I got a leaderboard with other bot agents, haha! The test itself, running the scripts, the AI fixing the bugs, the info provided during the onboarding - honestly the entire process is well guided and easy to follow through. As of now I made no app as I’m busy coding mine, but it would surely make me confident to try and host an app here. It seems a very professional and legit AI workflow, with a nice code editor and debugger unlike many I know - it’s dev ready, honestly I would recommend it.
  • GustavooIVPeerPush
    User
    Hey, looks really cool tbh. I have been thinking of making something like this myself in the past. Currently don’t have a need for it, but maybe in the future. How is it going for you - how many users does Lastest have? Just curious.
  • @wade_bhavy55123Bhavya Wade · founder whose app Lastest tested
    Really appreciate you trying it out and sharing feedback 🙌 Glad the no-auth flow felt smooth and worked on the first try. The confidence model was one area I wanted to make more thoughtful than a typical decision matrix.
    May 22
  • @Awaki18Lasse · building FixyFlow · Lastest flagged verify email
    Thanks, will investigate verify email!
    May 21
  • @codewithayobamiFolarin Ayobami · aMail founder
    Thanks bro ♥️
    Jun 29
  • @buildwithinnoInnocent Dev · InnoStore founder
    This cool I will check it out
    Jun 26
  • u/aviya88Reddit · honest user feedback
    Reddit
    Thanks for this. That looks cool. Just a comment as a user - it was not immediately clear what it does. I can see it generated a demo video, but did you do it manually or is it automated by the app? (in that case it’s great.)
  • u/ImplementImmediate54r/AI_Agents · BugHunters Vision builder
    Reddit
    Looked at lastest, interesting tool. Pre-capture stabilization is a smart approach - freezing noise before it hits the diff engine is clean. Might be worth pointing people toward lastest when they’re starting from scratch, BHV when they’re already invested in an existing suite.
  • u/hiten1818726363OP · Top 1% Commenter
    Reddit
    Thats just crazy ui bro. And concept is good too. It think you should add some video representation on how it works.
  • u/Deep_Ad1959r/webdev · validates the thesis
    Reddit
    this is the right split. the approach that’s clicked for me is using AI to crawl the app and generate the initial test files, then running those as plain playwright tests in CI. you get the time savings on the writing side without introducing non-determinism at runtime. the generated code is just standard test files you can read, edit, and debug like anything else.
  • u/Royal_Dream_6246r/softwaretesting · vendor-lock-in pain
    Reddit
    Yep - that’s exactly what I was trying to find. Feels like there’s still a gap here - either fully in-house or tool-dependent. I haven’t seen a vendor-neutral approach that combines no-code browser automation with visualization and still produces standard, portable automation code.
  • u/theov666r/ExperiencedDevs
    Reddit
    Well put. The "ADRs as checks instead of docs" framing is close to where my thinking has landed too. Traditional ADRs/documentation help humans review after the fact, but AI-assisted development shifts the bottleneck earlier. If constraints aren’t machine-readable/enforceable before or during generation, review becomes the only control layer and doesn’t scale with output volume.
  • u/Equal_Jellyfish_4771r/AI_Agents
    Reddit
    The versioned prompt + golden trace replay approach is solid, but the real unlock is treating tool selection itself as a signal. If your agent starts reaching for different tools than usual for the same intent pattern, that’s drift.
  • u/Just_Marionberry_673r/Everything_QA · visual regression flakiness
    Reddit
    I appreciate your insight. I found out anti-aliasing is also being one of the most difficult things. Can you share your approach using SSIM perceptual diff? Is it something that you build yourself?
  • u/zanex13r/Playwright
    Reddit
    This guy tests. Great recommendations.
  • u/mrothror/ExperiencedDevs
    Reddit
    Agree on both of these. I spend a lot of time up front working with it to make the plan. I have definitely had it make sequence diagrams or similar to make sure I understood how it was proposing the components work. Good tip on the tests, that is not something that is part of my regular rotation but probably should be.
  • u/tommix1987r/webdev
    Reddit
    Yes fully agree on the ci/CD part - it has enormous advantages.
  • u/TranslatorRude4917validates PW codegen + anchor tests approach
    Reddit
    Create onboarding flow anchor test, set up proper POM, fixtures etc. Using those solid foundations use AI to quickly generate edge-cases, variations, negative tests etc. 1 proper anchor test can provide you with enough to generate 10 or maybe even 20 tests using the same foundations. The bottleneck is probably creating those high-quality flows in the first place. I had pretty good result with what u/lastesthero suggested: using PW codegen to ground the tests in something that actually works, reducing hallucinations and AI spending a shitton of tokens figuring out how to use your app.
  • u/hrabria_zaekr/nextjs
    Reddit
    That makes a lot of sense! Thanks for your answer!
  • u/Crypted39r/Playwright · mask editor builder
    Reddit
    Appreciate it! Thank you!
  • LSTested by
    User
    Overall, the app feels pretty polished and thoughtfully designed. The onboarding was easy to follow, and I liked that the recorder automatically replayed the test after saving - that made the flow feel smooth and fast. The tooltips during recording were also genuinely helpful without being annoying. The biggest friction for me was needing to connect GitHub before getting much real value from the product. As someone just wanting to quickly test a URL, it felt a bit limiting because a lot of features seem blocked until a repo is connected. The recording experience itself worked well for the most part, although I noticed some clicks inside the embedded browser didn’t always trigger navigation correctly. Other than that, the UI is clean, defaults make sense, and the overall experience feels solid.
    Wed, May 6, 2026 · 08:58 AM
  • trogdorTested by
    User
    wow
  • u/Asipahio2 points · 1d ago
    Reddit
    Totally agree. AI has shifted the bottleneck from creation to verification. I’ve noticed this in my own work too. The verification problem reminds me of code reviews before we had good testing practices. The real unlock for me was accepting that verification is now the high-value work. Creation is commoditized, but knowing what’s right? That’s where humans still matter.
  • lisalacythompsonacaPeerPush
    User
    wow that’s pretty cool, thanks! Definitely a helpful tool for us vibe coders who kinda just cross our fingers and hope for the best 🫣 Are you launching on PeerPush? Once I get a chance to implement I’m happy to review!
    May 15, 2026
  • stuffyoushouldPeerPush
    User
    neat stuff!
  • @omkar_buildsOmkar · HermesDeploy founder · 9 baselines paired clean
    Signed up for HermesDeploy and ran every screen through Lastest: home → login → full 5-step agent wizard (Name → Plan → Model → Telegram → Ready). 9 baselines, paired perfectly clean. That’s so awesome, thanks!
    May 21
  • @georanklandGeoRankLand · signup flow tested end-to-end
    Just tested the signup flow end-to-end and verification is working cleanly. Links are single-use though, so if you clicked it twice that would trigger the error you’re seeing. Happy to manually verify your account or troubleshoot via DM.
    May 21
  • @BillingServBillingServ · replying to Lastest walkthrough feedback
    Thank you for the feedback, glad to hear feedback about Altcha we use it everywhere we can, we are GDPR compliant so take data seriously.
    Jun 30
  • @auditormusic19shantanu bhatt · replying to Lastest’s iGrow walkthrough
    Thank you for this analysis!
    Jun 26

Live · 743 real reports

See it on apps you know.

Every card is a real Lastest run against a live product. Click any one - that's the same report you'll get from your own staging URL.

Auto-rotating · hover to pause ·browse the full gallery →

Pricing

Early adopter pricing

Cloud plans are discounted for early adopters - sign up now and lock in this price for the lifetime of your subscription. Prefer to run it yourself? See the self-host page for self-host, supported, and enterprise licenses.

Cloud

Free

Try it out

€0/ month

Hosted by us. Kick the tires on a real project. No credit card.

  • 1 project
  • Shared runner pool
  • 500 capped runner-minutes
  • 1 concurrent run
  • Community support
Try cloud free
Early adopter

Starter

Solo devs & small teams

€29€14/ month + tax

For builders shipping regularly. Locked-in early adopter price.

  • 3 projects
  • 5,000 priority run-minutes
  • 2 concurrent runs
  • Email support
Start free

Pro

Larger teams + SSO

Customtailored quote

Capacity, SSO, and priority response for serious teams.

  • Unlimited projects (reasonable quotas)
  • 120,000 priority run-minutes
  • 15 concurrent runs
  • SSO / SAML
  • Priority support
Contact us

From the blog

Recent writing

Field notes on AI test generation, diff engines, and self-hosting visual regression at every team size.

Enterprise

AI speed meets enterprise governance

Lastest is free to self-host for every team. The human-in-the-loop dashboard already provides the oversight layer enterprises require - approval workflows, audit trails, and full test visibility. For organizations needing SLAs, managed infrastructure, SSO integration, or dedicated engineering support, we offer enterprise agreements. No minimum commitment. No sales presentations.

SSO at the edge, RBAC and audit log in the middle, governance outputs out the other side - all inside your network boundary.

SLA-backed uptime guarantees

SSO / SAML integration

Managed cloud deployment

Dedicated support channel

On-premise installation support

Priority feature development

Frequently asked questions about visual regression testing

What is AI-powered testing?
AI-powered testing uses machine learning to analyze your application, generate test cases, and identify bugs automatically. Unlike scripted automation, it adapts to UI changes and can explore paths a human might miss.
Will AI replace QA engineers?
No. AI handles repetitive regression checks at machine speed, freeing QA engineers for exploratory testing, edge cases, and judgment calls that require human context. It augments your team, not replaces it.
What's the difference between AI-assisted and agentic testing?
AI-assisted tools suggest or autocomplete test scripts you still manage. Agentic testing tools autonomously navigate your app, decide what to test, and generate full test suites with no manual scripting required.
What bugs does AI testing catch that manual testing misses?
Subtle visual regressions like 1px shifts, font rendering differences, and color changes. Also cross-browser inconsistencies and intermittent layout issues across responsive breakpoints that are invisible to human spot-checks.
What is visual regression testing?
Visual regression testing captures screenshots of your UI before and after code changes, then compares them to detect unintended visual differences. It catches what functional tests cannot - how your app actually looks to users.
How is visual testing different from functional testing?
Visual testing checks appearance, layout, and CSS rendering. Functional testing checks logic, data flow, and behavior. Visual catches pixel shifts and broken layouts; functional catches wrong calculations and missing data. You need both for complete coverage.
What are pixel-diff, DOM-based, and AI-powered comparison approaches?
Pixel-diff compares raw pixels and is fast but has high false positives. DOM-based compares HTML structure but misses visual-only bugs. AI-powered uses perceptual models for the lowest false positive rate and handles dynamic content. Lastest uses all three engines.
How does AI reduce false positives in visual testing?
AI distinguishes meaningful changes like broken layouts from noise like anti-aliasing differences, font rendering variations, and dynamic timestamps. Traditional pixel-diff flags every sub-pixel shift; AI focuses on what humans would actually notice.
How long does it take to set up AI visual testing?
With Lastest: run docker compose up, point it at your app, and AI generates your first test suite in under a minute. No test scripts to write manually.
Does AI visual testing integrate with existing CI/CD pipelines?
Yes. Lastest runs as a Docker container that plugs into GitHub Actions, GitLab CI, Jenkins, or any pipeline. Approved tests replay deterministically on every push at zero token cost.
What is the ROI of automated visual testing?
Teams report 40%+ more test coverage, 10x faster regression cycles, and 36+ engineering days saved per year. Manual visual QA that takes a full sprint is replaced by a 30-second AI run.
Is AI testing suitable for agile and continuous deployment teams?
It's practically required. When you ship daily, manual regression is the bottleneck. AI visual testing runs in CI on every push, catching regressions before they reach production.
Visual testing vs functional testing - which do I need?
Use visual testing for layouts, themes, and responsive design. Use functional testing for form submissions, API calls, and business logic. Best practice: use both together for complete coverage.
AI testing vs manual QA - when to use each?
AI excels at speed, unlimited scale, and regression coverage. Manual QA excels at exploratory testing, UX judgment, and edge cases. Use AI for repetitive regression; use manual for discovery and risk assessment.
AI testing vs traditional Selenium/Playwright scripts?
AI testing takes minutes to set up, self-heals when UI changes, and generates tests automatically. Traditional scripts require hours of manual writing, break on UI changes, and need 95% more maintenance. Lastest doesn't replace Playwright - it generates Playwright scripts for you.
Pixel-diff vs AI-powered visual testing?
Pixel-diff has a high false positive rate and fails on dynamic content but is simple to set up. AI-powered visual testing has low false positives, handles dynamic content with perceptual comparison. Lastest offers both plus structural diff - triple coverage.
What should I look for when evaluating AI testing tools?
CI/CD integration, false positive rate, self-healing capabilities, coverage reporting, and governance controls. Bonus points for open-source, self-hosted, and no per-seat pricing.
How are dynamic content and dates handled in visual testing?
AI visual testing uses region masking, smart ignore rules, and perceptual filtering to exclude known dynamic areas like timestamps, ads, and user-specific content while still catching real regressions.
Does AI visual testing work for mobile and responsive layouts?
Yes, and it's one of the highest-value use cases. AI tests across breakpoints simultaneously, catching responsive bugs that manual testing on 2-3 devices would miss.
What are the limitations of AI testing?
AI cannot assess business risk, understand user intent, or replace human judgment on subjective quality. It needs a review layer like Lastest's oversight dashboard and a human-defined testing strategy to be effective.
Does BackstopJS support Docker for visual diff?
Yes - BackstopJS ships a community Docker image you can run in CI, but it only wraps BackstopJS's pixel/structural diff and you still write every scenario by hand. For a Docker-first visual diff with AI-generated tests, a perceptual engine, and a review dashboard out of the box, Lastest is the better pick: one docker compose up and you're diffing. Lastest is free, open-source, and self-hosted.
How to choose visual regression testing for startups?
Startups should optimize for setup time, false-positive triage, and predictable cost. Rule out per-seat and per-snapshot pricing, require Docker self-host, and demand AI test generation so one engineer can cover the whole app. Lastest hits all three: free, open-source, unlimited screenshots, and one-minute setup via docker-compose.
Cheapest visual regression testing alternative to Chromatic?
The cheapest serious alternative to Chromatic ($179+/mo, Storybook-only) is Lastest. Lastest is free, open-source, self-hosted via Docker, works with any web app (Storybook optional), and costs $0 regardless of how many screenshots you take.
What visual testing tool integrates well with GitHub Actions?
Lastest integrates best with GitHub Actions. It runs as a Docker container, so the Actions step is a single docker run (or services: block) against your PR preview. Approved tests replay deterministically on every push at zero token cost - no API keys, no per-build fees, and no screenshots leaving your runner. Lastest also publishes a reusable GitHub Action (las-team/lastest/action@main) for zero-config CI/CD integration.
How to catch visual bugs in CI/CD pipeline?
Add a visual regression step after your build: spin up a preview of the branch, run a Dockerized visual diff against the main baseline, and fail the PR on a non-trivial diff. Lastest is purpose-built for this - Docker image, compatible with GitHub Actions, GitLab CI, and Jenkins, with a perceptual diff engine that keeps noise low enough that engineers actually read the results.
Best open-source visual regression testing tools for Playwright?
The serious open-source visual regression testing tools for Playwright are Lastest, BackstopJS, Lost Pixel, and playwright-visual-comparisons. Of those, Lastest is the only one that pairs Playwright with AI-generated tests, three diff engines (pixel, structural, perceptual), and a review dashboard. Lastest doesn't replace Playwright - it generates Playwright scripts for you.
How does Percy compare to Applitools for visual testing?
Percy (BrowserStack) is cheaper and simpler; Applitools is more powerful with "Visual AI" and a cross-browser cloud but 3–5× the price and enterprise-sales-only. Both charge per screenshot and ship your UI to their servers. For Applitools-class AI diffing without the invoice or the data-exfiltration problem, Lastest is the open-source alternative - self-hosted, unlimited snapshots, same perceptual-diff class.
What's the best visual regression testing tool for enterprise?
The best visual regression testing tool for enterprise is Lastest. Enterprise needs three things SaaS vendors struggle with: data residency (screenshots never leave your network), predictable cost (no per-seat or per-snapshot scaling), and governance/audit (who approved which baseline). Lastest checks all three - self-hosted Docker, open-source license, oversight dashboard with approval history - at a fraction of the Applitools, Percy, or Chromatic enterprise price.