-
Notifications
You must be signed in to change notification settings - Fork 1
test case doc #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
test case doc #28
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -1,32 +1,27 @@ | ||||||||||||||||||||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||||||||||||||||||||
| title: 'Creating an API Test Case' | ||||||||||||||||||||||||||||||||||||||||||||||||||
| description: 'Learn how to create a new API test case within an API suite in Robonito.' | ||||||||||||||||||||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||||||||||||||||||||
| ## Creating an API Test Case | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| # Creating an API Test Case | ||||||||||||||||||||||||||||||||||||||||||||||||||
| This guide explains how to create a new API test case using Robonito. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| An API test case in Robonito groups one or more API requests together to test a specific scenario or workflow. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| ### Adding Test Cases to a Suite | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| ### Prerequisite | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Test cases are systematically organized within suites according to functionality or modules. The type of test cases added depends on the suite type API. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Grammar issue in sentence. The phrase "depends on the suite type API" is grammatically unclear. 📝 Suggested fix-Test cases are systematically organized within suites according to functionality or modules. The type of test cases added depends on the suite type API.
+Test cases are systematically organized within suites according to functionality or modules. The type of test cases added depends on the suite type (API).📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| Before creating an API test case, ensure you have already created an API suite to contain it. If you haven't, see [How to Create an API Suite](../suites). | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| ### Steps to Create an API Test Case | ||||||||||||||||||||||||||||||||||||||||||||||||||
| #### Follow the steps below to create a Test Case | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| 1. **Open Test Explorer:** Navigate to the dashboard page and click the second icon in the sidebar to open the test explorer. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| 2. **Access Suite Menu:** In the test explorer's suite list, locate the API suite where you want to add the test case. Click the action menu button (usually represented by three dots or similar) associated with that suite. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| 3. **Add Test Case:** From the action menu, select the **Add Test Case** option. A modal window or form will appear. Fill in the required details for your new test case (e.g., name, description) and confirm its creation. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| 4. **Add Initial Request:** Once the test case is created, it will likely be empty. To make it functional, you need to add at least one API request. Click the **Add Request** button. A request holds all the configuration details for a single API call (URL, method, headers, body, etc.) within the test case. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| ### ✅ What's Next? | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| You have successfully created an API test case and added an initial request. The next step is to define the specifics of that request. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| Learn how to [Configure the API Endpoint](./configure-api-endpoint). | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 1. **Select Target Suite** Choose an existing test suite from the Target Suite dropdown. You may also type a name to create a new suite where the test case will be added. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 2. **Enter Test Case Name** Provide a clear and descriptive name in the Test case name field to easily identify the test scenario. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 3. **Select Test Type** Choose API as the test case type. This defines the test as an API automation test. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 4. **Add Description (Optional)** Enter a short description explaining the purpose and scope of the test case. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 5. **Select Browser** Choose the browser in which the test will run, such as Google Chrome. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 6. **Enter Target URL** Specify the application URL that will be opened when the test execution starts. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 7. **Select Device** Choose a predefined device preset to define screen resolution and viewport size (for example, Laptop 11 – 1366×768). | ||||||||||||||||||||||||||||||||||||||||||||||||||
|  | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Comment on lines
+14
to
+25
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Incorrect image alt texts throughout. All images use "Target Suite" as alt text regardless of what they're depicting. Alt text should accurately describe each image for accessibility. 📝 Suggested fix 1. **Select Target Suite** Choose an existing test suite from the Target Suite dropdown. You may also type a name to create a new suite where the test case will be added.

2. **Enter Test Case Name** Provide a clear and descriptive name in the Test case name field to easily identify the test scenario.
-
+
3. **Select Test Type** Choose API as the test case type. This defines the test as an API automation test.
-
+
4. **Add Description (Optional)** Enter a short description explaining the purpose and scope of the test case.
5. **Select Browser** Choose the browser in which the test will run, such as Google Chrome.
-
+
6. **Enter Target URL** Specify the application URL that will be opened when the test execution starts.
-
+
7. **Select Device** Choose a predefined device preset to define screen resolution and viewport size (for example, Laptop 11 – 1366×768).
-
+📝 Committable suggestion
Suggested change
🧰 Tools🪛 LanguageTool[style] ~19-~19: Consider using the synonym “brief” (= concise, using a few words, not lasting long) to strengthen your wording. (QUICK_BRIEF) 🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||||||||||||||||||||||||
| 8. **Auth Test Case (Optional)** Select an authentication test case to inject session cookies. This allows the test to bypass login steps during execution. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 9. **Create Test Case** Click the Create button to save the test case. Once created, the test case becomes available for adding steps and execution. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| ### Assertions | ||
|
|
||
| Assertions are used to validate expected behavior during test execution. **Robonito** allows you to add assertions while recording or after recording by editing a test step. | ||
|
|
||
| When adding an assertion, the **Add Assertion** dialog appears, enabling you to choose the assertion type and configure validation rules. | ||
|  | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| ### Page Assertion | ||
|
|
||
| Page Assertions are used to validate page-level properties during test execution. They ensure that the application navigates to the correct page and that the page is loaded as expected. | ||
|
|
||
| The **Add Page Assertion** dialog appears when you choose to add a page-level validation during recording or while editing a test step. | ||
|  | ||
|
|
||
| ### Page Assertion Types | ||
|
|
||
| Robonito supports the following page assertion types: | ||
|
|
||
|
|
||
| ### Page Title | ||
|
|
||
| Verifies the title of the currently loaded page. | ||
|
|
||
| ### Configuration Options | ||
|
|
||
| - **Expected Title*** – Enter the expected page title | ||
| - **Match Type** – Choose how the title should be matched: | ||
| - Exact Match | ||
| - Partial Match (if supported) | ||
|
Comment on lines
+21
to
+22
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ambiguous "(if supported)" qualifier. Documentation should state definitively whether Partial Match is supported. If it is, remove the qualifier. If it isn't yet implemented, either omit it or note it clearly as a planned feature. 🤖 Prompt for AI Agents |
||
| - **Case Sensitive** – Enable this option to perform case-sensitive matching | ||
|
|
||
| **Use case:** | ||
| Ensure the user is navigated to the correct page after an action. | ||
|
|
||
|
|
||
| ### Page URL | ||
|
|
||
| Validates the URL of the currently loaded page. | ||
|
|
||
| ### Configuration Options | ||
|
|
||
| - **URL*** – Enter the expected page URL | ||
|
|
||
| **Use case:** | ||
| Confirm correct navigation or routing after page transitions. | ||
|
|
||
|
|
||
| ### Add Page Assertion | ||
|
|
||
| After configuring the page assertion: | ||
|
|
||
| 1. Review the expected title or URL | ||
| 2. Click **Add Assertion** to attach the page assertion to the selected test step | ||
|
|
||
| During execution, Robonito evaluates the page assertion and marks it as **passed** or **failed** in the execution report. | ||
|
|
||
|
|
||
| ### Benefits of Page Assertions | ||
|
|
||
| Page Assertions help ensure: | ||
|
|
||
| - Correct navigation flow | ||
| - Accurate page rendering | ||
| - Reliable validation of routing behavior | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,55 @@ | ||
| ### Smart Assertion | ||
|
|
||
| Smart Assertion allows you to define validations using simple, human-readable descriptions. Instead of manually configuring assertion rules, you describe what should be true about the selected UI element, and **Robonito** automatically interprets and applies the appropriate validation logic. | ||
|
|
||
| This dialog appears when you choose **Smart Assertion** during recording or while editing a test step. | ||
|  | ||
|
|
||
| ### Create Smart Assertion | ||
|
|
||
| The **Create Assertion** dialog enables you to define intelligent assertions using natural language. | ||
|
|
||
|
|
||
| ### Assertion Description | ||
|
|
||
| Enter a clear description of what should be true about the selected element. | ||
|
|
||
| **Examples:** | ||
|
|
||
| - “The login button should be visible and clickable” | ||
| - “The error message should contain the text ‘Invalid credentials’” | ||
| - “The submit button should be disabled” | ||
|
|
||
| You can enter up to **500 characters**. | ||
|
|
||
|
|
||
| ### Instructions for Writing Smart Assertions | ||
|
|
||
| To create an effective Smart Assertion: | ||
|
|
||
| 1. Select the target UI element on the page first | ||
| 2. Describe what you want to verify about the element | ||
| 3. Use clear and specific language such as: | ||
| - `should be visible` | ||
| - `should be clickable` | ||
| - `should contain text` | ||
| 4. Save the assertion once the description is complete | ||
|
|
||
| The assertion is automatically evaluated during test execution. | ||
|
|
||
|
|
||
| ### Save Assertion | ||
|
|
||
| Click **Save Assertion** to attach the smart assertion to the selected test step. | ||
|
|
||
| During execution, Robonito evaluates the assertion and marks it as **passed** or **failed** in the execution report. | ||
|
|
||
|
|
||
| ### Benefits of Smart Assertions | ||
|
|
||
| Smart Assertions provide: | ||
|
|
||
| - Faster assertion creation | ||
| - Reduced manual configuration | ||
| - Clear, readable validations | ||
| - Improved test maintainability |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| ### Choose Assertion Type | ||
|
|
||
| Robonito supports two categories of assertions: | ||
|  | ||
|
|
||
| ### Content-Based Assertions | ||
|
|
||
| Content-based assertions validate text or content displayed on the page. | ||
|
|
||
| ### Plain Text | ||
|
|
||
| Asserts that a specific text appears on the page. | ||
|
|
||
| - Supports exact or partial text matching | ||
|
|
||
| **Use case:** | ||
| Validate headings, labels, messages, or static content. | ||
|
|
||
|
|
||
| ### Custom Expression | ||
|
|
||
| Asserts text using a custom expression for advanced matching scenarios. | ||
|
|
||
| **Use case:** | ||
| Validate dynamic text such as IDs, timestamps, or formatted values. | ||
|
|
||
|
|
||
| ### Regex | ||
|
|
||
| Validates text using regular expressions. | ||
|
|
||
| **Use case:** | ||
| Match complex patterns such as email addresses or dynamically generated strings. | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,83 @@ | ||
|
|
||
| ### UI / Element-Based Assertions | ||
|
|
||
| UI / Element-Based Assertions are used to validate the presence, visibility, count, and styling of specific UI elements on a page. These assertions ensure that UI components are rendered correctly and behave as expected during test execution. | ||
|
|
||
| The **Add Assertion** dialog appears when you select **UI / Element-Based** under the assertion type while recording or editing a test step. | ||
|  | ||
|
|
||
| ### Choose Assertion Type – UI / Element-Based | ||
|
|
||
| UI / Element-Based assertions focus on validating DOM elements rather than page content. | ||
|
|
||
| Robonito supports the following UI assertion types: | ||
|
|
||
|
|
||
| ### Element Exists | ||
|
|
||
| Asserts that a specific element exists in the DOM. | ||
|
|
||
| - Validates that the element is present, regardless of visibility | ||
| - Useful for ensuring required elements are rendered | ||
|
|
||
| **Use case:** | ||
| Verify that a header, button, or container exists on the page. | ||
|
|
||
|
|
||
| ### Element Visible | ||
|
|
||
| Asserts that a specific element is visible to the user. | ||
|
|
||
| - Ensures the element is displayed on the screen | ||
| - Useful for validating UI readiness before interactions | ||
|
|
||
| **Use case:** | ||
| Confirm that a button or text is visible before clicking or reading it. | ||
|
|
||
|
|
||
| ### Element Count | ||
|
|
||
| Validates the number of elements matching a selector. | ||
|
|
||
| ### Configuration Options | ||
|
|
||
| - **Expected count value** | ||
|
|
||
| **Use case:** | ||
| Verify the number of items in a list, table rows, or repeated UI components. | ||
|
|
||
|
|
||
| ### CSS Assertion | ||
|
|
||
| Validates the value of a specific CSS property for an element. | ||
|
|
||
| ### Configuration Options | ||
|
|
||
| - **CSS property name** | ||
| - **Expected property value** | ||
|
|
||
| **Use case:** | ||
| Ensure correct styling, such as color, font size, or visibility state. | ||
|
|
||
|
|
||
| ### Assertion Configuration | ||
|
|
||
| Once a UI assertion type is selected, the **Configuration** panel becomes active. | ||
|
|
||
| Depending on the selected assertion, you can configure: | ||
|
|
||
| - **Expected Text*** – The expected value associated with the element | ||
| - **Match Type** – How the value should be matched (e.g., Exact Match) | ||
| - **Case Sensitive** – Enable for case-sensitive matching | ||
|
|
||
| These settings define how Robonito evaluates the assertion during execution. | ||
|
|
||
|
|
||
| ### Add Assertion | ||
|
|
||
| After configuring the assertion: | ||
|
|
||
| 1. Review the selected UI assertion and configuration | ||
| 2. Click **Add Assertion** | ||
|
|
||
| The assertion is attached to the selected test step and evaluated during test execution. Results are displayed as **pass** or **fail** in the execution report. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| --- | ||
| title: 'Cloud' | ||
| description: 'Learn how to validate API responses using assertions in Robonito.' | ||
|
Comment on lines
+2
to
+3
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Align the meta description with Cloud execution content. The description mentions validating API responses using assertions, which doesn’t sound Cloud-specific. If this page is about cloud execution, please update the description to match the page topic so search/snippet text isn’t misleading. ✏️ Possible update-description: 'Learn how to validate API responses using assertions in Robonito.'
+description: 'Learn how to run and monitor tests in the Robonito Cloud.'🤖 Prompt for AI Agents |
||
| --- | ||
| Original file line number | Diff line number | Diff line change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,14 @@ | ||||||||||||||
| --- | ||||||||||||||
| title: Execution with Robonito | ||||||||||||||
| --- | ||||||||||||||
|
|
||||||||||||||
| # Execution | ||||||||||||||
|
|
||||||||||||||
| Robonito provides a powerful and intuitive way to test your APIs, ensuring they function correctly and meet expectations. This section guides you through the various features available for creating, configuring, and analyzing your API tests. | ||||||||||||||
|
|
||||||||||||||
| Learn how to: | ||||||||||||||
|
|
||||||||||||||
| - [Create an API Test Case](./create-api-testcase) | ||||||||||||||
|
Comment on lines
+9
to
+11
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix the API test case link target. The relative path resolves under 🔗 Proposed fix-- [Create an API Test Case](./create-api-testcase)
+- [Create an API Test Case](/api-testing/create-api-testcase)📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||
|
|
||||||||||||||
|
|
||||||||||||||
| Dive into the topics below to get started with API testing in Robonito. | ||||||||||||||
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,4 @@ | ||||||||||
| --- | ||||||||||
| title: 'Local Guide' | ||||||||||
| description: 'Learn how to validate API responses using assertions in Robonito.' | ||||||||||
|
Comment on lines
+2
to
+3
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Align the meta description with the Local guide topic. This description reads like the assertions page. If this page is about local execution, update the description to reflect that to avoid confusing metadata. ✏️ Possible update-description: 'Learn how to validate API responses using assertions in Robonito.'
+description: 'Learn how to run tests locally with Robonito.'📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||
| --- | ||||||||||
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
| @@ -1,12 +1,17 @@ | ||||||||
| --- | ||||||||
| title: Installation | ||||||||
| description: Robonito has two components the desktop app and a cloud executor. We shall share the installation of Robonito Desktop Application. The cloud executor lives in our (cloud) infrastructure with options for on-premise installation available but that is not covered in these docs. | ||||||||
| --- | ||||||||
| ### Installation Guide | ||||||||
|
|
||||||||
| This section explains how to install and set up **Robonito** on Windows, macOS, and Linux systems. Follow the instructions for your operating system to get started quickly. | ||||||||
|
|
||||||||
|
|
||||||||
| ### System Requirements | ||||||||
|
|
||||||||
| Before installing Robonito, ensure your system meets the following requirements: | ||||||||
|
|
||||||||
| ### Operating System | ||||||||
|
|
||||||||
| - [Download Robonito for Windows](https://robonito-prod-builds.s3.ap-south-1.amazonaws.com/Robonito-Setup-2.5.0.exe) | ||||||||
| - [Download Robonito for macOS](https://robonito-prod-builds.s3.ap-south-1.amazonaws.com/Robonito-2.5.0-arm64.dmg) | ||||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Indentation bug: macOS download link renders as a nested list item. Line 13 has a leading space before the Fix-- [Download Robonito for Windows](https://robonito-prod-builds.s3.ap-south-1.amazonaws.com/Robonito-Setup-2.5.0.exe)
- [Download Robonito for macOS](https://robonito-prod-builds.s3.ap-south-1.amazonaws.com/Robonito-2.5.0-arm64.dmg)
+- [Download Robonito for Windows](https://robonito-prod-builds.s3.ap-south-1.amazonaws.com/Robonito-Setup-2.5.0.exe)
+- [Download Robonito for macOS](https://robonito-prod-builds.s3.ap-south-1.amazonaws.com/Robonito-2.5.0-arm64.dmg)📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||
| - [Download Robonito for Linux](https://robonito-prod-builds.s3.ap-south-1.amazonaws.com/Robonito-2.5.0.AppImage) | ||||||||
|
|
||||||||
| The Robonito Desktop App is available for Windows and Mac | ||||||||
|
|
||||||||
| ## Installation Overview | ||||||||
|
|
||||||||
| Download for Window. | ||||||||
| Download for Mac intel or Mac Silicon. | ||||||||
| Download for Linux. | ||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,32 @@ | ||
| Robonito is currently compatible with Windows and Mac operating systems. At this time, we are not yet supporting Linux, but we appreciate your interest and feedback. | ||
| # Install Robonito on Linux | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Heading levels are inconsistent with the other OS guides. This file uses 🤖 Prompt for AI Agents |
||
|
|
||
| We are actively working to expand our offerings and hope to bring Linux compatibility in the future. | ||
| This guide explains how to install and run **Robonito** on Linux systems using AppImage. | ||
|
|
||
| Stay tuned for updates! | ||
| --- | ||
|
|
||
| ## System Requirements | ||
|
|
||
| Before installing Robonito, ensure your system meets the following requirements: | ||
|
|
||
| - **Operating System:** Ubuntu 20.04+, Debian-based, or equivalent | ||
| - **Browser:** Google Chrome (latest version recommended) | ||
| - **Internet Connection:** Required for updates | ||
| - **Permissions:** Execute permission for AppImage | ||
|
|
||
| --- | ||
|
|
||
| ## Download Robonito for Linux | ||
|
|
||
| - **Linux (AppImage)** | ||
| [Download Robonito for Linux](https://robonito-prod-builds.s3.ap-south-1.amazonaws.com/Robonito-2.5.0.AppImage) | ||
|
|
||
| --- | ||
|
|
||
| ## Installation Steps | ||
|
|
||
| 1. Download the Robonito AppImage file | ||
| 2. Open a terminal and navigate to the download directory | ||
| 3. Make the AppImage executable: | ||
|
|
||
| ```bash | ||
| chmod +x Robonito-2.5.0.AppImage | ||
|
Comment on lines
+31
to
+32
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. File appears truncated — code block is not closed. The file ends inside an open fenced code block ( Proposed fix to close the code block and add remaining content ```bash
chmod +x Robonito-2.5.0.AppImage
+ ```
+
+4. Run the AppImage:
+
+ ```bash
+ ./Robonito-2.5.0.AppImage
+ ```
+
+---
+
+## After Installation
+
+- Ensure **Google Chrome** is installed and up to date
+- Robonito is now ready to record and execute tests🤖 Prompt for AI Agents |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing YAML frontmatter.
This file is missing the YAML frontmatter that other documentation files in this PR have. Adding frontmatter with
titleanddescriptionfields ensures consistent metadata for navigation and SEO.📝 Suggested fix
📝 Committable suggestion
🤖 Prompt for AI Agents