Backed by Y Combinator
Write tests in plain English. Run them on every PR or deploy. Know in minutes — not hours — if something broke.
Trusted by ENGINEERING TEAMS AT
BENEFITS
Write thorough tests without the headaches
Replace brittle scripts with adaptive testing.
Never rewrite a test after a UI change
Lark tests don't break when you revamp your dashboard or introduce a new API. Instead, Lark adapts and alerts you to the change.
Test Everything
Lark's agents can test anything a human could — UIs, APIs, SDKs, async workflows, and more.
Catch bugs before your users do
Run your tests on every commit, pull request, or deployment.
Secure Secrets
Your secrets are stored in secure vaults and are only accessible to ephemeral testing environments.
How It Works
Lark makes writing and managing tests for complex workflows trivial.
STEP-1
Create a testing workflow
Simply describe in natural language what you want to test.
STEP-2
Run the workflow
Configure your workflow to run in development, staging, or production environments.
STEP-3
View the results
Get detailed test results once the workflow is finished.
FAQ
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.