Changelog

Everything new in qlane, freshest first.

  1. Re-run a single case

    Re-run one case of a finished pull-request run, a QA baseline that goes after your app's main user flows, API checks in pull-request runs, and fewer false bugs.

    TC-12Saved card
    Once3 times5 times
    Re-run this case
    Attempts
    This runFailed
    Re-run 1Failed
    Re-run 2Passed
    Re-run 3Failed

    Passed 1 of 4 attempts

    • Re-run one case of a finished pull-request run once, three or five times, and see whether the attempts agree.
    • The QA baseline ranks your app's areas and their main user flows, explores the top four, and keeps only cases that can fail. A Focus on field sends a run deep into one area, and features your deployment switches off are left out.
    • Get Started now ends by launching your QA baseline, and you can start and read a baseline over qlane MCP.
    • Pull-request runs check changed API endpoints with read-only requests, on every environment type except a plain URL.
    • Mention qlane in a review thread on a diff line, not only in the pull request's conversation.
    • In projects created since October 5, you can ask qlane for things in plain words in a pull-request comment, and a defect you dismiss as intended updates the case to expect that behaviour.
    • Fewer false bugs: no report from a cut-off page snapshot or a text check that differs only in spacing. A bug that a later pass contradicts is shown as Unconfirmed bug: needs a look, outside every bug count.
    • The agent sees authorization headers and cookies masked in every browser tool.
    • The header shows where you are as Project › Section, every switch in the app works the same way, and ⌘K finds every page in the sidebar.
    • Choose which editors can connect to qlane MCP, in organization settings.
    • Fixes: a pull-request check no longer stays in progress when a run cannot be planned, queued pull-request runs no longer stall at the plan limit, Compose files with YAML merge keys are accepted, and pending invitations no longer appear as members.

  2. A redesigned chat

    A new chat with run cards and named participants, a Test a pull request dialog, a new Coverage Matrix, a dashboard you arrange yourself, and faster Compose builds.

    B

    Ben

    Run the checkout suite before we ship

    Checkout suite6 / 8
    5 passed1 failed
    Staging
    • A redesigned chat: test runs appear as cards in the conversation, and every message shows who wrote it.
    • Test a pull request opens as a split view with the size of the change, its CI status and earlier runs.
    • A new Coverage Matrix: a matrix and a map on desktop, a list of areas on a phone.
    • The dashboard is made of widgets you can rearrange, with clickable Live rows and one period switch for all of them.
    • Compose builds reuse cached layers per environment, so repeat runs start faster.
    • Organization settings are split into pages for roles, plan and subscription.
    • Proposals are grouped by pull request.
    • Over qlane MCP you can create environments and sources, run configuration checks, and read results with their confidence.

  3. Start a pull-request test from qlane

    Test any open pull request from the dashboard, build a QA baseline for your whole app, and let a planner prepare the data each run needs.

    Test a pull request
    #482Add saved cards
    #479Fix coupon rounding
    #475New invoices page

    +120 −14

    CI passed

    Start test
    • Start a test for any open pull request from the Sessions page.
    • QA baseline: a first set of test cases for your whole app.
    • Before a run, a setup planner works out which data the tests need and creates it.
    • Chat can draft a test plan for a pull request.
    • A new session layout: cases on the left, everything else in panels under the recording. It works on phones too.
    • Run history shows the commit each run tested, and pull-request cards count their runs.
    • The Connections page is laid out as a catalog of integrations.
    • Setup can be switched off per project; it stays on by default.
    • Compose environments explain why a preview port didn't open.
    • The chat panel floats over the page instead of pushing it aside.

  4. qlane works with GitLab

    Merge requests on GitLab get the same testing as pull requests on GitHub, plus one comment per defect and a timeline for every recording.

    !42Add saved cards
    A

    @qlane test checkout with a saved card

    4 cases passed

    Saved card, new card, 3-D Secure, refund

    • GitLab support: connect GitLab, register repositories, test merge requests, and mention qlane in merge-request comments.
    • One comment per defect, edited in place as the change evolves.
    • Network requests, console output and the agent's actions sit on the same timeline as the session recording.
    • A bug's timecode jumps the recording to that moment.
    • Sandbox pages for the project and the organization show what is running, with details in a side panel.
    • When a setup goal fails, the reason is shown, and you can report it or run it again.
    • Test credentials can carry facts and notes for the agent.
    • Dashboard, Overview and Coverage Matrix are marked Beta.

  5. The agent prepares its own test data

    Runs now create the accounts and records a test needs before testing it, and a new organization dashboard brings every project's bugs into one queue.

    Before testing
    A customer with a saved card
    Three past orders
    Signed in as that customer
    Then: TC-5 Reorder from history
    • Setup: before testing, a run creates the accounts, records and state its cases need.
    • An organization dashboard with a roll-up of every project and a queue of bugs to triage.
    • Defects outlive the run that found them: they carry across pushes and close themselves when the case passes.
    • Setup goals get their own cards with a status roll-up.

  6. Pull requests across repositories, tested together

    Related pull requests in several repositories now run as one test, chat got faster, and multi-repository environments come to the Pro plan.

    acme/web#214

    feat/saved-cards

    acme/api#88

    feat/saved-cards

    One run

    Both branches, one sandbox

    Results posted to 2 pull requests

    • Pull requests that share a branch across repositories are tested in one run and reported on each.
    • Chat replies about 40% faster and starts a test when you ask for one.
    • Multi-repository environments are now part of the Pro plan.
    • A redesigned report on GitHub for every run.
    • The agent checks its results against what the pull request says it does.
    • Seven project settings that had no UI are now on a redesigned settings page, each with a help tip.
    • A per-project switch for qlane's status block in pull-request descriptions.
    • Compose environments can expose more than one public service.
    • qlane.ai explains the product in three pillars.

  7. A new way to get started

    Onboarding becomes a Get Started track you can come back to, the test agent finds more bugs, and a mention in a pull request starts a test.

    Get started2 of 4
    Connect GitHub
    Your environment
    Run your first test
    Invite your team
    • Get Started replaces onboarding: a step-by-step track you can come back to at any time.
    • The test agent runs on a newer model and finds more bugs: 16 of 16 seeded defects in our measurements, up from 9.
    • Mention @qlane in a pull-request comment to start a test.
    • Every verdict opens into its result, and after a run the session page becomes a report.
    • Pull-request reviews name the cases that failed.
    • Each proposal has a page of its own.
    • Your subscription status lives in the sidebar.

  8. Plan tests before you open a pull request

    Ask qlane for a test plan from your editor while the change is still local, give the agent its own mailbox, and see every pass backed by evidence.

    editor · qlane MCPno PR yet

    > plan tests for my local changes

    3 cases for 4 changed files

    1. Coupon survives sign-in

    2. Expired coupon shows an error

    • Plan tests for local changes from your editor over qlane MCP, before a pull request exists.
    • Connect your editor: a new dialog with setup for Claude, Cursor and Codex, also reachable from the user menu.
    • Test mailboxes: the agent receives email, so it can sign up and confirm accounts by itself.
    • A case passes only with captured evidence, and a case that couldn't run gets an outcome of its own.
    • Compose environments can seed app data from a script in your repository.
    • Test sessions show the pull request's author, and the sidebar remembers when you collapse it.

  9. A green check means something was tested

    qlane's pull-request check now says so when there was nothing to test, pull-request comments were redesigned, and the session list shows one row per pull request.

    Checks
    ci / buildPassed
    qlane · #4828 cases passed
    qlane · #483Nothing to test in this change
    • A neutral check when there is nothing to test; green only when cases ran.
    • Redesigned pull-request comments: an in-progress notice, a table of passed cases and a plain-language summary.
    • The Test Sessions list shows one row per pull request.
    • The agent uses your project skills while it tests.
    • Billing groups usage by pull request, with details in a side panel.
    • Environment warnings appear in a strip of their own.

  10. File bugs straight into Jira

    Jira Cloud and Jira Data Center join GitHub Issues as places to file the bugs qlane finds.

    Bug

    Expired coupon codes are still accepted

    High
    WEB-128
    TypeBug
    StatusTo do
    Reporterqlane
    • Jira Cloud and Jira Data Center as issue trackers, next to GitHub Issues.
    • Instructions for connecting qlane MCP right in the dashboard.
    • When an environment runs out of resources, the session says so.

  11. Try qlane free for 14 days

    New organizations get 25 credits for 14 days with no card, qlane connects to your editor over MCP, and every bug comes with evidence.

    Free trial

    25 credits

    14 days · no card needed

    Day 3 of 14

    • Free trial: 25 credits for 14 days, no card required.
    • qlane MCP: connect qlane to your editor, with regional endpoints and OAuth sign-in.
    • Every bug comes with evidence such as screenshots and logs, with secrets removed.
    • Apps that live in a subdirectory of a monorepo can be configured and run.

  12. See which case is being tested right now

    The session recording names the case the agent is working on, each test case keeps a history of its checks, and credits got simpler.

    Testing TC-4
    TC-2Add to cart
    TC-4Coupon
    TC-5Saved card
    • The recording shows which case is being tested, with redesigned case cards beside it.
    • Each test case keeps a history of the pull-request runs that checked it.
    • Simpler credits: one credit is worth one dollar, and a run reserves its credits before it starts.
    • Tool calls in chat fold into one quiet line per action, with an activity ticker while the agent works.

  13. Your data never trains a model

    Model providers don't train on qlane's AI requests, under their terms or our AI gateway provider’s agreements; zero data retention is a setting for each organization.

    How AI requests are handled
    Never used to train models
    Zero data retention, for organizations that have it
    Sub-processors listed at qlane.ai/security
    • No training by model providers on any AI request, under their terms or our AI gateway provider’s agreements with them; zero data retention for organizations that have it turned on.
    • A security page at qlane.ai/security, with an updated list of sub-processors.
    • Legal pages now match the published security posture.
    • Sandboxes get a public address (QLANE_SANDBOX_PUBLIC_URL) on qlane's own domain, so SSO and OAuth redirects work inside them.

  14. Pull-request comments that look at home on GitHub

    qlane's comments on pull requests were redesigned, pull-request tests reuse your existing test cases, and you can pay in euros.

    qlane commented

    7 passed · 1 failed

    TC-12Checkout with a saved card
    TC-9Sign in with SSO
    • Redesigned pull-request comments in GitHub's own style.
    • Pull-request tests reuse existing test cases where a change touches covered areas.
    • Pay in euros, with EU VAT handled.
    • qlane.ai: live test statistics, a mobile menu, pricing on the home page and the tools qlane works with.

  15. Environments built from several repositories

    A Compose environment can now combine several repositories, chat moves into a panel, and you can search Sessions, Test Cases and the Coverage Matrix by name.

    acme/web
    acme/api
    acme/worker
    Staging

    One sandbox, three repositories

    webapiworker
    • Compose environments built from several repositories.
    • Chat lives in a panel beside any project page, and shows the agent's reasoning.
    • Search by name on Sessions, Test Cases and the Coverage Matrix.
    • Review and edit a bug before it is filed to GitHub.
    • When a pull request merges, its test cases join the project's library.
    • Environment variables have a page of their own.
    • Starter prompts for a new chat.
    • A clear message when an action needs a different plan.

  16. Attach files and screenshots in chat

    Send the agent files and images, see how much context a conversation is using, and stop a reply reliably.

    checkout-spec.pdf

    The pay button overlaps the total on mobile. Can you reproduce it?

    Context 38%Stop
    • Attach files and images to chat messages.
    • A context indicator shows how much of the conversation's context is in use.
    • Stop reliably ends the agent's reply, and an indicator shows while the agent is working.
    • One pop-up window to connect GitHub and every integration.
    • Each environment keeps a history of its configuration checks.
    • Provisioning steps stay available to browse after a run.

  17. Chat with your team and the agent together

    Several people can now share one conversation with the agent, pull-request runs wait for CI, and failed results go straight to GitHub Issues.

    Invite flowAB
    A

    Ada

    Can you check that invites still work?

    B

    Ben

    Use the admin account.

    qlane

    Testing invites as admin now.

    • Shared chats: several people in one conversation, each with their own avatar.
    • Pull-request runs wait for CI to pass, without holding a run slot.
    • Test configuration: check an environment step by step with live logs before pull-request testing turns on.
    • File a failed result as a GitHub issue in the repository you choose.
    • Grafana integration: the agent reads your logs. Every MCP integration shows its health.
    • Run tests by hand, and read any session as a report.
    • Environment provisioning shows its progress in the session panel.

  18. Conversations that keep going

    Chat survives reloads and long-running work, chats join the Sessions page, and you can run a single test case.

    Run the signup suite on staging

    Running 12 cases…

    Page reloaded · picked up where it left off

    11 passed, 1 failed: the password reset email never arrives.

    • Chat conversations survive reloads and long-running work.
    • Chats and test runs share the Sessions timeline, with New chat in the header.
    • Test results appear in the chat itself.
    • Run a single test case, or a suite by test level.
    • The test plan is shown on the pull-request session page.
    • Choose a machine size and setup timeout for Compose environments, and change them later.
    • Rename a chat from the conversation.

  19. Follow a pull-request run stage by stage

    The session page shows which stage a run is in, failed builds explain themselves, and test credentials work in every environment.

    #482 · Add saved cards
    Prepare
    Plan
    Run
    Verify

    Running TC-3 of 8 · Checkout with a saved card

    • A live stage indicator on pull-request sessions.
    • Install, build and start failures show their logs in the dashboard.
    • Test credentials on every kind of environment, with the password hidden.
    • Project skills: write down instructions and know-how for the agent.
    • Compose environments get an editor for their .env file.
    • Credits are charged per phase of a run.
    • A loading bar on navigation, clickable passed cases, and a link to manage GitHub App access from the repository picker.

  20. Review proposed tests in one place

    A rebuilt review screen for proposed tests, a Coverage Matrix that fits your screen, promo codes at checkout, and pinned projects.

    Proposals
    Apply a coupon
    Reset a password
    Coverage Matrix
    • A rebuilt review screen for proposed test cases, with filters, confirmation and shareable links.
    • The Coverage Matrix fits the width of your screen.
    • Promo codes at checkout, with payments handled directly by Stripe.
    • Pin projects in your sidebar, and rename them.
    • qlane.ai: a section on enterprise security and a page to book a demo.
    • Onboarding sets up what to test as part of signing up.
    • A run ends when its tasks are done and marks a partial result as partial.
    • New icons across the product, and usage cards with charts.
Show older updates