Everything Probara does, written down.
57 product guides and the full integrator reference — the API, the MCP server, and what is still planned.
Start here
Get an account and reach your first project.
- Getting startedCreate an account and reach your first project.
- AuthenticationSignup, login, verification, and password reset.
- User profileEdit your name and role label from the account area.
- NotificationsWhat triggers a notification, where it shows up, and how to control it.
- Delete your accountPermanently delete your account, and what stays in your organizations.
Organization
Who is on the team, what they can do, and how the workspace is shaped.
- OrganizationsTenancy, roles, and organization settings.
- WorkspaceMembers, invitations, and workspace administration.
- Workspace activityOrganization-wide audit feed for owners and admins.
- Workspace usageSee your organization's live API-result, storage, and seat consumption in one place.
- InvitationsInvite teammates and accept invitations.
- Custom fieldsDefine metadata fields and project scope for test cases.
- TagsManage the shared tag vocabulary for test cases, defects, and test runs.
- Single sign-onVerify a domain, connect Google, an OpenID Connect provider or SAML, and require SSO for your organization.
- SCIM provisioningEnable SCIM for your identity provider, create and rotate its tokens, and revoke them.
- Delete an organizationSchedule a deletion, cancel it during the 14-day grace period, and what is erased.
Test repository
Projects, suites, cases, steps, and the files attached to them.
- ProjectsThe project directory, its health metrics, and project settings.
- Test repositorySuites, cases, steps, and the repository UI.
- Shared stepsReuse one sequence of steps across many test cases, edit it once, and keep runs frozen.
- Parameterized test casesRun one case against several data sets: parameters, shared parameters, excluded combinations, and runs that show each combination.
- Gherkin test casesWrite steps as Given, When, Then, choose the format per case or project, and import or export .feature files.
- Syncing feature files from GitKeep .feature files in Git as the source of truth: sync their scenarios from CI and send Cucumber results onto the same cases.
- Test case reviewSend new test cases and changes to existing ones for review before they reach the repository.
- Repository filteringSearch and filter test cases across every suite from the filter bar.
- Duplicating cases and suitesCopy a case or a whole suite subtree, optionally into another project.
- Import test casesBring an existing suite in from a Probara export, Qase, TestRail, or a Gherkin .feature file.
- CSV import walkthroughBuild or adapt a CSV that imports cleanly, with a downloadable example file.
- Restoring archived casesFind archived cases in Trash and restore them to the repository.
- AttachmentsMonitor storage usage and bulk-delete files across every attachment surface.
- Test case commentsDiscuss a case in threads, pin key context, and mention teammates.
Planning
Where you deploy, what varies, which cases you run, and the checkpoints they answer to.
- EnvironmentsProject-scoped deployment targets you attach to runs and reports.
- ConfigurationsReusable axes of variation — browser, operating system — for matrix planning.
- Test plansNamed selections of cases you curate once and generate runs from.
- MilestonesSprints, releases, and delivery checkpoints that runs roll up into.
Execution
Running tests, recording what happened, tracking what broke, and reading the result.
- Test runsPlan and track test execution.
- Execution panelCreate a run and work through its cases in the slide-over panel.
- Retrying a test caseReset a marked case while keeping past attempts in the Retries tab.
- Viewing past attemptsReopen completed marks from the Retries tab or per-case disclosure.
- DefectsTrack bugs across test runs, filter the project list, and review linked attempts.
- Coverage matrixThe latest result for every case in every environment, in one grid.
- QueriesAsk your own questions of your test data, read the answers, export them, and save the queries you reuse.
- Probara Query Language (PQL) referenceEvery entity, field, operator, function, limit and error of Probara Query Language (PQL), with worked examples.
- DashboardsCreate organization dashboards, add widgets, and choose who sees each one.
Integrations
Connect Probara to the tools your team already tracks work in.
- Jira Cloud integrationInstall the Probara app in Jira, connect a Jira site, and map projects.
- Jira issues from defectsCreate or link Jira issues from defects, and see what syncs in each direction.
- Traceability with JiraLink test cases to Jira stories and epics, and build traceability reports of the requirements they cover.
- The Probara panel in JiraWhat Jira users see on an issue, who can see it, and linking test cases from Jira.
- GitHub integrationInstall the Probara GitHub App, link issues to test cases, runs and defects, create issues from failures, and keep defect status in sync.
- Running tests with GitHub ActionsLaunch an automated run in GitHub Actions from Probara, set up the workflow and its secrets, and follow the build from the run.
- Reporting from CI with JUnit XMLCreate the app token your CI pipeline reports with, and manage it from the JUnit XML card.
- Reporting from CI with PlaywrightCreate the app token the Probara Playwright reporter signs in with, and add the reporter to your Playwright configuration.
- Reporting from CI with JestCreate the app token the Probara Jest reporter signs in with, and add the reporter to your Jest configuration.
- Reporting from CI with CypressCreate the app token the Probara Cypress reporter signs in with, and register the reporter in your Cypress configuration.
- Reporting from CI with VitestCreate the app token the Probara Vitest reporter signs in with, and add the reporter to your Vitest configuration.
- Reporting from CI with CucumberCreate the app token the Probara Cucumber reporter signs in with, add the reporter to your cucumber.js, and sync your .feature files.
- Outgoing webhooksSend project events to your own endpoints, signed and retried, from the Webhooks tab.
Administration
Plans and organization-wide controls.
For developers
The integrator surface: REST API, MCP, and CI.
- API reference (v1)Every /api/v1 endpoint, browsable against the live OpenAPI document.
- AuthenticationAPI keys, and how a request proves which organization it belongs to.
- MCP serverGive an AI agent the same operations your team uses, over Model Context Protocol.
- MCP tool referenceEvery tool an agent can call, with its arguments and return shape.
- Outgoing webhooksThe event catalog, the payload envelope, and how to verify each signed request.
- SCIM provisioningThe provisioning endpoints, filters, PATCH shapes, roles and limits an identity provider uses.
- CI integrationsReporting results from a pipeline: the CLI, or the Playwright, Jest, Cypress, Vitest and Cucumber reporters.
- Playwright reporterEvery Playwright attempt, with its steps, attachments and parameters, sent to a run.
- Jest reporterEvery Jest attempt sent to a run, and only the tests of a run when you ask for it.
- Cypress reporterEvery Cypress attempt, with the screenshot of each failure, sent to a run.
- Vitest reporterEvery Vitest attempt and repeat, with its steps and attachments, sent to a run.
- Cucumber reporterEvery Cucumber scenario and step, with its attachments, sent to a run and linked to its synced case.
- CLIReporting JUnit XML and Cucumber JSON files, and syncing .feature files from CI with an app token.
Nothing filed here yet
No guide matches this topic yet. Clear the filter to see the whole register.
Can't find it?
Tell us what you came looking for and we will write it.
Support requests are coming soon — the form is not wired up yet.