Integrates with your existing stack
Most teams are managing test cases in spreadsheets, sharing screenshots over Slack, and guessing at release readiness.
Spreadsheets, Confluence pages, Slack threads. No single source of truth for what's been tested.
Bug evidence lives in chat messages and email threads, not attached to the actual Jira ticket.
Release decisions made on gut feel. No coverage data. No visibility into what's still untested.
Stop re-running tests that already passed. Our inheritance engine carries forward verified results across builds automatically.
Screenshots are captured locally and uploaded directly to Jira. We never store your images — your storage bill stays at zero.
Connect GitHub Actions, GitLab CI, Bitbucket Pipelines, or Jenkins. Build events automatically trigger test planning.
Know exactly how much has been tested before you ship. Verified, pending, blocked, and new — all in one dashboard.
Push bugs to Jira with one click. Ticket status and links sync back in real time. No tab switching required.
Ingest automated test results, trigger runs programmatically, and subscribe to events via webhooks on Pro and Enterprise.
Link your Jira project and CI/CD pipeline. Perpetual Test syncs your releases and build history automatically.
Create test cases, organize them into sections, and assign coverage tags. Import from your existing spreadsheets.
Run tests, push bugs to Jira with screenshots, and get a release readiness score before every deploy.
No per-seat surprises. Teams pay for what they use.
For small teams getting started
Up to 3 users
For growing QA teams
1 lead required per 10 users — leads manage integrations & billing
Example pricing:
| Feature | Basic | Pro |
|---|---|---|
| Users | Up to 3 | Unlimited |
| Projects | 1 | Unlimited |
| Active Releases | 2 | Unlimited |
| Test Cases & Runs | ✓ | ✓ |
| Jira Integration | View-only | Full |
| Slack / Teams | — | ✓ |
| CI/CD Webhooks | — | ✓ |
| API Access | — | 1,000 calls/mo |
| Support | Priority |