Skip to content
probanda

Your QA bot. In your workflow.

Hand off a question or a ready code change. Get the checks, findings, and evidence back where your team already works.

Coming soon.

Guest checkout

Staging
Example task

Task conversation

You

Check guest checkout after this fix. Make sure customers can continue from the cart. Stop before payment.

Probanda

I’ll check one example item as a guest, on staging. No payment or account creation.

  1. Open the cartChecked
  2. Find the checkout buttonChecked
  3. Continue to checkoutBlocked
Probanda

Guest checkout is blocked. The button is disabled, so customers can’t continue.

Finding + evidence attached

The answer stays with the task.

Example QA reportFor the PR + issue

Checkout is blocked.

The button is visible but disabled. I stopped before payment.

Cart pageexample.com/cart
1 example item in your bag
disabled = true
Expected
Enabled
Observed
Disabled
expect(checkout).toBeEnabled()
Inspect example evidence
<button disabled>Continue to checkout</button>

The observed button state explains why this example check failed.

Example QA report.

Keep every check connected.

The request, the code change, and the result belong together. So the next fix doesn’t start from scratch.

Guest checkout on stagingExample workflow
Team conversationRequest
You

Check guest checkout on staging. Stop before payment.

Linked changeCheckout button fixcheckout-fix · a13f9c2
Or hand off the reviewed fix PR.

Hand off the check.

Start in a conversation, or let a configured workflow hand off a reviewed fix. The task keeps its original context.

What a request can include

The target environment, expected behavior, and where to stop. The intended bot asks when scope or permissions are unclear, rather than quietly expanding the task.

Checkout button fixScope
Review approvedTest environment ready
Check
Cart → guest checkout
Use
One example item
Stop
Before payment
Matching environmentstaging · a13f9c2

Test the agreed change.

Bring the acceptance criteria and the right environment into a scoped QA task. Keep the boundaries explicit.

Set the handoff rules

Planned controls would define allowed triggers, scope, permissions, and reporting destination. A development handoff waits for an approved review and a ready test environment for the linked fix.

ProbandaBlocked

Checkout is blocked.

The button is visible but disabled. The check stopped before payment.

Expected
Enabled
Observed
Disabled
Finding + evidence attachedrevision a13f9c2

Get evidence in context.

Receive the finding where the task started, linked to the change that was checked. Know what failed and where to look.

What belongs in a result

The relevant steps, expected and observed behavior, the tested change and environment, and anything still uncertain. Findings would return to the originating conversation, PR, or issue.

The next fix starts with context.

Keep the finding attached to the issue. When a new revision is ready, check it against the same agreed behavior.

Keep each result tied to its change

Each intended run is linked to the change and environment it tested. Evidence informs the next decision; a QA result does not automatically merge a PR or close an issue.

Guest checkout · same issueExample continuation
  1. Finding

    Checkout blocked

    a13f9c2

    Evidence stays with the fix.

  2. Revision

    A fix is ready

    b27e6d4

    Review approved. Staging ready.

  3. Retest

    Retest passed

    b27e6d4

    Checkout button enabled. Stopped before payment.

In the tools your team uses.

Connections are planned. Your team sets the scope, permissions, and handoff rules.

  • SlackConversations
  • EmailRequests
  • GitHubPull requests
  • LinearIssues

These examples show the experience we’re building. Slack, email, GitHub and Linear connections are planned.

Questions, answered.

What is Probanda?

Probanda is a QA bot designed to work across conversations and development workflows. Hand off a task or a ready code change, get scoped checks and evidence-backed findings, then carry the next fix into a retest.

Where can a task start?

Slack, email, GitHub and Linear are the planned entry points. Start with a request in a conversation, or use a configured workflow to hand a reviewed change to QA.

When would a code change be tested?

The intended handoff is an approved review and a ready test environment for the linked fix PR. Your team sets the scope and permissions. Merge and release decisions stay with your team.

Will I need another dashboard?

Everyday requests and findings should stay where the work happens. A companion workspace is planned for connections, rules, permissions and run history.

When can I use Probanda?

Probanda is coming soon. The examples on this page show the experience we’re building. Slack, email, GitHub and Linear connections are planned.

Take a closer look.

See how a task becomes a clear, evidence-backed answer.

Join the waitlist

Loading

Open form in a new tab