Solutions

Tesbo for QA engineers

Writing a test case is ten minutes of thinking and forty minutes of typing. Tesbo takes the forty minutes — and it drafts from a knowledge base of your actual product, not generic guesswork. You keep the ten minutes, and the final say over everything that lands in the repository.

Start freeSee pricing
  • Apache 2.0, self-hostable
  • No per-seat pricing
  • MCP server included
The problem

Most of a QA engineer’s week is data entry

The skill in this job is knowing what could break and designing the case that catches it. Almost none of the hours go there.

  • Preconditions and steps retyped for the fourth time this quarter
  • A regression pass that is mostly copy, paste, and renumber
  • Bug reports written twice — once in the tracker, once in the test run
  • Coverage nobody can describe without opening twelve folders
  • The interesting edge case skipped because the afternoon ran out
How it works

Test case management for QA engineers, from intent to approved case

  1. 1You describe

    One line of intent

    Name the behaviour you want covered. That is the whole input.

    Cover checkout when the saved card has expired
  2. 2Zyra drafts

    From your knowledge base

    It retrieves your own docs first, then writes steps and expected results.

    checkout-flow.md§4
    payments-api.yaml402
    3 cases drafted
  3. 3You decide

    Approve, edit, or discard

    Nothing reaches the repository without your name on it.

    ApproveEditDiscard
Why the drafts are relevant

The agent reads your product before it writes a word

You give it your product context. Tesbo keeps a hierarchical knowledge base of docs and files that is versioned and vector-indexed, and the agent retrieves from that when it drafts. The more of your real documentation lives there, the closer the first draft lands.

  • Versioned and vector-indexed, per project
  • Retrieved at draft time, not trained on months ago
  • Self-hosted, the index stays on your infrastructure

Pick a source to see what the agent drafts from it

Knowledge baseTESBO-COREIndexed
Context retrievedcheckout-flow.md

“§4 Guest checkout — the expiry field is validated in the browser before any payment call is made.”

“§4.2 A rejected card must leave the cart untouched, including quantities.”

DRAFTEDSaved card past expiry is rejected before payment
#ActionExpected result
1Open checkout with an expired saved cardExpiry flagged on the card row
2Submit the orderInline error, no payment request sent
3Return to the cartBoth items present, quantities unchanged
Edge case proposed: expiry falls in the current month

Draft a full case from one line of intent

Describe the behaviour you want covered. Zyra returns the preconditions, the steps, the expected results, and the edge cases it thinks you missed — grounded in a vector-indexed knowledge base of your own product docs, so the output reads like your suite rather than a template.

  • Steps and expected results, not a paragraph you then reformat
  • Grounded in your requirements and docs, not generic guesswork
  • Edge cases proposed, never silently added
  • One user story in, a whole set of cases out

Nothing enters your suite until you approve it

Every draft lands in a review queue. Accept it, edit it, or throw it away. This is the deliberate design decision in Tesbo, not a setting you can switch off — an agent writing straight into your repository is a liability, not a teammate.

  • Review before anything is saved, not a cleanup pass afterwards
  • Full version history on every case
  • Your name on the approval, so the audit trail is real

A failed step becomes a bug report you would have written

Mark a step failed and the report is drafted from the run itself — the case, the step, the expected and actual result, the environment, the evidence you attached. You read it, you send it. It stays linked to the failing case, so the next person sees the whole story.

  • Filed from the failed execution, not retyped into a tracker
  • Screenshots and logs attached where you captured them
  • Linked back to the case, and out to Jira or Linear

Bring your own agent, keep the same guardrail

Tesbo ships an MCP server, so Claude, Cursor, or an agent you wrote yourself can read the suite and propose cases without leaving your editor. Everything they submit goes through the same review queue a human draft does.

  • Works with any MCP client, including Claude and Cursor
  • Same human approval rules as Zyra — no back door
  • Every agent action in the audit log, attributed
.mcp.jsonCopy
{
  "mcpServers": {
    "tesbo": {
      "command": "npx",
      "args": ["-y", "@tesbo/mcp-server"],
      "env": { "TESBO_TOKEN": "$TESBO_TOKEN" }
    }
  }
}
claude ›propose_cases(suite: "Checkout", from: "PR #482")
tesbo ›2 cases queued for review · 0 written to the repository
The MCP server cannot write past the review queue
Moving in

Bring the suite you already have

Yes. Cases import and export as CSV or XLSX, so an existing spreadsheet or an export from another tool comes across in bulk rather than being retyped case by case.

Questions QA engineers ask

The same five come up in every evaluation. Answers, not positioning.

Ask us directly
Does the AI write test cases directly into my test suite?

No. Every case the agent drafts goes into a review queue first. A person accepts, edits, or discards it, and the approval is recorded against their name. That review step is the core design decision in Tesbo, not a setting you can turn off.

Can I still write test cases by hand?

Yes. Tesbo is a full test case management tool first — a nested repository with priorities and steps, versioning, runs, and reporting all work the same whether a case was typed by you or drafted by the agent.

How does the AI know anything about our product?

You give it your product context. Tesbo keeps a hierarchical knowledge base of docs and files that is versioned and vector-indexed, and the agent retrieves from that when it drafts. The more of your real documentation lives there, the closer the first draft lands.

Can I import the cases we already have?

Yes. Cases import and export as CSV or XLSX, so an existing spreadsheet or an export from another tool comes across in bulk rather than being retyped case by case.

Is there a free version for a single QA engineer?

Yes, two of them. The self-hosted Community edition is Apache 2.0 and free forever with no cap on test cases, and the Launch plan on Tesbo Cloud is $0 permanently rather than a trial. Neither one charges per seat.

Give the typing to the agent

Self-host the Community edition free, or start on Tesbo Cloud and keep your review queue in the browser. No seat math either way.

Start freeSelf-host it

Other roles

QA managersTesbo for QA managersAnswer “what’s covered?” without calling a standup. One repository holds every case, run, and result, so coverage is a view you open rather than a report someone assembles.Read more