"We deleted 4,000 snapshot tests. Then we wrote 300 from the spec…"
Example workspace
Click around a workspace.
This is Propel working on Specbot, an example product that turns specs into test suites. Everything is example data, and nothing you click sends anything. Approve drafts in the queue, watch a job at work, read results with their ranges, and see how far each channel may go. Follow the five-step tour, or explore on your own.
4 decisions waiting · 12 conversations started this week · cited in 7 of 20 buyer questions · read Monday · 6 posts out this week
We ship GitHub Actions support on Tuesday. Get us ready.
On it. I'll read what changed, check what AI assistants say about running spec tests in CI, write the launch thread and find QA leads who use GitHub Actions. That's about 180 credits.
Needs you
"Your team writes tests after the bug turns up. What if the spec wrote them first?"
The page ChatGPT, Claude and Perplexity are missing. Goes to your docs site.
"Can you show me how it handles flaky tests?" Your booking link is ready.
Get us ready for Tuesday's launch
- ✓Read what changed in the repo this week4s
- ✓Asked ChatGPT, Claude and Perplexity how to run spec tests in CI11s
- ✓Wrote 6 versions of the launch thread and ranked them1m 08s
- ✓Checked every claim and number against its source9s
- …Waiting for your yes on 4 piecesnow
This week, for Specbot
120 answers per engine · read Monday · ranges show where the true figure probably sits
Standing jobs
Later Standing jobs are not in the public beta. They switch on after it.
How far each channel can go
Limits read from the product's own rules. Steps are example progress.
Example product, people and numbers. The way it works, and the limits, are Propel's own.