# What Is TestOwl? No-Code Test Automation For an executive overview of the platform architecture, visit the [How It Works](https://testowl.ai/how-it-works) product overview. :::lead TestOwl is a no-code QA testing platform that lets you create automated tests simply by using your web application. Record your actions, and TestOwl converts them into reusable, editable test cases that you can review, modify, and run whenever you need to verify your application still works as expected. ::: Instead of spending time writing and maintaining automation scripts, your team can focus on validating product behaviour. Tests remain visual, easy to understand, and simple to update as your application evolves. You never have to write automation code by hand. Record yourself using your application once—or build a test visually step by step—and TestOwl creates a structured test that you can edit, reorder, reuse, and run across multiple browsers, devices, and environments. :::highlight Create and maintain automated tests without writing code, learning an automation framework, or maintaining fragile test scripts. ::: :::quote{author="TestOwl Team"} Build the test the same way you'd use the app. That's the whole idea. ::: ## Who it's for - **QA teams** who want reliable regression testing without maintaining a large code-based automation suite. - **Product and engineering teams** who want fast feedback before every release without becoming automation experts. - **Startups and small teams** who need automated regression testing but don't have dedicated QA engineers. - **Anyone migrating** from a code-based framework—Playwright, Cypress, Selenium, WebdriverIO, Puppeteer, and others—who wants their existing tests inside a visual, team-friendly tool. See the [Import Wizard](/docs/import-test-scripts/overview). ## Why teams choose TestOwl With TestOwl you can: - Build automated tests without writing code. - Record user journeys directly from your browser. - Visually edit tests whenever your application changes. - Reuse common flows across multiple test cases. - Execute tests across different browsers, devices, and environments. - Run tests locally or in the cloud, or put them on a schedule so they run automatically. - Catch regressions before every release with detailed reports, including screenshots, videos, logs, and execution history. - Import existing tests from supported automation frameworks instead of rebuilding them from scratch. ## The core building blocks ::::cardgrid :::card{title="Projects" href="/docs/getting-started/creating-a-project"} Everything lives inside a project—your team, your tests, your environments, your data, and your execution history. ::: :::card{title="Flows" href="/docs/building-tests/flows"} Reusable sequences of steps (such as logging in) that you create once and reuse across multiple test cases. ::: :::card{title="Test Suites & Test Cases" href="/docs/building-tests/test-suites"} Test suites organise related test cases, making it easier to manage and execute your automated tests. ::: :::card{title="Environments" href="/docs/environments/overview"} Named run configurations that define which browser, device, locale, network conditions, and other settings a test runs with. ::: :::card{title="Runs & Reports" href="/docs/running-and-results/triggering-a-run"} Execute tests on demand, then inspect detailed reports with step-by-step results, screenshots, videos, logs, and failure diagnostics. ::: :::card{title="Dashboard" href="/docs/getting-started/dashboard"} Monitor your project's health with pass-rate trends, execution history, environment coverage, and insights into failing tests. ::: :::card{title="Schedules" href="/docs/running-and-results/schedules"} Run suites or tests automatically — once, at an interval, weekly, monthly, or on custom dates. ::: :::card{title="Plans & Billing" href="/docs/team-and-account/plans-and-usage"} Every project starts on a free trial. Compare plans, track your usage, and manage billing. ::: :::: New to the app? [Navigating TestOwl](/docs/getting-started/navigating-testowl) explains where each of these lives in the interface before you dive in. ## How a test comes together 1. **Record or build** a test using the [Recorder](/docs/building-tests/recording-a-test) or the [Step Editor](/docs/building-tests/the-editor), choosing from a comprehensive library of step types for navigation, mouse and keyboard interactions, forms, assertions, API requests, database queries, loops, conditions, variables, file operations, and more. 2. **Organise** it into a [Test Suite](/docs/building-tests/test-suites) as a [Test Case](/docs/building-tests/test-cases). 3. **Reuse** common sequences (such as logging in) as [Flows](/docs/building-tests/flows) instead of repeating steps across multiple tests. 4. **Configure** an [Environment](/docs/environments/overview) to define the browser, device, locale, and other runtime settings, then provide any required [Variables](/docs/data/variables) or [Secrets](/docs/data/secrets). 5. **Run** your test locally using the [Desktop App](/docs/running-and-results/desktop-app) or execute it in the cloud — now or on a [schedule](/docs/running-and-results/schedules) — then analyse the detailed [Report](/docs/running-and-results/reports) to understand exactly what happened. Ready to build your first automated test? Continue to the [Quickstart](/docs/getting-started/quickstart), where you'll create a project, record your first test, and run it in just a few minutes.