Skip to content

Tessa testing companion

Test coverage in minutes, owned by your whole team.

Self-healing end-to-end tests in plain 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.

Take the product tour Request access
  • 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 plain-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

Plain-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
Edit amount was observed but never activated

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 plain-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 plain-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 recording for every target type
  • 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

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 plain-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
05plain-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 plain 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

Deployment

Deploy on your terms.

Run Tessa's server, browser UI, and device executors in your environment. Isolate data by organisation and connect the model provider or compatible endpoint your team approves.

Your identity
Enterprise single sign-on (SSO) included for free
Your environment
Docker or Kubernetes deployment
Your devices
Executors beside physical and virtual targets
Your models
Supported providers or an OpenAI-compatible endpoint

Editions

Choose how Tessa runs.

The same Tessa, managed by us or self-hosted by you.

Tessa Sovereign

Most control

Self-hosted deployment

Run the complete Tessa stack in your environment and keep services, test data, and evidence under your control.

  • Everything in Tessa Cloud, running in your infrastructure
  • Bring your own supported AI provider, including self-hosted endpoints
  • Custom branding available
  • Tailored identity, network, and device integration
  • Additional deployment and operational support

Designed for FINMA-regulated environments with customer-controlled infrastructure and data flows.

Discuss Sovereign deployment

Tessa Cloud

Managed Tessa

Use the same Tessa workflow in a managed cloud workspace without operating the server yourself.

  • Hosted server and browser UI
  • Managed access to supported AI models
  • Shared scenarios, plans, schedules, and run history
  • Run on the test devices you already own: Android, iOS, web, and desktop
  • CLI integration for CI/CD
  • Guided onboarding

Available now. Access is provisioned on request.

Request Cloud access

FAQ

Common questions.

What can Tessa test?

Tessa tests Android and iOS apps, web applications, and desktop targets you explicitly enable. Targets run on physical devices, local or remote virtual devices, and browsers.

Do scenarios require code or selectors?

No. Scenarios use plain-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?

With Tessa Sovereign, yes: connect a supported provider or OpenAI-compatible endpoint inside your deployment. Tessa Cloud uses a managed set of supported models, with usage billed through Ernst & Conte.

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.

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.

Is Tessa Cloud available?

Yes. We provision the managed workspace on request and help connect your testing targets, including the physical devices your team already owns.

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. Recording can be enabled for every target type.

Get started

Bring us a real flow.

We will show you how Tessa maps, tests, and reports one real flow from your product, then discuss the deployment that fits your organisation.