> For the complete documentation index, see [llms.txt](https://docs.qapilot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qapilot.io/detailed-documentation/test-recording.md).

# Test Recording

You can quickly record test steps by capturing user interactions, such as clicking buttons, entering text, navigating through screens, etc. They help users create elements that interact with the application during testing.

***

## Prerequisites

1. Ensure you create a [Project ](/detailed-documentation/projects.md)before recording the test steps.
2. Establish a [Local/Cloud Device](/detailed-documentation/setup/system-requirements.md) connection setup.
3. You should know how to create a [Test Case](/detailed-documentation/qapilot-terminology.md#test-case)

***

## Recording Steps

1. Select the "Start Recording" option to start setting up a test.

<figure><img src="/files/BIAAMJCYpAYrGiRi7t6r" alt=""><figcaption></figcaption></figure>

2. Let us see each of these steps in detail:
   1. [**Recording**](/detailed-documentation/test-recording.md) is the starting point of the workflow. In this step, you connect the target device, launch the application, and capture the exact user interactions that QApilot stores as test steps for automation. These actions usually include taps, text entry, navigation, waits, and validations that represent a real user flow.
   2. [**Test Case**](/detailed-documentation/test-plan-executions/test-case.md) is where the recorded flow (group of test steps) is saved as a reusable automated entity. You can name the test case, organize it with metadata such as severity or module, and manage the recorded steps so the scenario is ready for repeatable execution.
   3. [**Test Suite**](/detailed-documentation/test-plan-executions/test-suite.md) helps you group related test cases into one execution-ready collection. This is useful when you want to validate a full business flow, run regression coverage, or maintain the order in which multiple test cases should execute.
   4. [**Test Execution**](/detailed-documentation/test-plan-executions.md) is the stage where the recorded and organized tests actually run on the selected device or environment. Here, you choose the execution source, apply test data and runtime settings, start the run, and review the generated results and reports.