Start a pull-request test from qlane
24 days ago
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.
Pull-request testing no longer has to wait for a webhook. Open Sessions, pick an open pull request and start a run. The dialog shows how big the change is and whether its CI passed, so you can decide what is worth testing.
The same week qlane learned to build a QA baseline: a first set of test cases for the whole app, not only the parts a pull request touched.
Test a pull request
#482Add saved cards
#479Fix coupon rounding
#475New invoices page
+120 −14 · 6 files
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.