Skip to content

Tessa testing companion

Test coverage in minutes, owned by your whole team.

Self-healing end-to-end tests in natural language, with no selector code and no hours of automation work. Every run captures step-by-step evidence and feeds the App Map, living documentation of your application.

  • Tessa drafts, you approve
  • Self-healing replays
  • Self-hosted or managed
  • Android
  • iOS
  • Web
  • Desktop

Time to coverage

Your first scenario in under five minutes.

Our estimate: a new Tessa user creates and reviews a straightforward test scenario in under five minutes. The same case as a Playwright test, specified, implemented, and reviewed, takes around four hours because it crosses several people. On a mature project without automation the gap widens: a traditional test stack takes days to stand up, while Tessa connects in under 30 minutes.

< 5 minCreate and review a Tessa scenario
4 hrSpecify, implement, and review a Playwright test
< 30 minConnect Tessa to a mature project
DaysSet up traditional test automation on a mature project
Maintenance is a review.

When behaviour changes, revise the natural-language steps instead of maintaining selector scripts. Every change stays versioned.

Interactive product tour

Follow a complete testing flow.

Explore the transfer flow in MyBänkli, our demo banking app. Open the uncovered interaction, review Tessa's draft, run it, and inspect the evidence.

Open the interactive demo in a new tab

One connected system

Natural-language scenarios. End-to-end test runs. Solid evidence.

The core of Tessa: your team describes flows as scenarios, Tessa runs them, and every result comes with evidence. Along the way, each run grows the App Map — and shows you what is still untested.

Describe

You describe the flow. Tessa runs it.

A scenario describes a user flow the way you would explain it to a new team member: preconditions, steps, and expected results. No selector code. Tessa drives your application from that description and verifies every step.

  • Anyone on the team can write, read, and review scenarios
  • Import existing cases from Jira, spreadsheets, or plain notes
  • Watch runs live or review the results later
Scenario / MyBänkli Running

Send money to a saved recipient

01
Log in as the demo userPassed
02
Start a transfer from the Everyday accountPassed
03
Send CHF 240.00 to Anna KellerExecuting with Tessa
04
The review screen shows recipient and amountWaiting

Understand

A map of your application, drawn from real runs.

Every scenario run, replay, and exploration with Tessa feeds the App Map. Tessa groups observed screens, connects their transitions, and shows which scenarios cover each one.

  • Inspect screens or follow complete flows
  • Compare observed behaviour across platforms and builds
  • Explore with Tessa Assistant and keep what it observes in the App Map
App Map / MyBänkli4 of 8 screens
Log in1 scenario
Accounts3 scenarios
Transfer1 scenario
Review1 gap found

Close the gaps

Turn observed gaps into reviewed scenarios.

Unused interactions, uncovered screens, and dead ends become explicit gaps. Ask Tessa for a scenario draft, then accept, refine, or decline it before it enters your library.

  • Start from an observed gap, a natural-language goal, or Tessa's own exploration
  • Structured preconditions, steps, and expected outcomes
  • A human reviews every draft before it becomes coverage
Scenario draftTessa

Edit transfer amount before approval

01
Open Everyday accountAccount details are displayed
02
Start a new transferTransfer form opens
03
Continue to reviewRecipient and amount are preserved
04
Select Edit amountThe form reopens with existing values
RefineAccept scenario

Run everywhere

Run where your product runs.

Run natural-language scenarios on Android, iOS, web browsers, and desktop targets you enable. Watch the target live while Tessa works. Successful runs can become deterministic replays; when a replay diverges, Tessa takes over.

  • Single scenarios, test plans, batches, and schedules
  • Real devices, emulators, simulators, browsers, and desktop targets
Live run / Android Running
  1. 01
    Launch MyBänkliPassed
  2. 02
    Open transferPassed
  3. 03
    Edit amountExecuting with Tessa
  4. 04
    Verify reviewWaiting
MyBänkli

Review transfer

CHF 240.00 Confirm transfer Edit amount

Prove

Evidence your team can inspect and your CI can consume.

Review step status, expected and observed behaviour, screenshots, and application logs in one report. Enable a recording for any target, create self-contained browser reports for sharing, or emit CI-friendly result formats from the CLI.

  • Failure evidence tied to the exact scenario step
  • Android logcat, iOS console, and web console output
  • Optional run recordings
  • Self-contained HTML and JSON report exports from the browser
  • JSON, JUnit, Markdown, and HTML result formats from the CLI
Test run / EvidenceFailed

Failure evidence / Step 5

Edited values were not preserved

Expected

Recipient and amount remain filled after returning to the form.

Observed

The form reopened with both values cleared.

App bugHigh confidenceAndroid 15
Captured after step 5

Integrations

Failed runs become GitHub or GitLab issues.

Connect the Tessa GitHub App or your GitLab instance and a failed run turns into a drafted issue: title, description, and the affected scenario, taken straight from the report. Review and file it yourself, or let Tessa manage issues on its own — every action is documented on the issue with its reason.

01

Drafted from the report

Tessa proposes the issue from the failed run, so the details are already in place when you review it.

02

Duplicates become comments

When a known failure shows up again, Tessa comments on the existing issue instead of opening a new one.

03

Regressions flagged automatically

When a failure returns after its issue was closed, Tessa marks the run as a regression.

04

GitLab included

Connect gitlab.com or your self-managed instance with an access token; the integration layer is provider-neutral by design.

Results in context

See what changed and what needs attention.

Tessa connects current results with run history, scenario versions, and tested builds, so your team spots patterns and sees where a closer look pays off.

01

Triage the latest results

The dashboard separates results that need attention from flaky, live, and passing runs across one app or all of them.

02

Separate flakes from regressions

Recent pass/fail history by scenario and platform helps your team distinguish intermittent failures from consistent regressions.

03

Compare builds with context

Build Compare groups regressed, fixed, new, and unchanged scenarios and shows whether the scenario definition changed too.

04

Ask Tessa about your testing history

Ask Tessa can query trends, compare builds, assess flakiness, and retrieve the relevant reports and failure evidence.

Get started

See it on a flow you own.

Bring one real flow from your product and watch Tessa map, test, and report it, live.

Request a live session

Workflow comparison

From intent to reliable coverage

A typical code-based Playwright workflow crosses business intent, documentation, application changes, automation code, infrastructure, and ongoing maintenance. Tessa keeps the same journey in five natural-language steps one person can own.

Same starting point

Agreed intent, representative test data, and a testable target with usable accessibility or automation surfaces.

07steps across roles, tools, and code Code-based PlaywrightEvery handoff adds waiting time
  1. 01
    Agree on intentBusiness + QA
  2. 02
    Document the caseQA
  3. 03
    Add stable test IDs or accessible semanticsDev + Automation
  4. 04
    Walk the flow and choose locatorsQA / Automation
  5. 05
    Code the steps, assertions, and fixturesAutomation / Dev
  6. 06
    Debug runs and wire up CIDev + CI
  7. 07
    Maintain locators, code, fixtures, and docsQA + Dev
05natural-language steps With TessaOne person, start to finishBusiness / QA / Dev
  1. 01
    Pick a flow or an observed gap
  2. 02
    Describe the intent in natural language
  3. 03
    Review Tessa's draft
  4. 04
    Run it and inspect the evidence
  5. 05
    Revise the steps when behaviour changes
What Tessa can reduce
  • Selector codeNo hand-written locator scripts
  • HandoffsOne shared Business / QA / Dev workflow
  • Duplicate documentationThe reviewed scenario is the executable record
  • Cross-layer updatesRevise intent, then rerun

No vendor lock-in

Your devices. Your AI. Your data.

Tessa runs on the devices you already own, with the AI provider you choose, and lets you take everything with you, any time.

Your devices
Your own executors, phones, simulators, browsers, and desktop targets. Unlimited, no per-device fees.
Your AI
Your own API key for a supported provider or an OpenAI-compatible endpoint. The model stays with you.
Your data
Scenarios are plain Markdown, and one click exports your whole organisation — reports, screenshots, logs, and recordings included — as machine-readable JSON.
Your infrastructure
Tessa Sovereign runs the complete stack with Docker or Kubernetes. Enterprise SSO with Enterprise and Sovereign.

Editions & pricing

Tessa Cloud for you or your team. Tessa Sovereign in your infrastructure.

Sign up and the free 14-day trial runs on Team. No credits, no run limits, no per-device fees. Sovereign is the same product, self-hosted with Docker or Kubernetes.

Tessa CloudHosted by us in the EU. No credits, no run limits, no per-device fees. Tessa SovereignSelf-hosted
Compare
Solo
For one person
CHF 25
per month, incl. VAT
≈ €27 / $31
Start free trial
Team Recommended
For your whole team
CHF 480
per month, incl. VAT
≈ €510 / $600
Start free trial
Enterprise
Cloud at your scale
Custom
priced on request
 
Talk to us
Sovereign
Self-hosted in your infrastructure
Custom
priced on request
 
Talk to us
People who can sign in 1 Custom Unlimited
Projects 1 Unlimited Unlimited
Parallel runs 1 Unlimited Unlimited
Own executors & devices Unlimited Unlimited Unlimited
Shared workspace & history One person Included Included
AI provider Your own key Your own key Your own or self-hosted endpoint
Hosting EU, operated by us EU or Switzerland, operated by us Your infrastructure
Sign-in Google or GitHub Enterprise SSO Enterprise SSO
Cloud device fleet On request On request
Billing Monthly, cancel any time Custom Custom
Free trial 14 days on Team, no card Talk to us Talk to us
Tessa Cloud · hosted by us
SoloFor one person CHF 25per month, incl. VAT≈ €27 / $31
People who can sign in1
Projects1
Parallel runs1
Own executors & devicesUnlimited
Shared workspace & historyOne person
AI providerYour own key
HostingEU, operated by us
Sign-inGoogle or GitHub
Cloud device fleet
BillingMonthly, cancel any time
Free trial14 days on Team, no card
Start free trial
EnterpriseCloud at your scale Custompriced on request
People who can sign inCustom
ProjectsUnlimited
Parallel runsUnlimited
Own executors & devicesUnlimited
Shared workspace & historyIncluded
AI providerYour own key
HostingEU or Switzerland, operated by us
Sign-inEnterprise SSO
Cloud device fleetOn request
BillingCustom
Free trialTalk to us
Talk to us
Tessa Sovereign · self-hosted
SovereignSelf-hosted in your infrastructure Custompriced on request
People who can sign inUnlimited
ProjectsUnlimited
Parallel runsUnlimited
Own executors & devicesUnlimited
Shared workspace & historyIncluded
AI providerYour own or self-hosted endpoint
HostingYour infrastructure
Sign-inEnterprise SSO
Cloud device fleetOn request
BillingCustom
Free trialTalk to us
Talk to us

Your 14-day trial runs on Team, no card required. Choose Solo or Team when it ends. We bill in CHF; euro and dollar amounts are approximate. Sovereign is designed for FINMA-regulated environments with customer-controlled infrastructure and data flows.

Full pricing and FAQ

FAQ

Common questions.

What can Tessa test?

Tessa tests Android and iOS apps, web applications, and desktop targets you explicitly enable — from Electron apps to classic Java desktop software. Targets run on physical devices, local or remote virtual devices, and browsers.

Do scenarios require code or selectors?

No. Scenarios use natural-language preconditions, steps, and expected outcomes. Tessa drives the target through its available accessibility and automation tools instead of asking testers to maintain selector scripts.

How does the App Map stay current?

Observations from Tessa runs, deterministic replays, and Tessa Assistant explorations are folded into the App Map. Tessa groups stable screens, records transitions, and recalculates coverage gaps from the observed state.

Can we use our own AI provider?

Yes. With Tessa Cloud, connect your own API key for a supported AI provider. With Tessa Sovereign, connect a supported provider or OpenAI-compatible endpoint inside your deployment.

Can Tessa run inside our infrastructure?

Yes. The server, browser UI, and executors can be deployed in your environment, with application data scoped by organisation.

Can we take our data with us?

Yes, with one click. An organisation owner can export the complete organisation at any time: scenarios with their version history, test plans, schedules, the App Map, settings, integrations, members, and full reports including screenshots, logs, and recordings — one ZIP archive of machine-readable JSON. The export works in every organisation state, even after you cancel.

Does Tessa support enterprise SSO?

Enterprise single sign-on is part of the Enterprise plan and of Tessa Sovereign. Solo and Team use Google or GitHub sign-in.

Is Tessa Sovereign suitable for FINMA-regulated environments?

Tessa Sovereign is designed for them: services, test data, and evidence remain on customer-controlled infrastructure, and a self-hosted AI endpoint allows the deployment to be configured for fully internal operation. This is an architecture claim, not FINMA certification or approval; final compliance depends on the institution's configuration and controls.

Does Tessa integrate with GitHub or GitLab?

Yes. Install the Tessa GitHub App, or connect GitLab with an access token (gitlab.com or self-managed), and Tessa drafts issues from failed runs, comments on the existing issue when a failure reproduces, and flags a run as a regression when a closed issue's failure returns. You can also let Tessa open, comment on, and close issues autonomously; every action is documented on the issue with its reason.

How does the free Tessa Cloud trial work?

Open the sign-up page and sign in with Google or GitHub. Your workspace is provisioned automatically within a minute, no credit card required. Connect your own API key for a supported AI provider and use Tessa Cloud free for 14 days on the Team plan. When the trial ends, choose Solo or Team and add your card in the billing portal; from then on your organisation is billed monthly, including VAT. Without a card, nothing is charged.

What does Tessa Cloud cost?

Tessa Cloud has two plans, billed monthly and including VAT: Solo for one person with one project and one parallel run, and Team for up to six people with unlimited projects and unlimited parallel runs. The current prices are in the plan table above. Both include unlimited own executors and devices, your own AI provider key, EU hosting, and cancellation at any time; there are no credits, no run limits, and no per-device fees. Enterprise, with custom seats, enterprise SSO, and a cloud device fleet on request, and Tessa Sovereign, self-hosted in your own infrastructure, are priced individually.

How many people can use Tessa?

Every person who can sign in to your organisation's workspace counts. Solo is for one person, Team includes up to six people, Enterprise is custom, and Tessa Sovereign has no limit.

What counts as a project?

A project is one application you test with Tessa, with its own scenarios, test plans, runs, targets, and App Map across Android, iOS, web, and desktop. Solo includes one project; Team, Enterprise, and Tessa Sovereign have unlimited projects.

Where is Tessa Cloud hosted?

Solo and Team are hosted in the EU and operated by Ernst & Conte; Enterprise can be hosted in the EU or in Switzerland. Application data is isolated per organisation. Tessa Sovereign runs in your own infrastructure.

What evidence does a run preserve?

Reports include scenario-step results, expected and observed behaviour, screenshots, run metadata, and application logs: Android logcat, iOS console output, or web console output. A recording of the run can be enabled as well.

Get started

Bring us a real flow.

Request a live product walkthrough or a Sovereign deployment discussion. Tell us what you want to test and we will prepare the right next step. Want to try Tessa Cloud? Start your free trial directly, no request needed.