Test cases that follow your PRs
7 months ago
Every PR generates Draft test cases automatically; merging promotes them to Active, closing without merge archives them. Your test library grows with your codebase.
When a PR opens, qlane reads the diff and generates Draft test cases for the changed behavior. They live alongside your existing cases in the Tests view, marked Draft so they don't pollute your active library until you've reviewed them.
When the PR merges, the Drafts auto-promote to Active — they're now part of the canonical test suite. When the PR closes without merging, they archive automatically. When the PR gets a new push, the previous Drafts archive and a fresh set generates from the new diff.
The end result: zero manual test-case maintenance. Every change you ship leaves behind tested behavior; nothing accumulates from changes you didn't ship.
PR #284
on merge
- Draft cases generated automatically from the PR diff.
- Draft → Active on merge; Draft → Archived on close-without-merge.
- Push to a PR? Old Drafts archive, new ones generate from the latest diff.