Test your whole stack from its compose file
5 months ago
Docker Compose environments, Notion and Vercel integrations, organization settings, and a sharper planner for pull-request tests.
Point an environment at a repository with a compose file and qlane takes it from there. Every service starts in an isolated sandbox, qlane waits for the app to come up, and the test agent runs against it. You don't need a preview deployment or a staging server: qlane tests the same stack your developers run locally.
The same week brought a new planner for pull-request tests. Before it writes a single case, the agent reads the change and the code around it, and a separate critic reviews the plan. Cases come out sharper, with proper preconditions and postconditions.
compose.yaml
services:web:build: ./webports: ["3000:3000"]api:build: ./apicache:image: redis
Sandbox · pr-482
web:3000running
api:8080running
cache:6379healthy
Agent testing the preview- Docker Compose environments: your app starts from the repository's compose file in an isolated sandbox.
- Notion integration: the agent reads your documentation in Notion (read-only).
- Vercel integration: the agent reads build and runtime logs from your Vercel projects.
- Organization settings: logo, MFA, SSO with domain verification, and deleting an organization.
- A new test planner for pull requests: the agent studies the change first, and a critic reviews the plan.
- Features above your plan are shown locked, one click away from an upgrade.
- Live session view: watch the agent's browser and the test cases while a run is in progress.
- New navigation with separate organization and project rails.
- Session recordings get a poster frame, a jump to the failed step, and the agent's cursor; Stop ends a run.
- One setup wizard for pull-request testing and Compose, with a repository picker and recent chats in the sidebar.