Tester dashboard with a readable test suite, run output and attached mobile device

Tester 1.0.1 · On-prem software

Tester - on-prem test automation for web, API, Android and iOS.

Write one readable suite, run it against browsers, services and real devices, then keep the report and test data inside your network.

30-day evaluation · no runtime lock · two personal workstations · 30-day refund

4Web, API, Android, iOS
171Reviewable DSL steps
Local-firstOllama AI by default
SignedPackages, checksums and SBOM

Product

One test language, from intent to evidence.

Tester joins authoring, execution, device control and reports without hiding test behavior behind generated framework code.

Readable by design

The suite is the source of truth.

This is executable Tester syntax, not pseudocode. Suite data and case data combine as a cartesian product, while variables and generated values stay visible in the file that reviewers approve.

checkout_smoke.suite

# Checkout smoke
tags: web, smoke

| locale | input |
| --- | --- |
| en | checkout |
| tr | odeme |

## TC001 - Submit a web form
| choice | checkbox |
| --- | --- |
| One | Default checkbox |
| Two | Checked checkbox |

* Set variable "run_label" to "{{input}}-{{choice}}-${digits(4)}"
* Open URL "https://www.selenium.dev/selenium/web/web-form.html"
* Type "{{run_label}}" into "Text input"
* Select "{{choice}}" from "Dropdown (select)"
* Check "{{checkbox}}"
* Click "Submit"
* Verify "Received!" is visible on page
01

Infer only what the case needs.

Tester expands concepts, reads the registered steps and opens only the required Selenium, HTTP or Appium capabilities. A later replay no longer depends on the model that authored the suite.

WebSelenium browsers, DOM snapshots and download evidence

APIHTTP, OAuth2, OpenAPI contracts, schemas, PDFs and polling

MobileAppium, Android and iOS with screenshots and UI XML

MixedOne case can use several capabilities without target metadata

02

Lease devices and isolate every run.

Runner heartbeats, device leasing and per-project queues keep two jobs from taking the same phone. Artifacts, logs and Allure publication remain scoped to the exact project and run, including concurrent report regeneration.

SchedulingQueued work, retries, cancellation and drain controls

DevicesPhysical or emulated Android and iOS inventory

EvidenceCorrelation IDs, screenshots, source dumps and deterministic snapshots

03

Operate the appliance, not a collection of scripts.

Storage limits, retention, signed updates, backup and restore, audit search, support bundles, runner capacity and provider policy are managed from one server-enforced control plane.

Appliance storage and retention controls from the real Tester UI.
04

Fit the customer's identity boundary.

Project RBAC, OIDC and SAML login, SCIM provisioning, session controls, hashed tokens, encrypted write-only secrets and metadata-only audit records are built into the same appliance.

OIDC, SAML and SCIM administration from the real Tester UI.
05

Keep Jira aligned with the run.

Tester synchronizes the suite hierarchy and then applies Allure results back to the matching issues. Stable source and scenario labels keep updates attached when names change.

# Suite
Creates or updates the parent Jira Task.
## Test case
Creates or updates a Jira Sub-task with steps, data and tags.
Passed
Moves the Sub-task through the configured workflow to Done.
Failed or broken
Reopens when needed, moves to In Progress and attaches current failure evidence.
Parent status
Becomes Done only when every reported case passes; otherwise it remains In Progress.
06

Prove the exact run.

Allure reports retain the step trace beside screenshots, UI XML, DOM and API snapshots, logs and run metadata. Release packages add checksums, signatures and CycloneDX SBOMs.

Exact-run evidence and embedded Allure report from the real Tester UI.

Durable automation

The useful parts stay inspectable.

Tester keeps authoring, execution and operations explicit so a team can debug the system without a vendor-side black box.

Ground-truth locators

Accessible labels and project locators lead; DOM, page source and deterministic element indexes remain available for review.

Revision-safe project files

Suites, concepts and locators remain content truth, with ownership, optimistic edit checks and audit metadata enforced by the server.

Local-first generation

Ollama is the default. External providers require an administrator choice, an endpoint allowlist and the managed redaction boundary.

Deterministic replay

AI can propose a suite once; registered DSL steps execute the reviewed file locally on every later run.

Evidence by construction

Failures preserve screenshots, XML or HTML source, snapshots, request evidence, logs and the exact report identity.

Signed appliance lifecycle

Backups, retention, support bundles, signed updates, checksums and SBOMs support controlled on-prem operation.

AI provider choice

Local is the default, external is an explicit administrative decision.

Ollama works without sending prompts outside your network. Administrators may enable approved external providers behind an endpoint allowlist and redaction boundary. Test execution remains deterministic after generation.

Read AI provider configuration →

Inside your boundary

A control plane for teams that cannot send test data to a test SaaS.

Tester combines execution, identity, evidence and AI provider controls without turning deterministic test runs into model-dependent workflows.

01

One suite, four platforms

Selenium for web, a built-in HTTP client for APIs, and Appium for Android and iOS.

02

Project-scoped control

Server-enforced RBAC, OIDC/SAML, SCIM, session controls and metadata-only audit.

03

Local AI by default

Generate with Ollama or explicitly enable an allowlisted external provider with redaction controls.

04

Evidence that travels

Per-run reports, screenshots, UI snapshots and request evidence remain tied to the exact run.

05

Appliance operations

Backups, signed updates, rollback, retention policies and support bundles from one surface.

06

No expiry kill switch

A paid Tester 1.x license is perpetual. Support dates control updates, not whether existing tests run.

Product view

See the dashboard, runner and report in one minute.

Watch product demo

Tester 1.x

Own the major version. Keep running it.

€299 plus applicable taxes, once

One named user, up to two personal workstations, 12 months of feature updates, security support through at least 31 August 2031, and a 30-day refund.

Review purchase terms