# QLane ## Docs - [Docker Compose](https://docs.qlane.ai/connect/docker-compose.md): Run your full multi-service stack on every pull request from a compose.yaml file — web, API, workers, databases, and queues, with realistic data. - [Existing previews](https://docs.qlane.ai/connect/existing-previews.md): Test the per-PR preview deployments you already build with Vercel, Netlify, or Cloudflare Pages — no extra sandbox compute, faster turnaround. - [How QLane fits your app](https://docs.qlane.ai/connect/overview.md): Compare the four ways to connect QLane to your app: testing a URL, a single repo, a Docker Compose stack, or an existing PR preview deployment. - [Single repo](https://docs.qlane.ai/connect/single-repo.md): Connect a single-repo Node.js app so QLane clones the PR branch, builds it, runs it in an isolated sandbox, and tests it with full shell access. - [Test a URL](https://docs.qlane.ai/connect/test-a-url.md): Point QLane at any reachable staging or production URL to start testing in minutes — no build, no provisioning, optional credentials and linked repo. - [QA for the AI era](https://docs.qlane.ai/index.md): QLane is the AI QA engineer that tests every pull request in a real browser and posts structured GitHub reviews with screenshots and repro steps. - [Billing](https://docs.qlane.ai/manage/billing.md): Understand QLane plans, credits, concurrency, and retention — plus how to upgrade, downgrade, view invoices, and manage your subscription. - [Team and access](https://docs.qlane.ai/manage/team-and-access.md): Invite teammates, assign admin, member, and viewer roles, configure SAML SSO and SCIM directory sync, and review audit logs in your QLane organization. - [Quickstart](https://docs.qlane.ai/quickstart.md): Get QLane testing your pull requests in five minutes — sign up, connect a GitHub repo, create a project, pick a run mode, and open your first PR. - [Bug reports](https://docs.qlane.ai/results/bug-reports.md): What's in a QLane bug report — severity, repro steps, screenshots, DOM and console logs — and how to triage, dismiss, or push it to Linear or Jira. - [Coverage map](https://docs.qlane.ai/results/coverage.md): See what's tested and what's not with QLane's coverage map — a matrix of feature areas and test cases that surfaces gaps, trends, and untested epics. - [GitHub reviews](https://docs.qlane.ai/results/github-reviews.md): How QLane posts results to GitHub — a required check run, silent passes, and structured pull request reviews with one comment per bug on failure. - [Test cases](https://docs.qlane.ai/results/test-cases.md): Write plain-English test cases for the QLane agent — draft, active, and archived states, AI-drafted proposals from PR diffs, levels, tags, and versioning. - [Triggers](https://docs.qlane.ai/triggers.md): Trigger QLane sessions from GitHub, Linear, Jira, Slack, Claude Code, the browser extension, or on a schedule — wherever your team's work happens.