Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 21 additions & 26 deletions contents/docs/api-testing/create-api-testcase/index.mdx
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.
Comment on lines +1 to +3
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Missing YAML frontmatter.

This file is missing the YAML frontmatter that other documentation files in this PR have. Adding frontmatter with title and description fields ensures consistent metadata for navigation and SEO.

📝 Suggested fix
+---
+title: 'Creating an API Test Case'
+description: 'Learn how to create an API test case in Robonito.'
+---
+
 ## Creating an API Test Case
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## Creating an API Test Case
# Creating an API Test Case
This guide explains how to create a new API test case using Robonito.
---
title: 'Creating an API Test Case'
description: 'Learn how to create an API test case in Robonito.'
---
## Creating an API Test Case
This guide explains how to create a new API test case using Robonito.
🤖 Prompt for AI Agents
In `@contents/docs/api-testing/create-api-testcase/index.mdx` around lines 1 - 3,
Add YAML frontmatter to the top of the MDX file containing at least title and
description keys; for example set title: "Creating an API Test Case" and
description: "This guide explains how to create a new API test case using
Robonito." Ensure the frontmatter block (--- delimited) is placed before the
existing content header so metadata is available for navigation and SEO.


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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
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).
🤖 Prompt for AI Agents
In `@contents/docs/api-testing/create-api-testcase/index.mdx` at line 7, Replace
the unclear phrase "depends on the suite type API" with a grammatically correct
and clearer wording; locate the sentence containing "depends on the suite type
API" and change it to something like "depends on the suite's type (for example,
API)" or "depends on whether the suite is an API suite" so the relationship
between suite type and test case type is unambiguous.


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.
![Open Test Explorer](/api-testing/test-explorer-instruction.png)

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.
![Access Suite Menu](/api-testing/api-suite-menu-item.png)

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.
![Add Test Case Button](/api-testing/create-testcase-button.png)

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.
![Add Request Button](/api-testing/create-endpoint.png)

### ✅ 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.
![Target Suite ](/test-case/target-suite.png)
2. **Enter Test Case Name** Provide a clear and descriptive name in the Test case name field to easily identify the test scenario.
![Target Suite ](/test-case/test-case-name.png)
3. **Select Test Type** Choose API as the test case type. This defines the test as an API automation test.
![Target Suite ](/test-case/api-test.png)
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.
![Target Suite ](/test-case/browser.png)
6. **Enter Target URL** Specify the application URL that will be opened when the test execution starts.
![Target Suite ](/test-case/url.png)
7. **Select Device** Choose a predefined device preset to define screen resolution and viewport size (for example, Laptop 11 – 1366×768).
![Target Suite ](/test-case/device.png)
Comment on lines +14 to +25
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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.
 ![Target Suite ](/test-case/target-suite.png)
 2. **Enter Test Case Name** Provide a clear and descriptive name in the Test case name field to easily identify the test scenario.
-![Target Suite ](/test-case/test-case-name.png)
+![Test Case Name](/test-case/test-case-name.png)
 3. **Select Test Type** Choose API as the test case type. This defines the test as an API automation test.
-![Target Suite ](/test-case/api-test.png)
+![API Test Type](/test-case/api-test.png)
 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.
-![Target Suite ](/test-case/browser.png)
+![Browser Selection](/test-case/browser.png)
 6. **Enter Target URL** Specify the application URL that will be opened when the test execution starts.
-![Target Suite ](/test-case/url.png)
+![Target URL](/test-case/url.png)
 7. **Select Device** Choose a predefined device preset to define screen resolution and viewport size (for example, Laptop 11 – 1366×768).
-![Target Suite ](/test-case/device.png)
+![Device Selection](/test-case/device.png)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
![Target Suite ](/test-case/target-suite.png)
2. **Enter Test Case Name** Provide a clear and descriptive name in the Test case name field to easily identify the test scenario.
![Target Suite ](/test-case/test-case-name.png)
3. **Select Test Type** Choose API as the test case type. This defines the test as an API automation test.
![Target Suite ](/test-case/api-test.png)
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.
![Target Suite ](/test-case/browser.png)
6. **Enter Target URL** Specify the application URL that will be opened when the test execution starts.
![Target Suite ](/test-case/url.png)
7. **Select Device** Choose a predefined device preset to define screen resolution and viewport size (for example, Laptop 11 – 1366×768).
![Target Suite ](/test-case/device.png)
![Target Suite ](/test-case/target-suite.png)
2. **Enter Test Case Name** Provide a clear and descriptive name in the Test case name field to easily identify the test scenario.
![Test Case Name](/test-case/test-case-name.png)
3. **Select Test Type** Choose API as the test case type. This defines the test as an API automation test.
![API Test Type](/test-case/api-test.png)
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.
![Browser Selection](/test-case/browser.png)
6. **Enter Target URL** Specify the application URL that will be opened when the test execution starts.
![Target URL](/test-case/url.png)
7. **Select Device** Choose a predefined device preset to define screen resolution and viewport size (for example, Laptop 11 – 1366×768).
![Device Selection](/test-case/device.png)
🧰 Tools
🪛 LanguageTool

[style] ~19-~19: Consider using the synonym “brief” (= concise, using a few words, not lasting long) to strengthen your wording.
Context: ... Add Description (Optional) Enter a short description explaining the purpose and ...

(QUICK_BRIEF)

🤖 Prompt for AI Agents
In `@contents/docs/api-testing/create-api-testcase/index.mdx` around lines 14 -
25, Update the incorrect, repeated alt text "Target Suite" for each image
markdown occurrence (e.g., the strings "![Target Suite
](/test-case/target-suite.png)", "![Target Suite
](/test-case/test-case-name.png)", "![Target Suite ](/test-case/api-test.png)",
"![Target Suite ](/test-case/browser.png)", "![Target Suite
](/test-case/url.png)", "![Target Suite ](/test-case/device.png)") so each alt
description accurately reflects the image (e.g., "Target Suite overview", "Test
case name field", "API test type selection", "Browser selection dropdown",
"Target URL field", "Device preset selection") to improve accessibility and
clarity.

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.
7 changes: 7 additions & 0 deletions contents/docs/assertions/index.mdx
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.
![Add Assertions](/test-case/add-assertion.png)

58 changes: 58 additions & 0 deletions contents/docs/assertions/page-assertion/index.mdx
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](/test-case/page-assertion.png)

### 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
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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
In `@contents/docs/assertions/page-assertion/index.mdx` around lines 21 - 22,
Clarify support status for "Partial Match" in page-assertion/index.mdx: either
remove the ambiguous "(if supported)" qualifier and list "Partial Match" as
supported, or explicitly state it is not yet implemented and add a short note
like "Partial Match — planned/coming soon" (or similar) so readers know its
status; update the list entry that currently reads "Partial Match (if
supported)" accordingly.

- **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

55 changes: 55 additions & 0 deletions contents/docs/assertions/smart-assertion/index.mdx
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.
![Smart Assertion](/test-case/smart-assertion1.png)

### 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
34 changes: 34 additions & 0 deletions contents/docs/assertions/text-assertion/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
### Choose Assertion Type

Robonito supports two categories of assertions:
![Text Assertions](/test-case/plain-text.png)

### 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.

83 changes: 83 additions & 0 deletions contents/docs/assertions/ui-assertion/index.mdx
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.
![Text Assertions](/test-case/ui-assertion.png)

### 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.
4 changes: 4 additions & 0 deletions contents/docs/executions/cloud/index.mdx
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
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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
In `@contents/docs/executions/cloud/index.mdx` around lines 2 - 3, The meta
description currently references "validating API responses using assertions"
which doesn't match the Cloud execution topic; update the frontmatter
description field (the "description" key alongside "title") to a Cloud-specific
summary—for example: describe deploying/running executions in the cloud,
configuration, and cloud-only considerations—so the description aligns with the
"title: 'Cloud'" page content and search/snippet text.

---
14 changes: 14 additions & 0 deletions contents/docs/executions/index.mdx
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
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix the API test case link target.

The relative path resolves under /executions. If the guide lives under /api-testing, this link will 404. Consider using an absolute path (or ../api-testing/...) instead.

🔗 Proposed fix
--   [Create an API Test Case](./create-api-testcase)
+-   [Create an API Test Case](/api-testing/create-api-testcase)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Learn how to:
- [Create an API Test Case](./create-api-testcase)
Learn how to:
- [Create an API Test Case](/api-testing/create-api-testcase)
🤖 Prompt for AI Agents
In `@contents/docs/executions/index.mdx` around lines 9 - 11, The link "[Create an
API Test Case](./create-api-testcase)" resolves relative to /executions and will
404; update that link target to the correct location (either an absolute path
like /api-testing/create-api-testcase or a correct relative path such as
../api-testing/create-api-testcase) so the "[Create an API Test Case]" link
points to the actual guide.



Dive into the topics below to get started with API testing in Robonito.
4 changes: 4 additions & 0 deletions contents/docs/executions/local/index.mdx
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
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
title: 'Local Guide'
description: 'Learn how to validate API responses using assertions in Robonito.'
title: 'Local Guide'
description: 'Learn how to run tests locally with Robonito.'
🤖 Prompt for AI Agents
In `@contents/docs/executions/local/index.mdx` around lines 2 - 3, Update the
frontmatter description to match the "Local Guide" topic rather than assertions:
change the description value in the document's metadata (the description
frontmatter key paired with title "Local Guide") to a short phrase about local
execution, e.g., explaining how to run and validate Robonito locally or how to
execute tasks/validate responses in a local environment so the metadata
accurately reflects the page content.

---
23 changes: 14 additions & 9 deletions contents/docs/installation/index.mdx
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)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Indentation bug: macOS download link renders as a nested list item.

Line 13 has a leading space before the -, causing Markdown to render it as a sub-item under the Windows link rather than a sibling list item.

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

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- [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)
🤖 Prompt for AI Agents
In `@contents/docs/installation/index.mdx` at line 13, The macOS download list
item in contents/docs/installation/index.mdx has a leading space before the '-'
so it renders as a nested list item; edit the list block and remove the extra
leading space before "- [Download Robonito for
macOS](https://robonito-prod-builds.s3.ap-south-1.amazonaws.com/Robonito-2.5.0-arm64.dmg)"
so it is aligned with the other top-level list entries (ensure the dash begins
at column 1 to restore sibling list item rendering).

- [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.
33 changes: 30 additions & 3 deletions contents/docs/installation/linux/index.mdx
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
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Heading levels are inconsistent with the other OS guides.

This file uses # (H1) for the title and ## (H2) for sections, while the macOS and Windows guides both use ### (H3) throughout. This will produce a visually inconsistent navigation and document hierarchy across the installation docs. Align heading levels across all three OS-specific pages.

🤖 Prompt for AI Agents
In `@contents/docs/installation/linux/index.mdx` at line 1, The Linux install
doc's top-level heading uses "#" and its sections use "##", which is
inconsistent with macOS/Windows using "###"; update the headings so the main
title line "# Install Robonito on Linux" becomes "### Install Robonito on Linux"
and change any "##" section headings in this file to "###" to match the other OS
guides and keep document hierarchy consistent.


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
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

File appears truncated — code block is not closed.

The file ends inside an open fenced code block (```bash) without a closing ```. This will break MDX rendering. Additionally, compared to the macOS and Windows guides, this Linux guide is missing steps after making the file executable (e.g., "Run the AppImage" and an "After Installation" section).

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
In `@contents/docs/installation/linux/index.mdx` around lines 31 - 32, The MDX
file ends inside an unclosed fenced code block starting with the "```bash" that
contains "chmod +x Robonito-2.5.0.AppImage"; close that code block, then append
the missing Linux steps consistent with macOS/Windows guides: add a "Run the
AppImage" step showing how to execute "./Robonito-2.5.0.AppImage" in a bash code
block, a horizontal rule, and an "After Installation" section listing
post-install checks (e.g., ensure Google Chrome is installed/up-to-date and that
Robonito is ready to record/execute tests) so the guide is complete and renders
correctly.

Loading