Every ticket, verified in a real browser.
Priset Veritas reads the Jira ticket, learns your website, plans the tests with your team and runs them. You get exactly what passed, what failed and why, with a screenshot of every step.
- ✓Valid code reduces the order total
- ✓Codes are not case-sensitive
- ✓A second code replaces the first
- ✕Expired code shows a clear error
From ticket to verdict
Reads the ticket
Pulls the description, acceptance criteria and the latest comments from Jira, then states the requirement as testable rules.
Learns the website
Explores your site on its own and writes a guide to its pages, menus, forms and flows. Each website keeps its own documentation.
Plans with you
Proposes test cases, including the negative and edge cases people skip. Tell it where to focus; untick what you don't need.
Tests and reports
Runs each test in a real browser, step by step, and reports bugs with expected and actual results. Post them straight back to Jira.
Built for how QA teams actually work
Every organization gets its own private space. Inside it, each team owns its websites, documentation, test accounts and results.
- Teams with their own resources
- Websites, docs, test accounts, runs and CI tokens belong to a team. Other teams can't see them.
- A vault for test accounts
- Team admins store usernames and passwords once. Testers pick an account by name and never see the password.
- Documentation that keeps itself current
- Site guides update when the site is re-explored, and every run adds what it learned. Ten versions of each document are kept.
- Focus instructions
- "Only test the discount box. Try expired and lowercase codes." Veritas plans and tests inside that scope.
- Your AI provider
- Use Claude or OpenAI with your organization's own API keys and model choice.
- CI and Jira automation
- Team API tokens let your pipeline start a verification run whenever a ticket moves to QA.
Enterprise controls, on by default
Isolation
Every request is checked against organization and team membership. Data, screenshots and docs are scoped to the team that owns them.
Encryption
Test account credentials, API keys and 2FA secrets are encrypted with AES-256-GCM, using a separate data key for each organization, wrapped by a master key you can rotate.
Credentials stay out of the AI
The AI types placeholders. Real usernames and passwords are filled in inside the browser and redacted from everything the AI sees.
Access control
Organization roles (owner, admin, member) and team roles (team admin, tester, viewer). Two-factor sign-in, which you can require, plus account lockout and idle timeouts.
Audit trail
Sign-ins, invitations, role changes, vault use, settings changes and every run are logged and exportable as CSV.
Guardrails
Allowlists of the sites each organization and team may test, usage limits, data retention, and an agent that never logs out, deletes or pays.