Real bugs from real pull requests.
We test Qlane with Qlane. These are findings from our own app, and how far each one got.
Caught on our own pull requests
We test Qlane with Qlane. Here is some of what it found in our own app, and how far each finding got.
Each card shows what Qlane found, what a developer confirmed, what was fixed, and whether Qlane checked the fix. Where it didn’t, the card says so.
A dialog nobody could click
A pull request rebuilt every dialog in the app. The “Run a test session” dialog then opened under its own dimmed backdrop, and every click and tap landed on the backdrop.
- found Found by Qlane at 390 px and 1280 px wide, checked against a dialog that worked, and rated critical.
- confirmed Confirmed by the developer, who traced the cause.
- fixed Fixed before merge, with new tests that open the dialog with a click.
- not re-run Not re-run by Qlane after the fix.
The tests written with the change all started with the dialog already open, and the AI code reviewer skipped the 424-file pull request. The run that found it was partial, with two cases blocked.
A chat list hidden behind a footer
On short screens, the sidebar footer covered the list of recent chats and took the clicks meant for them. The bug was already in production.
- found Found by Qlane while it was testing a sidebar restyle that did not cause it, and filed as a GitHub issue from its report.
- confirmed Confirmed on production by a developer, who measured a scroll area 0 px tall holding 717 px of chats in a window 540 px tall.
- fixed Fixed in its own pull request.
- re-tested Re-tested by Qlane, which tested the first commit of the fix and flagged a sideways-scroll flaw the developer’s own review had already fixed in the next commit. It then passed the next commit.
A filter menu that only worked with a mouse
After Enter, focus stuck on the menu’s container, so arrow keys, Enter and Tab did nothing. A keyboard user could not pick a filter.
- found Found by Qlane, which tried the menu with the keyboard alone. The pull request’s text said nothing about keyboards at the time. Qlane recorded where focus went after each key, compared a menu that worked, and rated it major.
- confirmed, fixed Confirmed and fixed before merge, with a keyboard-only test.
- not re-run Not re-run by Qlane after the fix.
The run behind cases 01 and 03 also set aside one console error, already seen on an earlier pull request without the change.