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.
Show older updates