# Building Tests in TestOwl

> How to build tests in TestOwl without writing code: record a journey, refine it in the Step Editor, and organise it into Test Cases and Suites.

## Guides in this Section

- [Recording a Test](/docs/building-tests/recording-a-test): The Recorder is the fastest way to create a test. Use your web app as normal and TestOwl converts every interaction into an editable test step.
- [The Step Editor](/docs/building-tests/the-editor): The Step Editor is where you build, edit and reorder test steps. How to add, change and organise steps in any Test Case or Flow, without writing code.
- [Step Library](/docs/building-tests/step-library): A reference for every step type in TestOwl — clicks, inputs, assertions, waits, navigation and more — with what each one does and when to use it.
- [Flows (Reusable Steps)](/docs/building-tests/flows): A Flow is a reusable sequence of steps shared across Test Cases. Build it once, maintain it in one place, and every test using it stays up to date.
- [Test Cases](/docs/building-tests/test-cases): A Test Case verifies one user journey in your app. How to create, edit and organise test cases by recording, building manually or reusing Flows.
- [Test Suites](/docs/building-tests/test-suites): A Test Suite groups related Test Cases so they are easier to manage and run together. How to create suites, add tests and run a whole suite at once.
- [Creating Tests with AI](/docs/building-tests/creating-tests-with-ai): Describe a test in plain English and let AI build it, or ask AI to carry out one instruction mid-recording. How both work, and what they cost.