Skip to main content
Test Your App Now! (TYAN) verifies your application by executing real user journeys in a real browser against your live production URLs — not a staging clone, not a mocked API, and not a headless DOM simulation. Every run reflects exactly what a real user would experience if they visited your app right now. This section explains how each layer of the platform works, from building a flow to getting alerted when one breaks.

​
Building flows

You define flows using the visual, step-based flow builder. Each flow is a sequence of actions that mirrors a real user journey through your application. You don’t need to write code to get started — pick step types from the builder, configure them with a URL, selector, or expected value, and arrange them in order. Available step types cover the full range of browser interactions:
  • Navigate — load a URL and wait for the page to be ready
  • Click — interact with buttons, links, and any other clickable element
  • Fill field — type into text inputs, textareas, and select menus
  • Assert text — confirm that a string appears anywhere on the page
  • Assert element — verify that a specific element exists and is visible
  • Wait — pause for a set duration or until a condition is met before proceeding
Flows are versioned and shareable. You can duplicate them, parameterize them with environment variables (for example, to run the same flow against multiple environments), and export them to share with teammates or clients as acceptance evidence.

​
Running in production

When you trigger a run — manually, on a schedule, or via the API — TYAN spins up an isolated browser session and executes your flow against the target URL. Each run is fully isolated from every other run: there is no shared state, no cached sessions, and no leftover data from a previous execution. This means your results are always an accurate reflection of a fresh user visit. During execution, the platform captures a detailed trace of every step:
  • Pass/fail status per step with timing data
  • Screenshots at every step and a full-resolution capture at the point of failure
  • Console logs and network errors surfaced alongside the step trace for faster debugging
  • A shareable run report you can send to a client, a teammate, or a stakeholder without giving them platform access
Because flows run against real production URLs with real network conditions, you catch failures that never appear in unit tests or staging — broken third-party integrations, CDN misconfigurations, environment-specific bugs, and race conditions all show up here. Trigger a run from your CI/CD pipeline before every release and you have a definitive green or red signal on whether the critical paths still work — no manual retesting required.

​
Continuous monitoring

Scheduled monitoring is where TYAN becomes a safety net rather than a one-off check. Set a recurrence on any flow and it runs automatically at your chosen interval:
  • Every 5 minutes for your most critical journeys
  • Every 15 minutes or hourly for secondary flows
  • Daily or on a fully custom cron schedule for lower-priority paths
Every scheduled run is logged in your run history so you can track reliability over time and spot trends before they become incidents. When a run fails, TYAN fires an alert immediately through your connected channels — Slack, email, or an outbound webhook to route notifications anywhere you need them. When the flow recovers on a subsequent run, a recovery notification is sent automatically so you always know the current state without having to check the dashboard.
Alert fatigue is a real problem. TYAN sends one failure alert when a flow first breaks and one recovery alert when it passes again, rather than firing on every failed run in between. You stay informed without being overwhelmed.

​
Acceptance testing

TYAN flows are a natural fit for acceptance testing because they describe exactly what a user can do — not how the code is structured. To use them as acceptance gates, translate each acceptance criterion in your requirements into one or more flow steps, then run the flow against the delivered application. A flow that passes is objective, reproducible evidence that the feature works as specified. You can share the run report directly — no QA handoff, no manual spot-check, no ambiguity about what was tested and what the result was. Run the same flow on every merge to make acceptance a continuous gate rather than a one-time sign-off.
Start with your most critical user journey — for most applications that’s signup or checkout. A single well-defined flow covering that path gives you more confidence than dozens of unit tests, because it proves the whole journey works together in production.

Quickstart

Build and run your first flow in under five minutes.

API Reference

Trigger runs programmatically and integrate with your CI/CD pipeline.