Back to changelog

Re-run a single case

10 days ago

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.

When one case of a pull-request run fails and you are not sure the failure is real, you can now re-run just that case. Open it from the finished run, choose once, three or five times, and qlane runs only that case again, on the same commit and against the same environment. Every attempt is listed on the case under the original, with a line that says whether they agree. A re-run is for you alone: it never posts a check, a comment or a review to the pull request.

The QA baseline also got sharper this week. It now ranks the areas of your app by what matters most to the people using it, explores the top four, and keeps only cases that can actually fail. A new Focus on field sends a run deep into one area.

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.

Ready to ship without a QA bottleneck?

Set up in minutes. Connect a repo and let qlane test every PR like a human QA engineer.

Looking for Enterprise?

Dedicated support, custom data residency, and SSO.

Contact sales