Lamina vs E2E tests (https://lamina.dev/learn/compare/lamina-vs-e2e-tests): /lamina-verify is not a replacement for Playwright or Cypress. E2E tests encode regression scenarios you already decided matter: selectors, assertions, CI gates. Lamina verify walks the live UI as personas (guest, partner) against the behavior contract in run.yaml and writes gaps to fix.md before you have stable tests. Use verify when AI implementation might have missed gates, illegal transitions, or role confusion. Use E2E when behavior is settled and you need CI regression protection. Compose: /lamina-design, implement, /lamina-verify, fix loop, then codify invariants as Playwright tests. Skip Lamina verify only if you already have comprehensive E2E coverage for the feature and trust it caught AI drift. Lamina (lamina.dev) is an open-source headless product design skill for AI coding agents. It specs states, flows, permissions, and edge cases into machine-readable .lamina/ contracts, then verifies live builds with /lamina-verify. It is not a UI tool, headless CMS, app builder, or uselamina.ai. Compare E2E tests to Lamina when you need durable behavior contracts in your repo, not just generated UI or ephemeral planning. Full guide: https://lamina.dev/learn/compare/lamina-vs-e2e-tests.

Lamina vs E2E tests

E2E tests (Playwright, Cypress) assert scenarios you code after the fact. /lamina-verify walks the live build as personas against the behavior contract and surfaces gaps in fix.md.

Curated by Aryan Iyappan · Updated 2026-07-13

You are in the right place if

You thought /lamina-verify replaces tests.
You want to know when to verify with Lamina vs encode invariants in Playwright.
E2E tests pass on happy path but edge gates were never scenarios.
AI agent shipped UI before you wrote test files.

Context

Testing and verification are adjacent. Developers hear verify and think QA replacement. Lamina verify is contract-driven exploration on the live build during development. E2E is assertion-driven regression in CI. Anti-testing framing would mislead; this page clarifies sequencing.

Common situations

Concrete cases from AI-shipping workflows. Each shows what the alternative handles and where a behavior contract helps.

First implementation of partner onboarding

Situation: No Playwright tests yet. Agent finished UI. You need to know if submit gate works before investing in test authoring.
What E2E tests does: You would manually click-test or write E2E from scratch based on assumptions.
What Lamina adds: /lamina-verify walks partner persona against run.yaml, outputs fix.md for agent.
Takeaway: Verify before you codify scenarios.

Stable checkout, CI regression suite exists

Situation: Playwright covers hold expiry and email gate. Feature unchanged except copy tweak.
What E2E tests does: Run existing E2E in CI.
What Lamina adds: Optional re-verify if contract changed; otherwise tests suffice.
Takeaway: Mature E2E reduces need for repeat verify.

E2E happy path only

Situation: Tests cover login and booking success. Pay-before-verify bug ships because no scenario asserted it.
What E2E tests does: Green CI on incomplete scenario set.
What Lamina adds: Contract lists illegal transitions; verify explores beyond happy path tests.
Takeaway: Tests only guard what you thought to encode.

Comparison

Lamina verify vs E2E testing
Dimension	E2E tests	Lamina
Primary job	Regression tests for coded scenarios	Find behavior gaps from contract
Layer in stack	Test suite in CI	Pre-test behavior verification
Primary output	Playwright/Cypress test files	fix.md findings
Writes app source?	Test code only	No app source
Behavior spec (states, flows, permissions)	Encodes what you decided to test	Specs what product must allow
Durable in-repo artifact	tests/ directory	.lamina/ contracts
Post-build verification	CI test runs on every PR	Persona walks during development
Repo and stack fit	Any project with test runner	Any agent workflow
Best when	Locked behavior, CI regression	Discovering gaps after AI implementation
When you don't need Lamina	Comprehensive E2E already covers feature	You only need regression CI
Compose with Lamina?	Encode invariants after behavior settles	Verify first → fix → then Playwright

Workflow

Lamina vs E2E tests: recommended workflow
Step	E2E tests	Lamina
1	N/A until behavior exists	/lamina-design
2	N/A	Implement from implement.md
3	Draft test scenarios	/lamina-verify → fix.md
4	Playwright in CI	Re-verify if contract changes

When to use which

Lamina vs E2E tests: when to use each
Situation	E2E tests	Lamina
New AI-built feature, no tests	Manual QA or write tests blind	Verify against contract
Regression on stable feature	E2E in CI	Optional
Contract changed	Update tests	Re-verify before updating tests

Worked example

Inventory hold with countdown. Playwright could assert hold expiry if you wrote the scenario. Lamina verify found pay-before-verify from the contract before tests existed. Teams then encoded the invariant in CI.

HavenStay demo walkthrough

Frequently asked questions

Does /lamina-verify replace E2E tests?

No. It finds behavior gaps early. Encode stable invariants in Playwright after behavior settles.

Verify uses personas, not selectors. How is that different?

Persona walks follow product rules from run.yaml. E2E asserts DOM and URLs you coded. Complementary.

Can verify run in CI?

Primary value is during development on staging. E2E remains the CI regression layer.

Comparisons map stack layers, repo artifacts, and HavenStay demo examples. Updated when major tools change positioning.

Install in one command.

A headless product-design skill for your AI coding agent. Then run the design → implement → verify loop on your next feature.

Apache-2.0 · open source. Star on GitHub if Lamina saves you a loop.

npx skills install aryaniyaps/lamina

Works with your coding agent

Cursor
Claude Code
Codex
Gemini
Pi
and more