Manual and automated testing in one test record, with native reporters for the frameworks you already run. Probara starts free, bills per user with no minimum, keeps read-only users free, and works fully in Spanish.
IncludedAuthenticator app, every plan; owners can require it
Not availableNot documented in user settings
Audit log
IncludedExport on Enterprise
PartialServer only, as log output
SOC 2 or ISO 27001 report
Not available
IncludedSOC 2 Type II
Pricing
Allure TestOps lists $39 per user per month for both Cloud and On-premise, with volume pricing for larger teams; the cloud starts at one user, on-premise at five, and read-only guests are free. Probara is priced per user from the first seat, with a free plan for small teams.
Probara
Free
$0
up to 3 users
Pro
$24
per user per month, billed annually
$30 billed monthly
Enterprise
Custom
pricing and terms for advanced procurement, security or support needs
How does Probara’s pricing compare with Allure TestOps?
Probara’s Pro plan costs $24 per user per month billed annually. Allure TestOps lists $39 per user per month for both Cloud and On-premise, and has no free plan. Probara bills per user from the first seat, with no seat minimum and no packs, and on Pro, read-only viewers never take a seat, so the people who only follow results cost nothing; Allure TestOps Cloud also starts at one user with free read-only guests, while On-premise needs at least five full-access licenses. Probara also has a Free plan for 3 users and 3 projects, and every new organization starts with a 14-day Pro trial, with no credit card.
Can I bring my test cases over from Allure TestOps?
Yes, through a spreadsheet. Probara imports test cases from CSV and XLSX files laid out in its import template, with their suites and steps. Pull your manual test cases out of Allure TestOps, for example through its REST API, arrange them to match the template described in the CSV import guide, and import the file into a project. Automated tests come in through Probara’s reporters, which create the cases a report names. If you would rather have Probara read an Allure TestOps export as it is, or bring over anything else, ask for it with Send feedback in your profile menu in the app, or through the contact page before you sign up, and the team adds support for it.
How do my automated results reach Probara?
Add the Probara reporter for Playwright, Jest, Cypress or Vitest next to the Allure one: each CI run lands in a test run with its attachments, and the cases a report names that do not exist yet are created. Any other framework can send JUnit XML through the open-source Probara CLI. With GitHub, Probara can also launch GitHub Actions workflows from a run and post a results comment on pull requests. All of this is on the Pro plan. Allure has adapters for more frameworks, so check yours before you switch.
Do manual and automated tests live together in Probara?
Yes. Manual and automated cases share the same suites, test plans and runs, and the defects they produce are linked to the results and cases behind them. On Pro, PQL, Probara’s query language, selects, groups and aggregates across cases, runs, results and defects, as a table or a chart you can save.
Does Probara work with Jira?
Yes, with Jira Cloud on the Pro plan: create Jira issues from defects and failed results with their steps and evidence, keep status in sync both ways, link issues to the test cases that cover them, and build coverage reports from them.
Can AI agents work in Probara?
Yes. Probara’s MCP server, with 270+ tools and operations, reached through up to 14 tools listed by default, lets Claude, ChatGPT, Cursor and other MCP clients write test cases, start runs, record results and file defects, with the same permissions as the person who connected them. It is included on every plan, Free included, and it is not a beta: the Allure TestOps MCP server is a public beta that Qameta notes may carry additional fees in future releases.