One Inbox for every bug
Bugs from QA baselines, chats and manual runs collect in your project's Inbox, a QA baseline run gets its own page, and a QLANE.md file tells qlane about your app.
Bugs found outside pull requests used to stay on the page of the run that found them. Now they collect in your project's Inbox: bugs from QA baselines, chat tests, and manual and scheduled runs all arrive in one list. When the same bug turns up in several runs, its sightings are grouped into one bug, and each sighting says where it came from.
From the Inbox you can confirm a bug, file it to your issue tracker, or dismiss it as not a bug, as working by design, or as a duplicate. A bug that was already filed keeps its issue, so it is never filed twice. The Inbox item in the project sidebar shows how many bugs are open.
- Chats have their own section in each project, with a history you can search, pin, rename and delete. Below 1024px the app switches to a compact layout with a navigation drawer and bottom sheets.
- The test case page was redesigned, and you can write a new test case yourself. In the library, select several cases to run, move or delete them together.
- Proposals and case results follow the same design. An update proposal shows what would change and warns when it would remove a unique value or a path placeholder from the case.
- Environments were redesigned: one page with tabs and a single Save bar, archiving for an environment you no longer use, and a Test data tab where you give the agent values it cannot make up, such as a tax number your app checks.
- A QA baseline run has its own page with its plan, flows and current phase. Each user flow is explored on its own, in up to four browsers at once, and High explores six areas for up to 45 minutes. A repeat baseline goes after the flows your library does not test yet.
- QA baselines sign in more reliably: they check your test accounts before planning, run each flow as the account it needs, support accounts that sign in with an emailed code, and sign up for their own account on a Compose environment with none stored.
- QA baselines keep more of the cases they find: every area's findings reach the case writer, and every rejected case is repaired instead of dropped.
- Put a QLANE.md file in your repository and qlane reads it as guidance from your team, in QA baselines and in pull-request testing.
- A pull-request case that passed while its screenshot shows a broken page (a dialog under another layer, clipped text, unreadable contrast, a broken image) is looked at again before the pass counts.
- In projects created since October 5, a Page monitors switch reports console errors and failed requests as bugs. An error already in your app shows as one line in the review instead of a comment on every pull request.
- When the AI model declines a request, chat says so and the call costs nothing; a test run it declines ends as partial, with the reason.
- Unconfirmed bugs get their own note in the pull-request comment and in chat run cards, outside every bug count.
- Session replays have one timeline with a Network tab and the bug moments marked, and the live view follows the tab the agent is using.
- Drag your projects into your own order, with a Pinned section at the top.
- Fixes: manual runs follow each library case's steps, a bug is filed under the case it breaks, Wait for CI checks no longer waits forever, a Compose service that crashes on start is reported as crashed, and a run stopped by an error on our side charges only the minimum.