Specor for QA & Test Engineers
Tests written from intent, gated at the merge.
Specor turns acceptance criteria into test cases, writes Gherkin scenarios for every proposed merge from the real diff, and maps the regression blast radius — so nothing ships without a check.
Sound familiar?
Tests drift from the spec
Requirements change, tests don’t. You’re validating last quarter’s behaviour and calling it green.
Unknown blast radius
A change lands and you’re guessing what else it touched. Regression coverage is a gut feeling.
No gate before merge
By the time a defect is a bug report, it’s already in main. Prevention beats triage.
Specor ties every test back to a written acceptance criterion — and won’t let a merge through until the checks pass.
From acceptance criteria
One test per criterion — generated for you
Every feature in Specor carries explicit acceptance criteria. Specor generates a test case for each one, so coverage traces directly back to a written requirement instead of a tester’s memory.
When a criterion changes, you know exactly which test to revisit.
Feature · Guest checkout
- ✓AC: order under $200 needs no account → test_guest_under_limit
- ✓AC: over $200 prompts sign-up → test_guest_over_limit
- ✓AC: confirmation email sent → test_confirmation_email
Merge confidence
Gherkin scenarios for every proposed change
Open a merge and Specor writes Given/When/Then scenarios from the actual diff — not from a generic template. It also pulls in the two-hop neighbourhood of what changed, so you get regression coverage for the blast radius, not just the feature itself.
Testers can mark each scenario pass or fail — even from Cursor or Claude over MCP.
Scenario: Guest checkout under limit
Given a cart totalling $150
When the guest pays
Then no account is required
Blast radius: Cart, Payments, Email
The merge gate
Nothing merges until the checks pass
Test cases roll up into a pass/fail gate on the merge. A change with failing or unaddressed scenarios can’t be quietly waved through — the gate is explicit and visible to the whole team.
Meanwhile the Flow Consistency agent catches structural defects — unreachable steps, flows with no end state — before they ever reach a test run.
- ✓ 4 scenarios passing
- ✗ 1 scenario failing — over-limit sign-up
- ⚠︎ Flow “Checkout” has an unreachable step
A day with Specor
- 1
A developer opens a merge. Specor generates Gherkin scenarios from the diff and maps the blast radius.
- 2
You review the scenarios, add the edge case they missed, and run them against the build.
- 3
Mark each scenario pass or fail — the merge gate updates live. The failing one blocks the merge.
- 4
Fix lands, gate goes green, merge proceeds — with a permanent record of what was tested and why.
Work with other teams?
Specor is one shared source of truth — everyone reads the same product.
Gate every merge on tests that trace to intent
Start free — no credit card. Viewers are always free, so your whole team can read along.