Getting started

Install TITA Automation, record your first workflow, turn it into a test case, and run it on an agent — in a few minutes.

1. Install

Download the Windows installer and run it. It sets up three things:

Designer — the desktop app where you record, author, and run workflows.
Agent — the worker that executes runs (web & desktop).
Engine — the local orchestrator that stores workflows, test cases, and runs.

The installer is available from your portal after you register and pick a plan (the 30-day demo is free). Then log in and download it from your profile. Windows 10/11, 64-bit.

2. Sign in & pick a project

Open Designer and sign in. On the Start screen, choose your organization and project — or click New Project to create one. Everything you record is scoped to the selected project.

3. Record a workflow

Open the App/Web Recorder from the Designer ribbon.
Perform your task — clicks, typing, navigation — in a desktop app or browser.
Stop the recording and save it as a workflow.

4. Turn it into a test case

In the Test Explorer, create a test case from your workflow. Give it an expected status and optional input data sets, and drop it into a folder. The test case is the repeatable, verifiable face of your workflow.

5. Run it

Run from Designer, or from the web portal:

Pick an agent (or "any available agent") and toggle headless for web tests.
Watch status move Queued → Running → Succeeded live under Runs.
Open a run to see the step timeline, output log, and captured screenshots.

Headless vs. visible

Web/browser tests can run headless (no visible window) for speed. Desktop (Windows GUI) automation needs an interactive desktop session on the agent, so it runs visible.

Unattended runs pick for you. A run triggered from CI is headless by default — build agents have no desktop to show a browser on — and you can pass {"executionMode":"visible"} in the trigger body to opt out. A schedule has its own Headless (web) checkbox in Designer, off by default. Both apply to browser steps only; desktop steps always run visible.

Schedules

Attach a schedule to run a test case or workflow automatically — nightly regressions, hourly checks, and so on. Results appear in the portal like any other run.

Single sign-on (SSO) · Enterprise

Enterprise organizations can let their team sign in with the company identity provider over OpenID Connect (OIDC) — Okta, Azure AD / Entra, Google Workspace, and other OIDC providers. SSO is configured per organization and is off until an admin turns it on; password sign-in keeps working until then.

In the portal, an admin opens Settings › Single sign-on.
At your identity provider, create an OIDC web application (Authorization Code flow, confidential client) and register the redirect URI shown on that page:
https://api.titaautomation.com/api/sso/callback — scopes openid email profile.
Back in TITA, fill in your issuer URL, client ID and secret, and the email domain your team signs in with (e.g. acme.com). Optionally enable auto-provisioning to create accounts on first sign-in, and pick the default role.
Save and enable. Now anyone with an email at that domain can pick Continue with single sign-on on the login page and be routed to your IdP.

Issuer examples: Google https://accounts.google.com, Okta https://your-org.okta.com, Azure AD/Entra https://login.microsoftonline.com/<directory>/v2.0.

← Back to home