# QApilot Terminology Here are some common terminologies related to **QApilot** that you may come across: ### Test Case A test case is a list of steps or user actions that you list in a specific order to automate a test scenario. Test cases are conditions or steps designed to evaluate a particular feature or functionality of a software application. Users can create test cases using the **QApilot** Recorder or create steps manually. *** ### Test Suite A test suite is a collection or grouping of individual test cases that are organized together to execute them as a single entity. **QApilot** organizes your test cases into test suites based on common functionalities or scenarios to manage and execute them effectively. Test suites will help you in executing and reporting the test plan status. You can add a test case to multiple test suites. *** ### Test Data In **QApilot**, Test Data displays the details of the data sets utilized in different test scenarios. You can create and save data sets for various environments. The details of these data sets, such as the values used, are displayed in this tab. *** ### Test Rules **QApilot** Test Rules feature facilitates the appending/associating of relevant Test Data to the Test Cases under the respective Test Suite. They provide structure to the automation testing process and help ensure that tests are executed consistently, producing reliable and accurate results. *** ### Test Recorder Test Recorder lets you capture Elements and actions within **QApilot**. We recommend using the Test Step Recorder since it's quicker and easier and captures more locator details than manually creating elements. *** ### QApilot Executor as Local Agent You can run the tests you create on **QApilot** on your local device. For running the tests locally, you need a Local Agent utility running on the machine for Test Orchestration (queueing Tests, running the Tests, fetching the Test Results, etc.). *** ### Page Page in App Upload flow used in **QApilot** refers to a distinct screen or interface where specific functionality is implemented. It represents a logical section or module within the app. Each page in an app is designed to deliver a specific user experience, often related to a particular task or flow. *** ### Module A module in an application used in **QApilot** represents a self-contained unit that provides a specific feature or fulfills a functional need within the app. Each module typically focuses on delivering a specific scenario or workflow that aligns with the user’s needs. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.qapilot.io/detailed-documentation/qapilot-terminology.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.