Backed by Y Combinator
UI, API, CLI, and mobile tests run on a continuous cadence — you watch the green, Lark watches the red. Built by ex-Stripe engineers.
today · runs completed
99.6% pass·31 auto-repaired
Checkout flow · guest
wflw_exec_o6bi6LrKroef
push · main
—
Order webhook · paid
wflw_exec_K7e90UFiXgnd
schedule · 5m
—
Mobile · order placed
wflw_exec_R3kQzNm9tx7
push · staging
—
CLI · auth flow
wflw_exec_8mLfocK4pq2
manual · jack
—
Trusted by ENGINEERING TEAMS AT
Best-in-class testing infrastructure
Everything you need to make sure your product never breaks.
Test every surface
Lark's agents can test UIs, APIs, SDKs, async workflows, and more.
How do I integrate Lark with my CI/CD pipeline?
We provide native integrations with GitHub Actions, GitLab CI, and other popular CI tools.
What types of applications can Lark test?
Tests can be written for dashboards, API endpoints, and more. You can see some sample tests at https://tests.getlark.ai/a/polar/
How is Lark different from something like Playwright?
Playwright tests are hard to write and maintain because it's code. Lark tests are trivial to write because it's natural language. Playwright tests can be brittle and break easily if the product changes. Lark tests are more robust and can handle changes to the product. Playwright tests are for frontend only, Lark tests can be for frontend, backend APIs, and more.
What happens when a test fails in production?
You'll receive instant alerts via Slack, email, or PagerDuty with detailed logs and screenshots to help you quickly identify and resolve the issue. With our CI integration you can also prevent PRs from merging if tests fail.